Background:

As of November 2021, Microsoft has moved to annual update cycle for Windows 10 and 11. This means there is no YYH1 updates, making it a bit easier to predict what the next version of Windows 10 and 11 will be. This also incresaes uncertainty somewhat as feature update builds can be a bit unpredictable:

• Windows 10: Windows 10 is in maintenance mode (Vibranium releases). While people can guess what the build number can be (see below), we don't know when the final feature update will be released (I'm guessing 2023 based on support lifecycle for Home/Pro versus Enterprise/Education).
• Windows 11: build prediction is unpredictable as Microsoft can sign off on a build some time in northern spring with refresh branches used to prepare cumulative updates for the base build (compare co_release vs. co_refresh branches from last year).

Is your feature request related to a problem? Please describe.

With the impending release of Windows 10 and 11 Version 22H2, let NVDA recognize 22H2 builds. This can aid in detecting Sun Valley 2 (SV2) builds for UIA console and other work.

Describe the solution you'd like

Recognize the following builds:

• Windows 10 Version 22H2: 19045
• Windows 11 Version 22H2 (nickel/SV2): 22621

In addition, update AppX manifest to state that the last tested version is 10.0.22621.0 and ask folks to use Windows 11 SDK build 22621 (now available).

Describe alternatives you've considered

Leave things as is.

Additional context

Typically, new Windows builds are recognized once builds move to release preview channel. For Windows 11, this took place on June 7, 2022, and for Windows 10, it is being worked on internally.

Pull request strategy:

Choose from one of the following paths assuming that a PR is created:

1. Merge the upcoming PR.
2. Wait until Windows 10 Version 22H2 is released to release preview Insiders before merging the upcoming PR.

Thanks.