Windows Server End of Life: Every Version's Dates, the October 13 Double Deadline, and 2016's January Cliff
Two Windows Server clocks run out on the same day this autumn. On October 13, 2026, the third and final year of Extended Security Updates for Windows Server 2012 and 2012 R2 ends — and Windows Server 2022 leaves mainstream support the same Patch Tuesday. Ninety-one days later, on January 12, 2027, Windows Server 2016 reaches the end of extended support. Between those two dates a very large share of the world's on-premises Windows estate changes support status within a single quarter.
This page is the reference for all of it: every Long-Term Servicing Channel release from Windows Server 2000 to Windows Server 2025 with its release, mainstream, extended and ESU dates; the short-lived Semi-Annual and Annual Channel releases; the in-place upgrade paths Microsoft actually supports; how to identify the version you are running; and what to do when a version's date arrives. Per-version detail lives on the Windows Server lifecycle page.
Key Dates at a Glance
- Windows Server 2012 R2: extended support ended 2023-10-10; final ESU patches end 2026-10-13
- Windows Server 2012: extended support ended 2023-10-10; final ESU patches end 2026-10-13
- Windows Server 2016: mainstream support ended 2022-01-11; extended support ends 2027-01-12
- Windows Server 2019: mainstream support ended 2024-01-09; extended support ends 2029-01-09
- Windows Server 2022: mainstream support ends 2026-10-13; extended support ends 2031-10-14
- Windows Server 2025: mainstream support ends 2029-11-13; extended support ends 2034-11-14
- Windows Server Annual Channel 23H2: end of life 2026-05-12
Windows Server EOL Risk Scores
An end-of-life date on its own does not tell you how urgent a version is. We publish an EOL Risk Score (0–100) for every tracked version, combining four factors: how long past — or how close to — end of life it is, the attack surface of the software class, whether CISA lists the product in its Known Exploited Vulnerabilities catalog, and whether commercial extended support exists. Windows Server is a server operating system named in CISA's KEV catalog, so even fully supported versions start from an elevated baseline.
| Version | EOL Risk Score | What drives it |
|---|---|---|
| Windows Server 2012 R2 | 90 | Extended support ended October 10, 2023 (recency factor at maximum); server-OS attack surface; CISA KEV exposure. ESU coverage ends October 13, 2026. |
| Windows Server 2012 | 90 | Same lifecycle as 2012 R2 — and 2012 (non-R2) cannot upgrade in place beyond Windows Server 2016. |
| Windows Server 2016 | 58 | Extended support ends January 12, 2027; the recency factor climbs every month as that date approaches. |
| Windows Server 2019 | 50 | Extended support to January 9, 2029; score reflects attack surface and KEV exposure, not lifecycle urgency. |
| Windows Server 2022 | 50 | Extended support to October 14, 2031; same baseline as 2019. |
| Windows Server 2025 | 50 | Current release, supported to November 14, 2034; the baseline for a server OS in the KEV catalog. |
Two things worth reading out of these numbers. First, a supported version is not a zero-risk version — Windows Server 2019, 2022 and 2025 all score in the elevated band despite years of support remaining, because a server operating system carries a large attack surface and Windows Server appears in CISA's actively-exploited catalog. Second, Windows Server 2012 and 2012 R2 sit in the critical band because their recency factor has been at maximum since October 2023; ESU has kept them patched but does not change how far past end of life they are. Scores update automatically at every site build as dates pass and the KEV catalog changes; the methodology is on the EOL Risk Score page.
Every Windows Server Version: Release, Mainstream, Extended and ESU Dates
Long-Term Servicing Channel releases. Dates are Microsoft's Patch Tuesdays as published on the Microsoft Lifecycle site; ESU dates are from Microsoft's Extended Security Updates FAQ.
| Version | Released | Mainstream ends | Extended ends | ESU ends | Status (Aug 2026) |
|---|---|---|---|---|---|
| Windows Server 2025 | Nov 1, 2024 | Nov 13, 2029 | Nov 14, 2034 | — | Mainstream |
| Windows Server 2022 | Aug 18, 2021 | Oct 13, 2026 | Oct 14, 2031 | — | Mainstream |
| Windows Server 2019 | Nov 13, 2018 | Jan 9, 2024 | Jan 9, 2029 | Not announced | Extended (security only) |
| Windows Server 2016 | Oct 15, 2016 | Jan 11, 2022 | Jan 12, 2030 | Program confirmed; year dates not yet published | Extended (security only) |
| Windows Server 2012 R2 | Nov 25, 2013 | Oct 9, 2018 | Oct 13, 2026 | Oct 13, 2026 | EOL — ESU only |
| Windows Server 2012 | Oct 30, 2012 | Oct 9, 2018 | Oct 13, 2026 | Oct 13, 2026 | EOL — ESU only |
| Windows Server 2008 R2 SP1 | Feb 22, 2011 | Jan 13, 2015 | Jan 10, 2023 | Jan 10, 2023 (year 4 Azure-only: Jan 9, 2024) | EOL |
| Windows Server 2008 SP2 | Apr 29, 2009 | Jan 13, 2015 | Jan 10, 2023 | Jan 10, 2023 (year 4 Azure-only: Jan 9, 2024) | EOL |
| Windows Server 2003 SP2 | Mar 13, 2007 | Jul 13, 2010 | Jul 14, 2015 | — | EOL |
| Windows Server 2003 | Apr 24, 2003 | Apr 10, 2007 (superseded by SP1/SP2) | Jul 14, 2015 (as SP2) | — | EOL |
| Windows Server 2000 | Feb 17, 2000 | Jun 30, 2005 | Jul 13, 2010 | — | EOL |
Two corrections to a common misreading of this table. Windows Server 2016's extended support ends in January 2027 — a later ESU end date, when Microsoft publishes it, is not “support” and does not move the end-of-life date. And Windows Server 2012 R2 has been end of life since October 2023: October 13, 2026 is the last day of a paid bridge, not the EOL date.
Understanding the Windows Server Lifecycle
Every LTSC release of Windows Server follows Microsoft's Fixed Lifecycle Policy: a minimum of ten years of support, split into two five-year phases, with an optional paid tail.
| Phase | Length | What you get |
|---|---|---|
| Mainstream support | 5 years from release | Security updates, non-security fixes, new features, design changes, and the ability to open support requests. Windows Server 2022 leaves this phase October 13, 2026. |
| Extended support | 5 further years | Security updates only. No new features, no non-security fixes except through paid programs. Windows Server 2016 (to January 12, 2027) and 2019 (to January 9, 2029) are here now. |
| End of extended support | — | The end-of-life date. No further updates of any kind without ESU. This is the date to plan against. |
| Extended Security Updates (ESU) | Up to 3 years, sold annually | Critical and Important security updates only, no technical support. Free for eligible Azure VMs; 100% of the full license price per year on-premises. Not offered for every version, and never automatic. |
Microsoft's dates are always its monthly Patch Tuesday, which is why so many Windows Server milestones share a calendar day with Windows, SQL Server and Exchange milestones — and why October 13, 2026 carries more than one deadline.
October 13, 2026: The Double Deadline
Two things happen to Windows Server on that Patch Tuesday, and a third to the desktop estate that usually sits beside it.
Windows Server 2012 and 2012 R2: the last ESU patch. Extended support ended October 10, 2023. Microsoft sold three annual ESU periods — year one to October 8, 2024, year two to October 14, 2025, year three to October 13, 2026 — and has been explicit that year three is the end. After it, no channel exists for security fixes to 2012 or 2012 R2, including in Azure. The full story, including the Azure detail teams get wrong, is in the Windows Server 2012 ESU cliff; the decision framework is in Windows Server 2012: migrate, ESU, or move to cloud?.
Windows Server 2022: mainstream support ends. This is not end of life — extended support runs to October 14, 2031 — but it is the end of new features and non-security fixes. Teams that took 2022 as their “stable for a decade” platform in 2021 now have a version that is security-only for the second half of that decade, which is the normal Fixed Lifecycle shape but worth knowing before a 2027 hardware refresh assumes otherwise.
Windows 10: first ESU year ends. Windows 10's own ESU program runs to October 10, 2028 for organisations that keep paying, but year one closes the same day. If your Windows Server 2012 hosts and your Windows 10 fleet are in the same budget line, October 2026 is when both invoices change.
Windows Server 2016 — End of Extended Support January 12, 2027
Windows Server 2016 (build 10.0.14393) was released October 15, 2016. Mainstream support ended January 11, 2022; extended support ends January 12, 2027. It has been security-fixes-only for over four years, and it is the version most likely to still be running line-of-business applications that were “temporarily” left behind during the 2019/2022 rollouts.
Microsoft has confirmed that Extended Security Updates for Windows Server 2016 begin when extended support ends. Under Microsoft's ESU policy that means up to three annual periods of Critical and Important security fixes, priced on-premises at 100% of the full license price per year, free for eligible Azure virtual machines, and purchasable either as annual volume-licensing SKUs or monthly through Azure Arc-enabled servers. As of this article's date, Microsoft's lifecycle FAQ has not yet published the per-year end dates for 2016 ESU; when it does, we will add them here and to the Windows Server 2016 page. Do not plan on ESU being cheaper than the 2012 program was — Microsoft moved to flat 100%-per-year pricing with 2012 and has kept it.
The upgrade path is unusually forgiving: Windows Server 2016 can upgrade in place to 2019, 2022, or directly to 2025 (see the upgrade-path table below), and the 2025 target keeps the destination in mainstream support until November 2029. Application and agent compatibility, not the OS upgrade itself, is the schedule driver — which is why a January 2027 deadline makes the autumn of 2026 the testing window, not the planning window.
Windows Server 2019 — Extended Support to January 9, 2029
Windows Server 2019 (build 10.0.17763) was released November 13, 2018. Mainstream support ended January 9, 2024; extended support ends January 9, 2029. No ESU program has been announced. It upgrades in place to 2022 or 2025, from media or — for the 2025 target — as a feature update through Windows Update once the prerequisite cumulative update is installed. It is on the roadmap, not the emergency list; the sensible plan is to fold it into whatever 2025 migration the 2016 deadline forces.
Windows Server 2022 — End of Life October 14, 2031 (Mainstream Ends October 13, 2026)
Windows Server 2022 (build 10.0.20348) was released August 18, 2021. Its end-of-life date — the end of extended support — is October 14, 2031. The nearer deadline is mainstream support, which ends October 13, 2026: from that Patch Tuesday, 2022 receives security fixes only — no new features, no non-security bug fixes, no design-change requests — for its remaining five extended years.
In plain terms: Windows Server 2022 is safe to run for years yet, but from October 2026 it is a maintenance-mode platform. It upgrades in place only to 2025, so any workload you expect to keep past the decade mark has exactly one hop available. Provisioning something new today? Choose 2025 instead and skip a future migration.
Windows Server 2025 — End of Life November 14, 2034
Windows Server 2025 (build 10.0.26100) was released November 1, 2024. Mainstream support runs to November 13, 2029; extended support — the end-of-life date — is November 14, 2034. It is the current release, the only version with new features still arriving, and — because it accepts in-place upgrades from up to four versions back — the natural landing zone for every consolidation project the 2016 and 2012 deadlines are forcing. Windows Server 2025 also introduced hotpatching for Datacenter: Azure Edition and, as a paid subscription, for on-premises Standard and Datacenter, which reduces reboot-requiring security updates to a handful per year.
Windows Server 2012, 2012 R2, 2008 and Older — End of Life
Windows Server 2012 R2 (build 6.3.9600, released November 25, 2013) and Windows Server 2012 (build 6.2.9200, released October 30, 2012) share a lifecycle: mainstream ended October 9, 2018, extended ended October 10, 2023, and ESU ends October 13, 2026. One difference matters for migration: 2012 R2 can upgrade in place to 2016, 2019 or 2025, while original 2012 can only reach 2012 R2 or 2016 — a 2012 host bound for 2025 must hop through 2016 first or be rebuilt.
Windows Server 2008 R2 SP1 and 2008 SP2 reached end of extended support January 14, 2020, and their ESU ended January 10, 2023 on-premises, with a fourth Azure-only year to January 9, 2024. Windows Server 2003 ended July 14, 2015 and Windows Server 2000 July 13, 2010. Anything in this section still running in 2026 is a documented, actively-targeted risk with no patch path at all; the only options are isolation and replacement.
Semi-Annual and Annual Channel Releases
Alongside the LTSC releases, Microsoft shipped short-lived Server Core-only releases on an 18-month lifecycle. All are end of life. Windows Server, version 1709 through 20H2 were the Semi-Annual Channel; 23H2 was the first (and so far only) release of the Annual Channel for container hosts.
| Release | Channel | Released | End of life |
|---|---|---|---|
| Windows Server, version 23H2 | Annual Channel | Oct 24, 2023 | May 12, 2026 |
| Windows Server, version 20H2 | Semi-Annual | Oct 20, 2020 | Aug 9, 2022 |
| Windows Server, version 2004 | Semi-Annual | May 27, 2020 | Dec 14, 2021 |
| Windows Server, version 1909 | Semi-Annual | Nov 12, 2019 | May 11, 2021 |
| Windows Server, version 1903 | Semi-Annual | May 21, 2019 | Dec 8, 2020 |
| Windows Server, version 1809 | Semi-Annual | Nov 13, 2018 | Nov 10, 2020 |
| Windows Server, version 1803 | Semi-Annual | Apr 30, 2018 | Nov 12, 2019 |
| Windows Server, version 1709 | Semi-Annual | Oct 17, 2017 | Apr 9, 2019 |
Supported In-Place Upgrade Paths
From Microsoft's upgrade-path table for installation media, non-clustered servers. Windows Server 2025 accepts upgrades from up to four versions back; 2022 and earlier targets accept two. Cluster OS rolling upgrades move one version at a time regardless of target.
| Upgrade from ↓ / to → | 2012 R2 | 2016 | 2019 | 2022 | 2025 |
|---|---|---|---|---|---|
| Windows Server 2012 | Yes | Yes | No | No | No |
| Windows Server 2012 R2 | — | Yes | Yes | No | Yes |
| Windows Server 2016 | — | — | Yes | Yes | Yes |
| Windows Server 2019 | — | — | — | Yes | Yes |
| Windows Server 2022 | — | — | — | — | Yes |
Restrictions worth knowing before you start: an in-place upgrade keeps the edition (Standard stays Standard unless you step up to Datacenter during the upgrade — never down); you cannot switch between Server Core and Desktop Experience during an upgrade; NIC Teaming must be disabled first; and boot-from-VHD and Windows Storage Server installs are not upgradeable in place. Each Windows Server upgrade requires its own license.
How to Check Your Windows Server Version
Any of these works on every version listed above:
winver— opens the About dialog with version and build.systeminfo | findstr /B /C:"OS Name" /C:"OS Version"at a command prompt.Get-ComputerInfo | Select-Object WindowsProductName, OsVersion, OsBuildNumberin PowerShell.
Map the build number to the version: 6.2.9200 = 2012 · 6.3.9600 = 2012 R2 · 10.0.14393 = 2016 · 10.0.17763 = 2019 · 10.0.20348 = 2022 · 10.0.26100 = 2025. Across a fleet, the same fields come from your configuration-management or RMM tooling; the EOL Checker takes the version and returns its status and dates.
What Happens When Windows Server Support Ends
Nothing stops working on the day — and that is the problem. The server keeps running exactly as before, while every vulnerability disclosed after the date stays open on it. For a server operating system in CISA's Known Exploited Vulnerabilities catalog, that is not a theoretical exposure: Windows Server flaws are actively used in ransomware intrusions, and an unpatched domain controller, file server or RDS host is precisely the foothold those campaigns look for. Compliance follows the same logic — PCI DSS, HIPAA, ISO 27001, NIS2 and cyber-insurance questionnaires all treat unsupported operating systems as a control failure, not a risk to be accepted quietly. And Microsoft support ends with the product: without ESU you cannot open a ticket even with a paid support plan.
Your Options When a Windows Server Version Reaches End of Life
- Upgrade in place. The cheapest path where the roles support it — and with 2025 accepting 2012 R2 and later directly, most estates now have a single-hop route. Test applications and agents first; back up before you start.
- Rebuild and migrate. New servers on 2025, roles and data moved across. More work, cleaner result, and the only option for 2012 (non-R2) hosts that need to reach 2025.
- Buy Extended Security Updates. Where Microsoft offers them (2016 from January 2027; 2012/R2 until October 13, 2026): Critical and Important fixes only, no support, 100% of the license price per year on-premises, requires Software Assurance or an equivalent subscription, and years cannot be skipped. A bridge with a hard end, not a plan.
- Move the workload to Azure. Eligible Azure VMs, Azure Stack, Azure VMware Solution and Nutanix Cloud Clusters on Azure receive ESU at no additional charge for the ESU period — Microsoft's intended escape hatch, and the reason so many 2012 estates went to Azure in 2023.
- Third-party support and isolation. Independent vendors sell security patches for Windows Server versions past their Microsoft dates; where a system genuinely cannot move, network isolation plus third-party patching is the defensible interim. See the extended support options page for how these programs work.
The right choice usually comes down to how many more years the system has to run: under a year, a bridge; one to three, migrate once; indefinitely, migrate now and put the next date in the calendar. The Windows Server 2012 decision guide walks the trade-offs with costs.
Windows Server currently carries an EOL Risk Score™ of 80/100 — Grade D, high risk, recalculated at every site build from EOL recency, attack surface, CISA KEV exposure, and extended-support availability. Per-version scores and dates are on the Windows Server lifecycle page.
The right response comes down to one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support fees paid repeatedly cost more than doing the project once. Indefinitely, migrate now and plan the next one before it surprises you. Extended support is often the more expensive choice over a multi-year horizon — a bridge, not a destination. And if this deadline feels like vendor caprice, it isn’t — why end of life is inevitable for every version, with the receipts.
Frequently Asked Questions
When does Windows Server 2016 reach end of life?
Windows Server 2016 reaches the end of extended support on January 12, 2027. Mainstream support ended January 11, 2022, so it has received security fixes only for the past four years. Microsoft has confirmed that Extended Security Updates for Windows Server 2016 begin when extended support ends; ESU is a maximum of three years and is a paid bridge, not an extension of the product's lifecycle.
Is Windows Server 2012 R2 still supported in 2026?
Not in the normal sense — extended support ended October 10, 2023. Organizations that bought all three years of Extended Security Updates receive critical and important security fixes until October 13, 2026. After that date there is no Microsoft-sanctioned way to patch Windows Server 2012 or 2012 R2, on-premises or in Azure.
What happens on October 13, 2026?
Two Windows Server clocks run out on the same Patch Tuesday: the third and final year of Extended Security Updates for Windows Server 2012 and 2012 R2 ends, and Windows Server 2022 leaves mainstream support and enters its five-year extended phase (security fixes only, until October 14, 2031). Windows 10's first ESU year ends the same day.
Which Windows Server versions are fully supported today?
Windows Server 2025 (mainstream to November 13, 2029, extended to November 14, 2034) and Windows Server 2022 (mainstream to October 13, 2026, extended to October 14, 2031). Windows Server 2019 is in extended support until January 9, 2029, and Windows Server 2016 until January 12, 2027 — both receive security fixes but no new features or non-security fixes.
How long does Microsoft support each Windows Server version?
Long-Term Servicing Channel releases follow the Fixed Lifecycle Policy: five years of mainstream support followed by five years of extended support, ten years in total. Extended Security Updates, where Microsoft offers them, add up to three further years of critical and important security fixes for a fee — free only for eligible virtual machines running in Azure.
Can I upgrade Windows Server 2012 R2 directly to Windows Server 2025?
Yes. Starting with Windows Server 2025, non-clustered servers can upgrade in place across up to four versions at once, so Windows Server 2012 R2, 2016, 2019 and 2022 can all upgrade directly to 2025 from installation media. Windows Server 2022 and earlier targets allow only two versions per hop, and cluster OS rolling upgrades advance one version at a time. Original Windows Server 2012 (not R2) can only upgrade in place to 2012 R2 or 2016.
How much do Windows Server Extended Security Updates cost?
On-premises and in hosted environments, Microsoft prices Windows Server ESU at 100% of the full license price per year, for each of up to three years, and you cannot buy year two or three without having bought the prior years. Eligible virtual machines running in Azure (including Azure Stack, Azure VMware Solution and Nutanix Cloud Clusters on Azure) receive ESU at no additional charge. Azure Arc-enabled servers can pay monthly instead of buying annual licenses.
How do I check which Windows Server version I am running?
Run winver, or systeminfo | findstr /B /C:"OS Name" /C:"OS Version" at a command prompt, or Get-ComputerInfo | Select-Object WindowsProductName, OsVersion in PowerShell. The build number tells you the version: 6.2.9200 is 2012, 6.3.9600 is 2012 R2, 10.0.14393 is 2016, 10.0.17763 is 2019, 10.0.20348 is 2022 and 10.0.26100 is 2025.
Related Resources
- Windows Server lifecycle page — live status, dates and risk scores for every version
- Windows Server 2012 & 2012 R2 ESU cliff: the final deadline is October 13, 2026
- October 13, 2026 — the day three Windows support clocks run out — the triple-deadline triage guide
- Windows Server 2012: migrate, ESU, or move to cloud? — the decision guide
- Windows 10 end of life — the desktop ESU that shares the October 13 date
- SQL Server 2016 end of life — the database usually sitting on these hosts
- EOL Watch — the deadline calendar · EOL Checker · EOL Risk Score methodology