Hi,
This could be considered a subtle form of add-on to NVDA Core issue:
Background
Windows releases are identified by four part version number: major.minor.build.revision. The first three identifies a given Windows release, whereas the fourth number (sometimes called QFE (quick fix engineering) build) identifies the update revision for a build and is updated whenever Windows Update installs cumulative updates. For example, as of June 2025, the latest Windows 11 24H2 build identifies itself as 10 (major).0 (minor).26100 (build).4351 (update build revision).
Is your feature request related to a problem? Please describe.
As part of GitHub issues template, people are asked to fill in the Windows version the yare using. While most submitters do include Windows version identifier information such as 10 22H2 or 11 2024 Update, only the build number is given. As explained above, whenever a computer installs cumulative updates, the fourth component (build revision) changes, and this information can provide information to compare the latest revision versus what the submitter is using. The update revisoin can also help us identify if a Windows issue the submitter is experiencing is resolved in a later release, thereby directing reporters to appropriate Microsoft Knowledge Base (KB) article.
Describe the solution you'd like
Add "revision" field to winVersion.WinVersion class to record update build revision (UBR) value, accessible from Windows Registry. In short, a specific code path from Resource Monitor will be brought into NVDA Core.
Describe alternatives you've considered
No action, or ask users to run WinVer and copy the build.revision information.
Additional context
Resource Monitor reports build.revision when NVDA+Shift+number row 6 is pressed. A potential downside is that if revision field is static, NVDA may report wrong information if a hotpatch changes revisoin number after installation.
Thanks.
Hi,
This could be considered a subtle form of add-on to NVDA Core issue:
Background
Windows releases are identified by four part version number: major.minor.build.revision. The first three identifies a given Windows release, whereas the fourth number (sometimes called QFE (quick fix engineering) build) identifies the update revision for a build and is updated whenever Windows Update installs cumulative updates. For example, as of June 2025, the latest Windows 11 24H2 build identifies itself as 10 (major).0 (minor).26100 (build).4351 (update build revision).
Is your feature request related to a problem? Please describe.
As part of GitHub issues template, people are asked to fill in the Windows version the yare using. While most submitters do include Windows version identifier information such as 10 22H2 or 11 2024 Update, only the build number is given. As explained above, whenever a computer installs cumulative updates, the fourth component (build revision) changes, and this information can provide information to compare the latest revision versus what the submitter is using. The update revisoin can also help us identify if a Windows issue the submitter is experiencing is resolved in a later release, thereby directing reporters to appropriate Microsoft Knowledge Base (KB) article.
Describe the solution you'd like
Add "revision" field to winVersion.WinVersion class to record update build revision (UBR) value, accessible from Windows Registry. In short, a specific code path from Resource Monitor will be brought into NVDA Core.
Describe alternatives you've considered
No action, or ask users to run WinVer and copy the build.revision information.
Additional context
Resource Monitor reports build.revision when NVDA+Shift+number row 6 is pressed. A potential downside is that if revision field is static, NVDA may report wrong information if a hotpatch changes revisoin number after installation.
Thanks.