You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
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):
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.
The text was updated successfully, but these errors were encountered: