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

Include UBR (Update Build Revision) into Windows version number #1372

Closed
d1ss0nanz opened this issue Nov 1, 2022 · 2 comments · Fixed by #1374
Closed

Include UBR (Update Build Revision) into Windows version number #1372

d1ss0nanz opened this issue Nov 1, 2022 · 2 comments · Fixed by #1374

Comments

@d1ss0nanz
Copy link
Contributor

Is your feature request related to a problem? Please describe.
The currently returned version string on Windows is missing the UBR (Update Build Revision).

Describe the solution you'd like
In PlatformInformationWithContext read the 'UBR' key from 'SOFTWARE\Microsoft\Windows NT\CurrentVersion' and append it to the version.
Instead of "10.0.19044 Build 19044" we would have "10.0.19044.1949 Build 19044".

Describe alternatives you've considered
None.

Additional context
The version withour UBR is not very useful, since it only changes in the half-yearly updates. The UBR allows to track if the Windows installation is up to date.
https://learn.microsoft.com/en-us/windows/release-health/windows11-release-information

@d1ss0nanz
Copy link
Contributor Author

BTW: Is there a reason for the redundant build number in the version string?
"10.0.19044 Build 19044"

@shirou
Copy link
Owner

shirou commented Nov 5, 2022

Thank you for the information! I have opened PR #1374. Could you take a look?

BTW: Is there a reason for the redundant build number in the version string?

I can not remember, but I think this format comes from ohai. You can check Get-WmiObject Win32_OperatingSystem and Version string contains a version same as BuildNumber.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants