Illustrative image: the .NET logo. Image: Wikimedia Commons.
TL;DR — .NET 8 end of support November 2026 lands on November 10: Microsoft stops security patches for .NET 8 and .NET 9 on the same day, so move to .NET 10 LTS — supported until November 14, 2028 — before the deadline, not after it.
UPDATE — 10 November 2026: the deadline is today. .NET 8 and .NET 9 support ends today, 10 November 2026 — Microsoft will ship no further security patches for either runtime. .NET 11's general-availability announcement is expected at the .NET Conf keynote later today (8 AM PST / 9:30 PM IST); this post will be updated when Microsoft confirms it. .NET 10 LTS, supported until 14 November 2028, remains the recommended move.
📌 KEY HIGHLIGHTS
- The deadline: .NET 8 (LTS) and .NET 9 (STS) both reach end of support on November 10, 2026, per Microsoft's official .NET support policy, last updated October 25, 2026.
- What stops: security fixes, servicing updates and Microsoft technical support for both runtimes. Your apps keep running — but every vulnerability found after November 10 stays unpatched.
- The safe target: .NET 10, the current Long Term Support release, supported until November 14, 2028. Do not wait for .NET 11 — it is a shorter-support STS release.
- Why both end together: .NET 9's STS support was extended from 18 to 24 months during its life, so the 2023 LTS and the 2024 STS land on the same Patch Tuesday.
- Don't confuse the two .NETs: the deadline applies to modern, cross-platform .NET only — .NET Framework 4.8 follows its Windows lifecycle and is not ending on November 10.
.NET 8 end of support November 2026: what ends, and when
Microsoft's .NET support policy table is unambiguous. .NET 8 shipped on November 14, 2023 as a Long Term Support release with three years of patches; .NET 9 shipped on November 12, 2024 as a Standard Term Support release with two. Both are now in the maintenance phase — security fixes only since May 2026 — and both stop on November 10, 2026, a Patch Tuesday. The latest patches, released October 25, 2026, are .NET 8.0.33, 9.0.22 and 10.0.14.
| Version | Released | Support track | End of support |
|---|---|---|---|
| .NET 8 | November 14, 2023 | LTS (3 years) | November 10, 2026 |
| .NET 9 | November 12, 2024 | STS (2 years) | November 10, 2026 |
| .NET 10 | November 11, 2025 | LTS (3 years) | November 14, 2028 |
| .NET 11 RC3 | October 25, 2026 | Go-live (pre-release) | November 10, 2026 |
What actually stops — and what keeps running
The most common misunderstanding about an end-of-support date is also the most dangerous one: nothing visibly breaks on November 11. Your .NET 8 application will start, serve requests and pass its health checks exactly as it did on November 9. What ends is Microsoft's obligation to fix it — no servicing updates, no security patches, no support cases. Every runtime vulnerability disclosed after the deadline stays open on your systems, and the risk grows fastest for anything reachable from the internet.
Two related deadlines land the same day and are easy to miss. The in-process hosting model for Azure Functions on .NET 8 and .NET 9 also ends support on November 10, 2026, so Functions users must move to the isolated worker model on .NET 10 as well. And hosting platforms and container base images eventually stop offering the old runtimes altogether — staying put is not a stable long-term option even if it feels like one on November 11.
Illustrative image: code on a developer's screen. Image: Wikimedia Commons.
Why .NET 10 is the target — not .NET 11
.NET 11 is real and imminent — its release candidates are already out and it is expected to go generally available at .NET Conf, November 10–13, 2026. But as an odd-numbered release it is an STS version with roughly two years of support, while .NET 10 is the LTS release supported until November 2028. For production systems, the boring, correct move is .NET 10 now; .NET 11 is a fine next step afterwards, not a reason to delay. Teams that upgrade every LTS cycle — roughly every two to three years — get the longest quiet stretch.
For most applications the upgrade itself is a retarget, not a rewrite: install the .NET 10 SDK, change the target framework to net10.0, move Microsoft packages to 10.0.x, rebuild and fix what the compiler and your tests report. The work that surprises people is the inventory — the version hides in project files, global.json pins, CI setup steps, Docker base images, App Service settings and self-contained deployments, and any one of them can quietly keep you on .NET 8 after you think you have moved. Cross two sets of breaking changes (9.0 and 10.0) on the way from 8 to 10, and check the documented changes for ASP.NET Core, Entity Framework Core and Blazor first, since those are where upgrades most often break.
Why it matters for World Tech readers — and what it means for India
This is a global deadline with a direct India angle: a large share of enterprise, fintech and services software in India runs on .NET, and Indian teams maintaining those systems face the same November 10 cutoff. If your vendor product runs on .NET 8 or 9, the runtime deadline can arrive before the vendor's own end-of-support date — check with your vendor, not just your own code. Prioritise internet-facing systems, apps handling sensitive data and shared services first; internal tools with little exposure can follow, but they still belong on the list. Our Symfony AI 1.0 beta explainer covers another framework's big shift, our Three.js r187 release explainer covers a breaking-change release in the JavaScript world, and our Arch Linux November 2026 ISO explainer shows how fast-moving stacks handle the same keep-current pressure.
Should you care?
✅ Verdict: Yes — if anything you run or rely on is on .NET 8 or 9, start the move to .NET 10 now. The deadline is today — if you have not inventoried your runtimes yet, do it now; patch to the final releases (8.0.33 / 9.0.22) as a minimum. ⏳ If you genuinely cannot move before November 10, record the decision, set a dated upgrade plan and patch to the final releases (8.0.33 / 9.0.22) — but do not treat staying put as a strategy.
FAQs
When does .NET 8 support end?
.NET 8 support ends on November 10, 2026. It is a Long Term Support release that shipped on November 14, 2023, and Microsoft's support policy lists the same end date for .NET 9.
Will my .NET 8 or .NET 9 app stop working on November 10, 2026?
No. Your app keeps running exactly as before. What ends is security patches, servicing updates and Microsoft technical support — so vulnerabilities found after that date stay unpatched.
Should I upgrade to .NET 10 or wait for .NET 11?
Upgrade to .NET 10. It is the current LTS release, supported until November 14, 2028, while .NET 11 is an STS release with about two years of support. You can move from 10 to 11 later; waiting for 11 leaves you on an unsupported runtime.
Is .NET Framework also ending support on November 10, 2026?
No. .NET Framework is a different product on a different clock: versions 4.8 and 4.8.1 are supported as long as the Windows version they ship with, and 4.6.2 ends January 12, 2027. The November 10 date applies to modern, cross-platform .NET only.
TAKEAWAY: .NET 8 and .NET 9 both go out of support on November 10, 2026 — .NET 10 LTS, supported until November 2028, is the move. Inventory your runtimes today, not on November 9.
Follow World Tech on TechByCountry for tomorrow's update.
📸 Get tech in the last 24 hours on Instagram — follow @_techinlast24hrs for daily posts (9 AM–9 PM) and reels at 12:30 PM & 8:30 PM.
Comments
Post a Comment