Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows 11 Version 24H2: recognize build 26100 as RTM build #16439

Closed
josephsl opened this issue Apr 22, 2024 · 0 comments · Fixed by #16481
Closed

Windows 11 Version 24H2: recognize build 26100 as RTM build #16439

josephsl opened this issue Apr 22, 2024 · 0 comments · Fixed by #16481
Labels
p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.

Comments

@josephsl
Copy link
Collaborator

Hi,

Part of winVersion module maintenance:

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

As of NVDA 2024.2, NVDA offers basic support for Windows 11 2024 Update (Version 24H2), specifically #16348. Therefore it makes sense to add the actual build number to winVersion module. Also, signs point to the below build as being the RTM, such as preview cumulative updates adn Xbox build numbers.

Describe the solution you'd like

Recognize build 26100 as Windows 11 Version 24H2 (and Server 2025) base (RTM) build.

Describe alternatives you've considered

Leave things as is.

Additional context

Version 24H2 is an OS upgrade - new build, changed system components, and several removals. Microsoft is putting finishing touches to it, including AI Explorer, fixing bugs, and other things. Windows 11 24H2 will be released in two waves (source: Windows Central):

  • Northern summer (June at the earliest): ARM64 version
  • Northern fall (September at the earliest): AMD64
    At the moment Windows Insiders in dev and canary channels are running the base build (26100) and a staging build (26200), respectively. I expect beta and release preview Insiders to meet 24H2 in the beginning and middle of northern summer, respectively, with general availability being later this year.

Based on how 24H2 updates turn out, the new winVersion.WinVersion entry can be part of NVDA 2024.2 (beta branch_ or 2024.3 (future alpha). For now I'll submit a pull request targeting beta branch in May.

Thanks.

@seanbudd seanbudd added p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation. labels Apr 22, 2024
seanbudd pushed a commit that referenced this issue May 31, 2024
Closes #16439

Summary of the issue:
Recognize Windows 11 build 26100 as 24H2 (2024 Update and Server 2025) RTM build.

Description of user facing changes
None

Description of development approach
winVersion.WIN11_24H2 constant is defined, as wel as updating last tested Widows version in AppX manifest to 10.0.26100.

Testing strategy:
Manual testing: on Windows 11 24H2 build 26100, make sure winVersion.getWinVer() == winVersion.WIN11_24H2.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p4 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants