Windows Server 2025 End of Life: November 14, 2034 (Extended Support)
Windows Server 2025 reaches end of life (EOL) on November 14, 2034. That is the end of extended support on Microsoft's product lifecycle page and the last day Microsoft ships a security update for it. The date that arrives first is the end of mainstream support, on November 13, 2029. From then on the release receives security updates and nothing else: no new features, no non-security fixes, no design changes. The release shipped on November 1, 2024 under Microsoft's Fixed Lifecycle Policy, which covers the Datacenter, Datacenter: Azure Edition, Essentials and Standard editions.
The dates, in one table
| Milestone | Date | What it means |
|---|---|---|
| Release | November 1, 2024 | Start of the fixed lifecycle |
| End of mainstream support | November 13, 2029 | New features and non-security fixes stop |
| End of extended support (end of life) | November 14, 2034 | Last security update |
Microsoft's page lists one set of dates for the whole release and four editions: Datacenter, Datacenter: Azure Edition, Essentials and Standard. It shows the dates in Pacific Time.
How the support lifecycle works
Windows Server 2025 is a Long-Term Servicing Channel release. Microsoft's servicing channels documentation describes that channel as five years of mainstream support followed by five years of extended support, installable as Server Core or Server with Desktop Experience. The two phases differ in one way that matters for planning:
- Mainstream support, until November 13, 2029: security updates, non-security fixes and new features.
- Extended support, until November 14, 2034: security updates only. A bug that is broken but not exploitable is not something to expect a fix for in this phase.
After the end-of-life date the release receives no further security updates under the standard lifecycle.
No Extended Security Updates are listed
Microsoft's lifecycle page for Windows Server 2025 lists a mainstream end date and an extended end date, and no Extended Security Updates program. Do not plan on one unless Microsoft publishes it. Treat November 14, 2034 as the real deadline.
Windows Server 2025 next to the earlier releases
Every supported release follows the same two-phase pattern. The neighbours' dates set the order of work in a mixed estate; each has its own guide.
| Release | Released | Mainstream support end | Extended support end |
|---|---|---|---|
| Windows Server 2025 | November 1, 2024 | November 13, 2029 | November 14, 2034 |
| Windows Server 2022 | August 18, 2021 | October 13, 2026 | October 14, 2031 |
| Windows Server 2019 | November 13, 2018 | January 9, 2024 | January 9, 2029 |
| Windows Server 2016 | October 15, 2016 | January 11, 2022 | January 12, 2027 |
Older releases and the full version list are in our guide to every Windows Server version.
Upgrading to Windows Server 2025
Windows Server 2025 widened the in-place upgrade window. Microsoft's upgrade documentation says nonclustered systems can now upgrade up to four versions at a time, so a server on Windows Server 2012 R2, 2016, 2019 or 2022 can go directly to 2025 from installation media. Three conditions from the same page:
- Clusters move one version at a time. A Cluster OS rolling upgrade cannot skip releases.
- The Windows Update route is narrower. Microsoft lists it for Windows Server 2019 and 2022 only, with the required cumulative update installed first.
- Each upgrade needs its own license, and not every role supports an in-place upgrade. Check Microsoft's role and feature matrix before choosing between an upgrade and a migration.
Hotpatching, which installs security updates without a restart, is available on Windows Server 2025. Microsoft's Hotpatch documentation lists it for the Datacenter: Azure Edition images on Azure and Azure Local, and for Azure Arc-connected machines running the Standard or Datacenter edition.
What to do with this
- Make 2025 the default for new builds. Its support dates run later than those of any other Windows Server release in the table above.
- Send servers leaving older releases here. A server leaving 2016 or 2019 can reach 2025 in one in-place step.
- Put both dates in the asset register. November 13, 2029 is when feature and non-security work stops; November 14, 2034 is when security updates stop.
- Check the rest of the stack in the same pass. The database, the runtime and the agents on the server each have their own dates. Our EOL Checker and API answer those.
Frequently Asked Questions
When is Windows Server 2025 end of life?
Windows Server 2025 reaches the end of extended support on November 14, 2034, per Microsoft's product lifecycle page. That is the last day Microsoft ships security updates for it.
When does Windows Server 2025 mainstream support end?
Mainstream support for Windows Server 2025 ends on November 13, 2029. After that date Microsoft ships security updates only: no new features, no non-security fixes and no design changes, for the five years of extended support that follow.
Is Windows Server 2025 still supported?
Yes. It is in mainstream support until November 13, 2029 and in extended support, with security updates only, until November 14, 2034.
Is there an ESU for Windows Server 2025?
Microsoft's lifecycle page for Windows Server 2025 lists a mainstream end date and an extended end date and no Extended Security Updates program. Plan on the extended support end date as the real deadline.
Which versions can upgrade in place to Windows Server 2025?
Per Microsoft's upgrade documentation, nonclustered systems can upgrade directly to Windows Server 2025 from Windows Server 2012 R2 and later, which covers 2012 R2, 2016, 2019 and 2022. A Cluster OS rolling upgrade can advance only one version at a time.
Related
- Windows Server 2025 — the live status page with its EOL Risk Score
- Windows Server · Windows Server End of Life — every version's dates and the supported in-place upgrade paths
- Windows Server 2022 End of Life, Windows Server 2019 End of Life and Windows Server 2016 End of Life — the nearer deadlines
- How we verify our dates — the rules every number on this site is held to