Windows Server End of Support Dates by Version
Windows Server end of support dates: 36 versions are listed below. 28 are already past Microsoft's end of support, most recently Windows Server 23H2 AC on May 12, 2026; the next to end is Windows Server 2016 (LTSC) on Jan 12, 2027. Microsoft sells Microsoft Extended Security Updates (ESU) for a limited period after that date. Third-party support keeps any of these versions in production after the vendor date, with 24x7 incident response, vulnerability mitigation and compliance documentation, typically at 40-70% below the vendor's renewal.
Windows Server versions and end of support dates
"Vendor end of support" is the date Microsoft stops free fixes and security updates. "Extended end" is the end of the paid extension where Microsoft offers one. Each version links to its own page and quote form.
Why Windows Server versions stay in production
Windows Server versions outlive their support dates in every estate because the application on top of them is the thing nobody wants to touch: a line-of-business system, a file server with a decade of permissions, a domain controller in a remote site.
Microsoft's answer is Extended Security Updates, priced per core and doubling each year. Third-party support is the alternative for servers you intend to keep running while a migration or decommission is planned.
How Microsoft's support lifecycle works for Windows Server
Microsoft publishes a Fixed Lifecycle policy for on-premises server and desktop products: five years of Mainstream Support, five years of Extended Support, and for some products paid Extended Security Updates (ESU) for up to three further years. Mainstream end stops feature updates and non-security fixes; Extended end stops free security updates.
ESU is per-device or per-core, priced to rise each year, and buys security patches only. It is usually the comparison point for third-party support on an estate you intend to keep running.
What changes on the end of support date
- Microsoft stops free security updates and non-security fixes for the version.
- ESU becomes the only source of Microsoft security patches, for up to three years at rising per-core prices.
- The servers, roles and applications keep running; compliance frameworks start asking for a plan.
Your options after Windows Server end of support
1. Upgrade to a supported version
Right when the application above it is ready and the budget exists. Wrong as a forced move: an upgrade driven by a support date rather than a business need is where regression bugs and surprise licence costs come from.
2. Buy Microsoft Extended Security Updates (ESU)
Microsoft's paid extension buys more time at a price that rises each year and typically covers security fixes only. It keeps the deadline in place and is often the most expensive line in the renewal.
3. Third-party support
Replaces the vendor contract with ours for the versions you run, with no deadline. For Windows Server that covers:
- Operating system, Active Directory, Hyper-V, clustering, file and print incidents, 24x7
- Hardening and compensating controls for new vulnerabilities when patches are not available
- Compliance evidence: supported-status letters and patch-posture documentation
- Migration planning to a current Windows Server release or to cloud
Not included: new vendor patches or licences. Those stay with Microsoft; everything operational moves to us.
Windows Server end of support: frequently asked questions
Which Windows Server versions are out of support?
Windows Server 2012 (LTSC) (Oct 10, 2023), Windows Server 2012 R2 (LTSC) (Oct 10, 2023), Windows Server 23H2 AC (May 12, 2026), Windows Server Core 2012-R2 (LTSC) (Oct 10, 2023), Windows Server Core 2012 (LTSC) (Oct 10, 2023), Windows Server 2008 R2 SP1 (LTSC) (Jan 14, 2020), Windows Server 2008 SP2 (LTSC) (Jan 14, 2020), Windows Server Core 20H2 (Aug 9, 2022) and 20 earlier versions. All of them can be covered by third-party support.
Is third-party support a replacement for Windows Server ESU?
It is an alternative. ESU delivers Microsoft security patches only; third-party support delivers incident response, hardening and compliance documentation. Some customers combine ESU for internet-facing servers with third-party support for the rest.
Can we keep Windows Server 2012 R2 or 2016 in production after end of support?
Yes. The licence does not expire. Third-party support keeps those servers covered with 24x7 incident response and vulnerability mitigation while you plan the migration.
What does third-party support for Windows Server cost?
Typically 40 to 70% below the vendor renewal or extended-support price for the same versions, priced per instance, server or core depending on the product. We return an indicative price within 24 hours and a firm quote within 48.
How do we move Windows Server to third-party support without a gap?
Start before the vendor renewal date: inventory versions and instances, download all media and fixes you are entitled to, confirm no bundled contract depends on the renewal, then let the vendor support lapse as ours starts. We handle the hand-over checklist with you.
Version-by-version guides
- Windows Server 2016 EOL: Action Plan for Jan 2027 (Oct 12, 2026)
- Windows Server 2016 EOL: 6 Months to Jan 12, 2027 (Jul 15, 2026)
- Windows Server 2016 EOL Jan 12, 2027: 3 Options Compared (Apr 12, 2026)
- Windows Server 2016 (LTSC) EOL January 2027 – Plan Now (Dec 12, 2025)
- Windows Server 23H2 AC EOL – Third-Party Support Options (Oct 24, 2025)
- Windows Server 23H2 AC: EOL Action Plan (Oct 24, 2025) (Jul 24, 2025)
- Windows Server 23H2 AC EOL Oct 24, 2025 — Migration Timeline (Apr 24, 2025)
- Windows Server 23H2 AC EOL Oct 2025: Three Exit Options (Jan 24, 2025)