Detailed description of the issue
On June 19, 2026, Microsoft announced Windows 11 Version 26H2 (build 26300). The latest version recorded in NVDA is 25H2 (build 26200).
Why are the other templates not appropriate in this case?
This is not a bug report because it does not address regressions or errors. This is not a feature request because it does not add noticeable user-facing features. While this can be classified as a developer facing change, it is mostly designed to keep NVDA up to date with supported Windows releases.
Have you asked for advice on how to report this issue via a community discussion? If so, please link to the discussion
None
Additional information (if applicable)
There exists Windows 11 Version 26H1 but its build number is higher than 26H2 (26H1 = 28000, 26H2 = 26300). This means code like:
winVersion.WIN11_26H1 < winVersion.WIN11_26H2
will not make sense. Perhaps we need a dedicated winVersion constant for Windows 11 Version 26H1 (this may allow NVDA to support Windows API features introduced/changed in 26H1 but note that 26H1 is really meant for ARM64 devices released in 2026). Also, just like previous winVersion.WIN* constants, let's add 26H2 constants when 26H2 is released to release preview Insiders (this won't hapen until nothern fall, so it gives us time to discuss what to do with 26H1).
Steps to reproduce or illustrate the issue (if applicable)
None
Expected outcome or behaviour (if applicable)
ON build 26300, winVersion.getWinVer() == winVersion.WIN11_26H2 will be reported as "True"
Logs, screenshots and other attachments (if applicable)
None
NVDA type
No response
NVDA version
None because 26H2 constant is not defined yet
Have you tried any other versions of NVDA? If so, please report their behaviors.
None
Windows version
Windows 11 26H2 Insider Preview Experimental (build 26300.8935 AMD64)
Name and version of other software in use when reproducing the issue
None
Other information about your system
Used as a development workstation
Detailed description of the issue
On June 19, 2026, Microsoft announced Windows 11 Version 26H2 (build 26300). The latest version recorded in NVDA is 25H2 (build 26200).
Why are the other templates not appropriate in this case?
This is not a bug report because it does not address regressions or errors. This is not a feature request because it does not add noticeable user-facing features. While this can be classified as a developer facing change, it is mostly designed to keep NVDA up to date with supported Windows releases.
Have you asked for advice on how to report this issue via a community discussion? If so, please link to the discussion
None
Additional information (if applicable)
There exists Windows 11 Version 26H1 but its build number is higher than 26H2 (26H1 = 28000, 26H2 = 26300). This means code like:
winVersion.WIN11_26H1 < winVersion.WIN11_26H2will not make sense. Perhaps we need a dedicated winVersion constant for Windows 11 Version 26H1 (this may allow NVDA to support Windows API features introduced/changed in 26H1 but note that 26H1 is really meant for ARM64 devices released in 2026). Also, just like previous winVersion.WIN* constants, let's add 26H2 constants when 26H2 is released to release preview Insiders (this won't hapen until nothern fall, so it gives us time to discuss what to do with 26H1).
Steps to reproduce or illustrate the issue (if applicable)
None
Expected outcome or behaviour (if applicable)
ON build 26300, winVersion.getWinVer() == winVersion.WIN11_26H2 will be reported as "True"
Logs, screenshots and other attachments (if applicable)
None
NVDA type
No response
NVDA version
None because 26H2 constant is not defined yet
Have you tried any other versions of NVDA? If so, please report their behaviors.
None
Windows version
Windows 11 26H2 Insider Preview Experimental (build 26300.8935 AMD64)
Name and version of other software in use when reproducing the issue
None
Other information about your system
Used as a development workstation