Windows Server end of life: support dates for 2019, 2016, 2022 and 2012 R2

Windows Server 2019 reaches end of life on January 9, 2029, when its extended support ends; mainstream support already ended on January 9, 2024. Until 2029 it still gets monthly security updates, but no new features and no non-security fixes. Windows Server 2016 is much closer: its extended support ends on January 12, 2027. Windows Server 2022 left mainstream support on October 13, 2026 and gets security updates until October 14, 2031, while Windows Server 2012 R2 gets nothing at all since its last paid update year ended on October 13, 2026.

Source: Microsoft’s Lifecycle page for each version, checked 21.10.2026 (links at the end of the article). All five follow Microsoft’s Fixed Lifecycle Policy, and the dates apply to the Standard, Datacenter and Essentials editions alike. Microsoft shows the dates in Pacific Time, so in Europe the last day of support ends on the following morning.

What do mainstream support, extended support and end of life mean?

“End of life” is the everyday name; Microsoft calls it end of support, and it is the end of the extended phase, not the mainstream one. Microsoft’s Fixed Lifecycle Policy defines the phases like this:

For a server you run yourself, the line that matters is the first one. A version in extended support is as safe to run as one in mainstream support, as long as you install the monthly updates. A version past its end of support stops receiving fixes for newly found vulnerabilities, and every month that passes adds holes that will never be closed.

When does Windows Server 2019 reach end of life?

On January 9, 2029. Mainstream support ended on January 9, 2024, so 2019 has been in extended support for almost three years: it still gets the monthly security updates and will until 2029, but Microsoft no longer fixes non-security bugs in it. Microsoft re-released Windows Server 2019 on November 13, 2018 and counts its dates from that release.

In practice, 2019 is a reasonable system to run today and a poor one to set up for the next five years. Microsoft supports in-place upgrades from 2019 to 2022 and to 2025 (see the upgrade paths), so the move does not have to be a rebuild.

When does Windows Server 2016 reach end of life?

On January 12, 2027, less than three months after this article was written. Mainstream support ended on January 11, 2022. After January 12, 2027 Windows Update offers no further security updates for 2016.

Unlike 2012 R2, 2016 has no extended update programme to fall back on so far: Microsoft’s Lifecycle FAQ on Extended Security Updates, checked 21.10.2026, lists ESU for Windows Server 2012 and 2012 R2 and for Windows 10, and none for Windows Server 2016. Plan the move now. From 2016, Microsoft supports in-place upgrades to 2019, 2022 and 2025.

What changed for Windows Server 2022 on October 13, 2026?

Its mainstream support ended. Since October 14, 2026, Windows Server 2022 is in extended support: security updates continue every month until October 14, 2031, but non-security fixes and feature changes are over. Nothing changes on a running server, and nothing needs to be done right away. Of the versions most servers run today, 2022 has the longest security support left after 2025.

Is Windows Server 2012 R2 still getting updates?

No. Its extended support ended on October 10, 2023. Microsoft then offered three paid years of Extended Security Updates, which ended on October 8, 2024, October 14, 2025 and October 13, 2026. Microsoft describes ESU as coverage of up to three years after the end of support, so since October 14, 2026 there is no update channel for 2012 R2 left at all. The Lifecycle page adds that Microsoft Edge 109 was the last Edge version for Windows Server 2012 and 2012 R2, with critical fixes until October 10, 2023.

A 2012 R2 server can go in place to 2016, 2019 or straight to 2025, but not directly to 2022: Microsoft’s path table allows two versions at a time up to 2022 and four at a time to 2025.

And Windows Server 2025?

Support for Windows Server 2025 started on November 1, 2024. Mainstream support runs until November 13, 2029 and extended support until November 14, 2034, three years past 2022.

What are Extended Security Updates, and can you buy them?

ESU is Microsoft’s paid last resort for running a version past its end of support: critical and important security updates only, for at most three years, with no new features and no technical support beyond the updates themselves. On Azure virtual machines it is included at no extra charge. Everywhere else, Microsoft sells it through volume licensing or Azure Arc, and only for servers covered by Software Assurance, subscription licences, or Windows licensed through a provider’s licence-included (SPLA) offer. Late sign-ups pay for the months they missed.

Two things follow for a rented server. ESU exists only for the versions Microsoft names; today that is 2012 and 2012 R2, whose ESU has now ended too. And a server on a Windows evaluation licence meets none of the eligibility conditions above, so the realistic answer to an end-of-support date is an upgrade or a new server, not ESU.

How do I check which version a server runs?

Get-ComputerInfo -Property WindowsProductName, OsBuildNumber
DISM /online /Get-CurrentEdition      # e.g. ServerStandard, or ServerDatacenterEval on an evaluation

winver shows the same in a window. The build number tells the versions apart even where a product name is ambiguous:

Which upgrade paths does Microsoft support?

From Microsoft’s “Plan your Windows Server upgrade path”, for an in-place upgrade with installation media on a server that is not clustered:

Windows Server 2019 and 2022 can also go to 2025 through Windows Update as a feature update, without installation media. Microsoft requires the March 2026 cumulative update or later first (KB5078752 for 2019, KB5078766 for 2022) and a registry value that allows the offer:

New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AllowWindowsServerFeatureUpdate"
New-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AllowWindowsServerFeatureUpdate" -Name "AllowWindowsServerFeatureUpdate" -PropertyType DWord -Value 1

The conditions Microsoft attaches to every in-place upgrade:

• A licence for the new version. Unlike Windows on a PC, each Windows Server upgrade needs its own valid product key and activation for the target version.
• A full backup that you have tested by restoring it, and a maintenance window: the server restarts several times.
• Same language and same installation type. Switching between Server Core and Desktop Experience during the upgrade is not supported, and neither is changing the language.
• No domain controllers. Microsoft advises against upgrading domain controllers in place: install a new one on the new version and retire the old one.
• Your provider. Microsoft notes that some cloud providers support in-place upgrades and some do not, so check with yours.

Setup logs land in C:\Windows\Panther if an upgrade fails, and Get-ComputerInfo -Property WindowsProductName confirms the new version afterwards.

What does this mean on a VMHeaven Windows server?

Our Windows images are Windows Server 2022 and Windows Server 2019, picked at order time and reinstallable from the panel. Both are in extended support and get security updates: 2022 until October 14, 2031, 2019 until January 9, 2029. We do not offer 2016, 2012 R2 or 2025 images.

• For a new server, choose 2022 unless an application needs 2019: it has almost three more years of security updates.
• Install the monthly updates on whichever you run; extended support only protects a server that takes them. The commands are in keeping Windows Server updated.
• Moving from 2019 to 2022 is cleanest as a fresh install: a second server, or a reinstall from the panel once your data is safe elsewhere, because a reinstall wipes the disk (backups taken before it are kept). The panel has no ISO upload, so the installation-media upgrade above is not available on our servers.
• The Windows Update route to 2025 needs a Windows Server 2025 licence of your own, and we have not tried it on our templates. If you do, take a snapshot first so you can roll back from the panel.
• On the evaluation licence? New servers run Windows on a time-limited evaluation until you activate your own key. Convert to your key before any upgrade; converting the evaluation with DISM has the steps.

Sources

All checked on 21.10.2026:

• Microsoft Lifecycle: Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, Windows Server 2022, Windows Server 2025
• Microsoft: Fixed Lifecycle Policy
• Microsoft: Product Lifecycle FAQ, Extended Security Updates
• Microsoft: Plan your Windows Server upgrade path and Upgrade Windows Server in place

Frequently asked