You need both major, minor and build number to correctly identify windows 11.
See this good article that shows what real version number are for all the windows. https://www.lifewire.com/windows-version-numbers-2625171
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
the function RtlGetNtVersionNumbers in ntdll.dll and the macro VerifyVersionInfo from kernel32.dll both return MAJOR_VERSION 10 in Windows 11.
Why is that? Is there a new way of checking the OS version? I need this for development.
Running Windows 11 Pro, Build 22000.258, on a Hyper-V VM.
Thanks
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Answer accepted by question author
You need both major, minor and build number to correctly identify windows 11.
See this good article that shows what real version number are for all the windows. https://www.lifewire.com/windows-version-numbers-2625171
Hi Sumit,
I don't understand or appreciate the tone, but your answer gave me insight on the cause of the problem, not a way to fix it. It is always helpful to learn about the cause, but my main concern is a viable solution. Though I appreciate your efforts, a viable solution was provided in a different answer.
Hi Anastasis_
You may not like the answer, but this is true, and by design.
Thanks, this is very helpful!
Hi Anastasis,
I am Sumit here to assist you with this question.
Microsoft has not increased the Kernel number in Windows 11 to maintain compatibility, hence you see certain DLLs returning Windows 10 as version. This is by design, as Microsoft told us.
Hope that helps.