nvda

53f01f4c - appModules/explorer: report Windows build.revision as product version (#19855)

appModules/explorer: report Windows build.revision as product version (#19855) Closes #19802 Summary of the issue: File Explorer app module reports wrong product version (specifically, base Windows version). Description of user facing changes: Product version for File Explorer will reflect current Windows build.revision. Description of developer facing changes: Add-ons and parts of NVDA code that queries app version data will see a more "accurate" (see below) product version for File Explorer. Description of development approach: A custom "est product info" method is defined in the File Explorer app module. This is needed because "productVersion" is a descriptor and one must define "_set_productVersion" to override it. Further, even with the custom product version defined, it can be overridden from the base app module every time set product info method is run. Therefore, a custom 'set product info' method is defined to treat Windows build.revision as File Explorer product version. This change will be most noticeable if running an enablement package release. For example, Windows 11 24H2's build number is 26100 which is also shown for system files after installing 25H2 (build 26200) because 25H2 is an enablement package on top of 24H2. Further, NVDA is actually dealing with "wxplorer.exe.mui" not "explorer.exe" when asking for file information from Windows.