November 10, 2026: Four Support Clocks Run Out on One Patch Tuesday
Microsoft's release arithmetic has stacked four endings onto one day. On November 10, 2026: .NET 8, the long-term-support runtime that most production .NET now runs on, reaches end of life; .NET 9, the eighteen-month release that followed it, ends the same day, so skipping 8 for 9 bought nothing; PowerShell 7.4 and 7.5 go with the runtimes they are built on; and Windows 11 23H2 for Enterprise and Education stops being serviced. Two of these are patch-stops with no Microsoft extension. Here is which is which.
Key Dates at a Glance
- .NET 8 (LTS) — released November 14, 2023; end of life November 10, 2026. No Microsoft extended support; the supported path is .NET 10.
- .NET 9 (STS) — released November 12, 2024; end of life November 10, 2026, the same day.
- .NET 10 (LTS) — the destination: released November 11, 2025, supported until November 14, 2028.
- PowerShell 7.4 (LTS) and 7.5 — both end November 10, 2026. PowerShell 7.6 (LTS), released March 18, 2026, runs to November 14, 2028.
- Windows 11 23H2, Enterprise and Education — end of servicing November 10, 2026 (Home and Pro 23H2 ended November 11, 2025). 24H2 Enterprise and Education runs to October 12, 2027.
- The same fortnight — OpenSSL 3.6 and the Exchange 2016/2019 ESU end November 1, 2026; Rails 8.0 leaves security support November 7, 2026; PostgreSQL 14 reaches end of life November 12, 2026.
.NET 8: the LTS that most of production is standing on
This is the emergency tier. .NET 8 shipped on November 14, 2023 as a long-term-support release, and LTS in .NET means three years, not five: support ends November 10, 2026. Microsoft has no Extended Security Update program for .NET the way it has for Windows, so after that Patch Tuesday a .NET 8 application receives no security fixes from Microsoft at any price. Because 8 was the LTS in the cycle, it is the runtime that most enterprise services, container images and build agents standardised on through 2024 and 2025 — which makes November 10 less a version retirement than a fleet event. The in-place path is .NET 10, the current LTS (released November 11, 2025, supported until November 14, 2028); the mechanics, breaking changes and container-image consequences are in our .NET 8 and .NET 9 double-cutoff guide, and every version's dates are in the .NET end-of-life reference.
.NET 9: the same day, on purpose
.NET 9 was the standard-term release that followed 8 — released November 12, 2024 and supported for eighteen months, which is exactly how it lands on November 10, 2026, the same date as its predecessor. Microsoft's cadence is designed so that an STS release never outlives the LTS before it, and this is the first cycle where that design lands on a single day for both. The practical consequence: a team that moved from 8 to 9 to get newer features did not buy a longer runway. Both go together, and the only supported destination for either is .NET 10.
PowerShell 7.4 and 7.5: they end when their runtime ends
PowerShell 7 is built on .NET, and each PowerShell release inherits the support window of the .NET version underneath it. PowerShell 7.4 (LTS) sits on .NET 8 and PowerShell 7.5 on .NET 9, so both reach end of life on November 10, 2026. Scripts do not stop running, but the engine stops receiving security fixes, and PowerShell is the tool that runs with the highest privileges on most Windows estates. The replacement is PowerShell 7.6, the LTS line on .NET 10, released March 18, 2026 and supported until November 14, 2028. Windows PowerShell 5.1, the version shipped inside Windows, is unaffected by this date and follows the operating system's lifecycle instead.
Windows 11 23H2 for Enterprise and Education: end of servicing
The fourth clock is the fleet one. Windows 11 version 23H2 reached end of servicing for Home and Pro editions on November 11, 2025; Enterprise and Education editions get 36 months, and their window closes on November 10, 2026. A device still on 23H2 after that stops receiving monthly security updates until it takes a feature update. There is no ESU for a Windows 11 feature version — the fix is the free move to 24H2 (Enterprise and Education serviced to October 12, 2027) or to 25H2, not a purchase. Unlike the two .NET endings, this one is solved by update management rather than engineering work, which is why it belongs at the bottom of the triage order rather than the top.
The same fortnight: four more dates within days
November 10 sits in the middle of a crowded two weeks. Nine days earlier, on November 1, 2026, OpenSSL 3.6 reaches end of life and Exchange Server 2016 and 2019 lose their Extended Security Update coverage. Three days before, on November 7, 2026, Rails 8.0 leaves security support. Two days after, on November 12, 2026, PostgreSQL 14 reaches end of life — the database version a great deal of .NET 8-era infrastructure was provisioned against. An organisation working the November 10 list should plan the whole fortnight as one maintenance window; the individual guides are linked below.
Nine weeks out: the triage order
- .NET 8 and .NET 9 applications — act now. Inventory every runtime, container base image and self-contained deployment; move to .NET 10 where the code allows, and get third-party extended-support quotes for whatever genuinely cannot be rebuilt before November 10, 2026.
- PowerShell 7.4 / 7.5 — same project. Automation hosts, CI agents and jump servers move to PowerShell 7.6 alongside the runtime upgrade; the two ship together for a reason.
- Windows 11 23H2 Enterprise / Education — schedule the feature update. A servicing-ring change, not an engineering task; make sure the ring completes before November 10, 2026.
- The fortnight around it — calendar it. OpenSSL 3.6 and Exchange ESU on November 1, 2026, Rails 8.0 on November 7, 2026, PostgreSQL 14 on November 12, 2026.
Not sure what you're running? Paste your dependency list or SBOM into our free stack scanner — it checks every line against the same lifecycle data this page is built on, in your browser, with nothing uploaded.