> Hmm, but the 'ver' output seems to have more information than those APIs.

Is there any need/desire to also identify Server 2016, 2019, and 2022? win32_ver() needs a workaround to return release '11' if the build number is 22000 or greater. The _WIN32_CLIENT_RELEASES table based on major.minor version number isn't helpful since Windows 10 and 11 have the same version number. It'sĪctually the build version which provides the indicator, it seems.Īny idea, whether a patch will fix this on Windows soonish ? Note: The tables for mapping to releases for Windows only take the Hmm, but the 'ver' output seems to have more information than those These probably need to be updated to return '11' for versions 0 and greater. > There are tables in platform module that map the specific version to the release name. Just like how Windows 5.x and 6.x were around for a very long time each ) > The version number for 'Windows 11' still starts with 10.0. There are tables in platform module that map the specific version to the release name. The version number for 'Windows 11' still starts with 10.0. I do wonder why those don't return the same version as the 'ver' command line tool.Īdding our Windows experts to the noisy list.

Win32_ver() should be using the internal Windows APIs to figure out the version. ĭemo.py contains dirty hack that can be used as a fix for some time before microsoft will not fix it. The bug comes from Microsoft terminal bug : If I type there : ver it will return Microsoft Windows only one patch is if that will check the build. The build version is correct ,but the windows version is still not. I was using the simplest way as possible: Now I am trying to write script that will detect is user use windows 11 or windows 10. Platform() is not able to detect windows 11Įvernow, eryksun, lemburg, lukasz.langa, miss-islington, paul.moore, sahsariga111, steve.dower, tim.golden, zach.wareĬreated on 19:43 by sahsariga111, last changed 14:59 by admin.

Windows 10 to windows 11 upgrade