Windows Server release information

Microsoft has updated its servicing model. The Semi-Annual Channel is a twice-per-year feature update release with 18-month servicing timelines for each release. This page is designed to help you determine the end of support date for the Semi-Annual Channel releases.

The Semi-Annual Channel provides opportunity for customers who are innovating quickly to take advantage of new operating system capabilities at a faster pace, both in applications — particularly those built on containers and microservices. For more information see the Comparison of servicing channels. Customers also have the option to continue using the Long-Term Servicing Channel releases, which continue to be released every 2-3 years. Each Long-Term Servicing Channel release is supported for 5 years of mainstream support and 5 years of extended support.

Windows Server current versions by servicing option

Windows Server release	Version	OS Build	Availability	Mainstream support end date	Extended support end date
Windows Server, version 20H2 (Semi-Annual Channel) (Datacenter Core, Standard Core)	20H2	19042.508.200927-1902	10/20/2020	05/10/2022	Review note
Windows Server, version 2004 (Semi-Annual Channel) (Datacenter Core, Standard Core)	2004	19041.264.200508-2205	05/27/2020	12/14/2021	Review note
Windows Server, version 1909 (Semi-Annual Channel) (Datacenter Core, Standard Core)	1909	18363.418.191007-0143	11/12/2019	05/11/2021	Review note
Windows Server, version 1903 (Semi-Annual Channel) (Datacenter Core, Standard Core)	1903	18362.30.190401-1528	5/21/2019	12/08/2020	Review note
Windows Server 2019 (Long-Term Servicing Channel) (Datacenter, Essentials, Standard)	1809	17763.107.1010129-1455	11/13/2018	01/09/2024	01/09/2029
Windows Server, version 1809 (Semi-Annual Channel) (Datacenter Core, Standard Core)	1809	17763.107.1010129-1455	11/13/2018	11/10/2020	Review note
Windows Server 2016 (Long-Term Servicing Channel)	1607	14393.0	10/15/2016	01/11/2022	01/11/2027

End of service for Windows Server, version 1809 has been delayed due to the ongoing public health crisis. For more information, see our Support article.

Windows Server, version 1803 and later are governed by the Modern Lifecycle Policy. See the Windows Lifecycle FAQ and Comparison of servicing channels for details regarding servicing requirements and other important information.

Operating System Version

The Version API Helper functions are used to determine the version of the operating system that is currently running. For more information, see Getting the System Version.

The following table summarizes the most recent operating system version numbers.

Operating system	Version number
Windows 10	10.0*
Windows Server 2019	10.0*
Windows Server 2016	10.0*
Windows 8.1	6.3*
Windows Server 2012 R2	6.3*
Windows 8	6.2
Windows Server 2012	6.2
Windows 7	6.1
Windows Server 2008 R2	6.1
Windows Server 2008	6.0
Windows Vista	6.0
Windows Server 2003 R2	5.2
Windows Server 2003	5.2
Windows XP 64-Bit Edition	5.2
Windows XP	5.1
Windows 2000	5.0

* For applications that have been manifested for Windows 8.1 or Windows 10. Applications not manifested for Windows 8.1 or Windows 10 will return the Windows 8 OS version value (6.2). To manifest your applications for Windows 8.1 or Windows 10, refer to Targeting your application for Windows.

Identifying the current operating system is usually not the best way to determine whether a particular operating system feature is present. This is because the operating system may have had new features added in a redistributable DLL. Rather than using the Version API Helper functions to determine the operating system platform or version number, test for the presence of the feature itself.

To determine the best way to test for a feature, refer to the documentation for the feature of interest. The following list discusses some common techniques for feature detection:

• You can test for the presence of the functions associated with a feature. To test for the presence of a function in a system DLL, call the LoadLibrary function to load the DLL. Then call the GetProcAddress function to determine whether the function of interest is present in the DLL. Use the pointer returned by GetProcAddress to call the function. Note that even if the function is present, it may be a stub that just returns an error code such as ERROR_CALL_NOT_IMPLEMENTED.
• You can determine the presence of some features by using the GetSystemMetrics function. For example, you can detect multiple display monitors by calling GetSystemMetrics(SM_CMONITORS).
• There are several versions of the redistributable DLLs that implement shell and common control features. For information about determining which versions are present on the system your application is running on, see the topic Shell and Common Controls Versions.

If you must require a particular operating system, be sure to use it as a minimum supported version, rather than design the test for the one operating system. This way, your detection code will continue to work on future versions of Windows.

Note that a 32-bit application can detect whether it is running under WOW64 by calling the IsWow64Process function. It can obtain additional processor information by calling the GetNativeSystemInfo function.

Windows Server: versions, editions, licensing

When wondering which version of Windows Server to choose for their business, users, as a rule, are faced with a wide variety, and it is far from always clear how to choose the most suitable option. The Windows Server operating system has not only different versions but also different editions. Let’s look at the differences between them.

What is a version of Windows Server?

In the 90s, during the time of Windows NT, each version of Windows Server had a unique number. For example, Windows NT had numbers 3.1, 3.51, and 4.0. But starting in 2000, Microsoft began to add, after the name, the year the operating system was launched: Microsoft Windows 2000, Windows Server 2003, 2008 (which also had version R2), 2012 (also with R2), 2016 and 2019, etc.

Each new version of Microsoft Windows Server introduces new functionality. For example, Hyper-V, Server Core, and BitLocker virtualization were introduced in Windows Server 2008, Windows and Nano Server containers were introduced in Windows Server 2016 , and Windows Server 2019 brought Windows Admin Center — a new way to remotely administer the server infrastructure, improve the hyper-converged infrastructure and deep support for the Linux subsystem.

What is the end of support?

As they say, nothing lasts forever. And at some point, Microsoft stops releasing patches for legacy software. The date by which Microsoft releases product updates is called the end date of support. And after this date has passed, an outdated version of the OS will become an easy target for malware, since it will no longer receive security updates and, therefore, will be vulnerable to new exploits.

Microsoft operating systems are usually supported for at least 10 years. For example, the popular Windows Server 2003, released in April 2003, had extensive support that ended in 2015. Extended support for Windows Server 2008 R2 should end in January 2020, and Windows Server 2012 R2 will continue to receive updates until at least October 2023. Versions of Server 2016 and 2019 will receive updates through 2027 and 2029, respectively. Therefore, for security reasons, organizations should only use the latest versions of Windows Server.

What is the Windows Server edition?

When you buy a car, at least several sets of the same model are available to you. For example, the basic economical option, a luxurious option with leather seats and a sunroof, as well as a sporty option with larger wheels and a more powerful engine. In other words, each version of the car has its price and feature set for groups of customers with different budgets and needs.

The same goes for Windows Server editions. Each option includes functionality that is suitable for different companies, depending on their size and budget. For example, different editions may support a different number of users.

Differences between editions of Windows Server 2012 R2

To help understand some of the differences between OS editions, let’s look at an example of Windows Server 2012 R2:

• Foundation is a general-purpose server OS that is best suited for lower-level servers. The OS only supports one processor and 32 GB of RAM. The Foundation edition (not available in Windows Server 2016) is limited to 15 users, which makes it suitable only for small offices. Foundation is only available through OEMs, which usually means it is preinstalled on computers that you buy from companies such as Dell and HPE.
• Essentials (formerly SBS or Small Business Server) is an easy-to-configure server solution that supports up to 25 users and 50 devices, making it suitable for small offices. Essentials support more powerful hardware with up to 64 GB of RAM and two processors. Unlike other editions of Windows Server, Essentials pre-configured roles such as Active Directory, DNS, file services, IIS, and Remote Desktop, making it ideal for organizations with less developed IT or less experienced IT staff.
• Standard does not restrict users, but unlike Foundation and Essentials, you will have to purchase Client Access Licenses (CALs) separately, depending on how many people you need to support. Standard supports a maximum of 4 TB of RAM, and each license purchased extends to two processors. If you are interested in virtualization, this release will allow you to use the Hyper-V hypervisor to run up to two virtual instances of the operating system (additional virtual instances of Windows Server will require additional costs) on the same physical hardware, which makes the Standard edition suitable for a lightly virtualized environment.
• Datacenter is the best and most expensive edition of Windows Server. Windows Server 2012 R2 Datacenter is almost identical to the standard version with one big exception. With the Datacenter license, you can run an unlimited number of virtual instances with Windows Server as a guest OS on a single dual-processor computer. This small difference has a big impact, as companies can save by running dozens of OS instances on a single server.

The differences between editions of Windows Server 2016 and 2019

• Hyper-V is a free edition of Windows Server designed only to launch the Hyper-V hypervisor role. Its goal is to be a hypervisor for your virtual environment. It does not have a graphical interface. This is a stripped-down version of Server Core. You will use sconfig.cmd to enable the hypervisor, and then manage the environment using Hyper-V Manager (as part of RSAT) from a Windows 10 workstation on your network. It is recommended that you use this edition for your hypervisor to maintain the purity and simplicity of licensing.
• Essentials — ideal for both small and medium-sized businesses, and people with needs for basic server functions. The GUI is pretty much the same as in Standard, except the Essentials setup wizard.

Virtualization Rights
You are allowed to run one physical Essentials instance as a Hyper-V host that hosts one Essentials virtual instance. You need to remove all roles except the Hyper-V role from the physical instance of Essentials to ensure compliance. Essentials are also suitable for one virtual instance on any other hypervisor.

Licensing model
based on the processor. Client licenses are not required, but you are limited to 25 users and 50 devices connecting to the server.

Hardware limitations
Essentials are limited to 64 GB of RAM and 2 CPUs on the computer on which it is installed.

• Standard — ideal for any company or for people who require advanced features, but they will not be intensively virtualized.

Virtualization Rights
You can run up to two Hyper-V virtual machines or containers or one physical instance with a standard license. If you use the Hyper-V role only on a physical instance, you can use it as a Hyper-V host, and then host two Hyper-V virtual machines on that host. If you want to use multiple roles on a physical instance, you cannot start the virtual machine on top with the same license.

Licensing model
based on the core. Client licenses are required for each user or device that connects indirectly or directly to the server. For example, if you use the server as a file server, you will need a CAL for each user account or computer that accesses this file server on the network.

Hardware limitations
The standard is limited to a maximum of 24 TB of RAM and 512 cores.

• Datacenter — ideal for any company with a high degree of virtualization. You get a license depending on how many cores your hosts have on which any virtual machine with a version of Datacenter can live (run or potentially run after Vmotion). This licensing, at first glance, seems expensive, but it allows you to create an unlimited number of virtual machines running Datacenter on the hosts that you consider. If you have a small number of hosts (and subsequently kernels) and a large number of potential virtual machines, then this license is not difficult.

Virtualization Rights
The unlimited number of virtual machines or Hyper-V containers. As stated above, you will buy licenses depending on how many cores you have on the hosts. At this point, you can run as many virtual machines as you like on the hosts using any role.

Licensing model
based on cores. Make sure that you do not accidentally select this release when installing on a physical server that does not host virtual machines. Client licenses are required for each user or device that connects indirectly or directly to servers in your environment.

Differences in licensing for Windows Server 2016 and newer

Although the prices for Windows Server 2012 R2, 2016, 2019 are the same, if you are using a standard license or a Datacenter license for Windows Server 2016 or later, there are some key changes that you need to be aware of. First of all, while Windows Server licenses have historically been sold for each processor/socket, in Windows Server 2016, the licensing model switched to each core.

Thus, if you have a server containing 2 processors with 24 cores, in Windows Server 2012 you will only need to buy one Standard or Datacenter license. In Windows Server 2016, you will have to buy licenses for all 24 cores. This becomes quite difficult, as there are many rules, but the main thing is that if you have a 16-core server, the costs will be approximately the same. However, OS licensing may be more expensive on servers with a higher core density.

Despite the change to the core license, the virtualization rules remain the same in Windows Server 2016 and later. Once you have licensed all your cores on the server, with the standard version you get 2 licenses for the Windows Server guest OS compared to the unlimited number in the Datacenter version.

Also, the features in Windows Server 2012 Standard and Datacenter were the same. But some features of Windows Server 2016, such as Storage Spaces Direct or shielded virtual machines, are only available in the Datacenter release.

Comparing installation options for Windows Server 2016 and 2019

Standard and Datacenter editions offer a variety of installation options. These options affect what features will be available after installation, such as a graphical user interface and a set of services. The following installation options are available:

• Desktop Experience (with a graphical interface);
• Core;
• Nano

Desktop Experience is an installation option that most people are familiar with. This option installs most of the functions and roles out of the box, including the desktop GUI. You will receive the Server Manager, which allows you to add and remove roles and components. The advantage is that the system can be easier to manage for people who are used to using a graphical interface. The downside is that you have more updates, reboots, and open ports to deal with.

Learn more from Microsoft here .

The Server Core lacks a graphical interface and several roles that are installed by default under the Desktop Experience option. The server core has less disk space and, therefore, a smaller attack area due to the smaller codebase. There are also fewer updates, reboots, and open ports to work with. This is a great option for infrastructure servers such as Active Directory domain controllers and DNS servers.

This edition lacks accessibility tools, built-in server configuration tools, and sound support. This version is no frills. It will not be amiss to make sure that you are familiar with command-line administration.

You can read more about this on Microsoft’s site.

Starting with Windows Server 2019, Nano is only available as a containerized image of the operating system. It is designed to run as a container inside a container host, such as the Server Core mentioned above. If you rely on container applications designed for server OS, then you will use this version to compile these applications.

Nano can be deployed using Standard or Datacenter versions, but you must have Software Assurance attached to the host server licensing. You can learn more about this on the website of Microsoft.