Forum Discussion

Rob Hamm's avatar
Rob Hamm
Copper Contributor
Aug 20, 2018

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...
General
Mike Jones's avatar
Mike Jones
Copper Contributor
Sep 13, 2018

On Server 2019 Standard Edition build 17733, the ReleaseId field from 

 "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" shows 1803.

 

On Server 2019 Datacenter Edition build 17744, the ReleaseId field shows 1809.

 

On Server 2016 Standard Edition Build 14393, the ReleaseId field shows 1607.

 

Does this mean that ReleaseId values 1803 and above will indicate that Server 2019 is present?

Thanks.

Mary Hoffman's avatar
Mary Hoffman
Former Employee
Sep 13, 2018

1809 is associated with Windows Server 2019 and Windows Server, version 1809 only. This number  represents the approximate YYMM of the final build, and is usually released to customers in the following month.  The Semi-Annual channel releases come out every 6 months or so and you will see this number change in the branding, i.e., Windows Server, version 1709 (1803, 1809, etc.) 

 

While we are developing the next release, the previous version number may still be present for some time in preview builds for vNext. The version number is usually not updated on previews until we get closer to the final build and are certain when we will be releasing it. Does that help?

  • Mike Jones's avatar
    Mike Jones
    Copper Contributor
    Sep 13, 2018

    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?

    • Aswin221285's avatar
      Aswin221285
      Copper Contributor
      Nov 21, 2018

      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

      • Deleted's avatar
        Deleted
        Nov 27, 2018

        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's avatar
      Mary Hoffman
      Former Employee
      Sep 13, 2018

      Windows Server 2016 will always be 1607. Once a product is released, that ID will not change.

      • tussinger's avatar
        tussinger
        Copper Contributor
        Oct 02, 2018

        Hi,

          we use the function GetVersionEx to determine the version.

          What is the different in Osversioninfoex between Server 2016 and 2019 ?

        thanks

           Richard

Resources