Forum Discussion
Windows Server 2019 version info
Preliminary tests have revealed that the version of 'kernel32.dll' found on our current preview build Windows Server 2019 system is of the form '10.0.x.x'. Hence, it would appear that the major/min...
Thanks Mary.
My concern is the ReleaseId value for Server 2016 would be changed to a value above the current 1607. That is, new updates to Server 2016 this year or next year would be 18xx or 19xx. Is this the case? If so, then I can't assume that a ReleaseId value of less than 1803 will indicate that Server 2016 is present.
Or, is this ReleaseId value for Server 2016 fixed no matter how many Server 2016 updates occur?
Hi Mike
I have the same issue how would you determine the standard release version using Microsoft Docs . Currently we are using OSVersionInfoex to determine the windows server and now what I am trying to is if we first determine the major and minor version if the major version is 10 and minor version is 0 and osvi.wProductType != VER_NT_WORKSTATION and then if osvi.dwBuildNumber >= 17633 then we are going determine that as windows 2019 else it would be windows 2016 will that work ?. Your response would be highly appreciated
To determine if Server 2016 or Server 2019 is present, I read the Windows Registry key that Mary Hoffman suggested back on 08-22-2018. As for using the Build Number, Mary would need to confirm if this would work as well.
Hope this helps!
- Mary Hoffman
Microsoft
The ReleaseID value for Server 2016 was 1607. For Server 2019, it was 1809. Having said that, this early in the preview cycle for VNext, the ReleaseID located at hklm:\software\microsoft\windows\windows NT\CurrentVersion" -Name ReleaseID has not yet been updated for vNext and previews will still have the value "1809". The final build of Windows Server 2019 was 17763. For now, it is safe to assume that any major build number greater than 17763 is a preview for vNext.
But is it safe to assume any build number greater than 17633 that is not VER_NT_WORKSTATION is server 2019?
