We had a major storm through here recently and we suffered damage to the house roof and ceilings. I just received the quote to repair. I’m hoping that a small fraction of the 80,000 odd people that download SDIO and/or Desktop Info every month won’t mind chipping in a few dollars to help out. Click on the big blue button at the bottom of the page to help us keep a roof over our heads, literally!
Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.
Would it be possible to get an update to the version shown for Windows Server later than 2016? With Server 2019 and 2022 it continues to show 2016 and I suspect later this year will do the same for 2025. Thanks.
Added to the next release. enum.cpp.
Thank-you for doing this, but when I change from 2016 to 2022, it reverts back to 2016. I can change it to Win10/Win11 and it sticks, bit 2022 always goes back to 2016.
Also, you might want to add Server 2025 seeing as that's officially released now.
Added to the next release. enum.cpp.
Thank-you for doing this, but when I change from 2016 to 2022, it reverts back to 2016. I can change it to Win10/Win11 and it sticks, bit 2022 always goes back to 2016.
Also, you might want to add Server 2025 seeing as that's officially released now.
according to https://msdn.microsoft.com/en-au/library/windows/desktop/ms724832(v=vs.85).aspx
Windows 2016, 2019, 2022, 10 & 11 all have the same version number of 10.0. The reason it seems to go back to 2016 is because that's the first in the list with the version number of 10.0
This code is pretty obscure so it's going to take a while to figure out what to do about.
@glenn yes, all current releases of Windows workstation/server are v10.0 you need to also check against the build v.10.0.nnnnn - as usual, Microsoft hasn't made it very easy. Every few years the bginfo tool needs updating as well for the same reason.
