.NET End of Life (EOL) Dates: Every Version and Its Support Status
Release and end-of-support dates for every .NET and .NET Core version, which releases Microsoft still patches, and how LTS and STS lengths differ.
Updated Dates checked Shahzeb Umer
Where to be now
Be on .NET 10.
- Supported now
- 2
- Next to end
- Microsoft .NET 1114 November 2028, in 726 days
- Newest release
- Microsoft .NET 11Released 10 November 2026
- Why .NET 10
- It is the current LTS release, supported until 14 November 2028, and .NET 11, released on 10 November 2026 as an STS release, ends on that same day, so moving to 11 brings newer features and no extra support time.
- Bug and security fixes
- Security fixes only
- Extended support, often paid
- Today
Microsoft .NET: 2 of the 6 releases shown are supported today. 11 from 10 Nov 2026 to 14 Nov 2028; 10 from 11 Nov 2025 to 14 Nov 2028; 9 from 12 Nov 2024 to 10 Nov 2026; 8 from 14 Nov 2023 to 10 Nov 2026; 7 from 8 Nov 2022 to 14 May 2024; 6 from 8 Nov 2021 to 12 Nov 2024.
Version guides
Your version, in depth.4
Supported
Versions still getting fixes2
| Version | Released | Security fixes until | Latest |
|---|---|---|---|
| 11Microsoft .NET 11 end of life | 11.0.010 Nov 2026 | ||
| 10LTSMicrosoft .NET 10 end of life | 10.0.1510 Nov 2026 |
Ended
Versions that no longer get fixes12
| Version | Released | Ended | Final release |
|---|---|---|---|
| 9 | 9.0.23 | ||
| 8LTSMicrosoft .NET 8 end of life | 8.0.34 | ||
| 6LTSMicrosoft .NET 6 end of life | 6.0.36 | ||
| 7 | 7.0.20 | ||
| 3.1LTS | 3.1.32 | ||
| 5 | 5.0.17 | ||
| 2.1LTS | 2.1.30 | ||
| 3.0 | 3.0.3 |
Show 4 older versions
| 2.2 | 2.2.8 | ||
| 1.1 | 1.1.13 | ||
| 1.0 | 1.0.16 | ||
| 2.0 | 2.0.9 |
Reading the dates
What Microsoft .NET’s own terms mean.
- How long a release lasts
- Microsoft ships a new major .NET release every November. Even-numbered releases are Long Term Support (LTS) with three years of free support and patches, and odd-numbered releases are Standard Term Support (STS) with two years, up from 18 months before .NET 9. The last six months of any release are maintenance, with security fixes only.
- LTS
- Long Term Support: three years of free support and patches from release. .NET 10 is the current LTS release.
- STS
- Standard Term Support, formerly called Current: two years of free support and patches, which since .NET 9 ends on the same day as the LTS release before it. .NET 11 is the current STS release.
- Active support
- The release gets updates that improve its functional capabilities and fix security vulnerabilities.
- Maintenance support
- The final six months of support, when the release gets fixes for security vulnerabilities only.
Worth knowing
Before you plan around these dates.
.NET ships every November, and support ends on a Patch Tuesday, the second Tuesday of the month. Since .NET Core 3.1, every end-of-support date has landed on one. Under the current policy both events fall in November: the new release arrives, and support for older releases ends.
Why .NET 8 and .NET 9 ended on the same day
Until 2025, STS releases got 18 months. In September 2025 Microsoft raised that to 24 months, starting with .NET 9, which moved its end of support from 12 May 2026 to 10 November 2026, the day .NET 8 also ended. Microsoft's reason was dependencies: out-of-band releases such as .NET Aspire can pull STS versions of packages into an app built on an LTS release, and under the old policy those packages lost support six months before the LTS itself. The same pairing holds now: .NET 10 (LTS) and .NET 11 (STS) both end on 14 November 2028. Choosing 11 gets you newer features and the same end date.
Staying supported means taking every patch
Microsoft supports only the latest servicing update of each release. Once 10.0.16 ships, 10.0.15 is no longer a supported servicing level. Servicing updates ship almost every month, and the ones with security fixes come out on Patch Tuesday.
How a patch reaches your app depends on how you deploy it. A framework-dependent app rolls forward to the newest installed patch of its runtime automatically, so updating the runtime on the machine or in the base image is enough. A self-contained app carries its own copy of the runtime and has to be republished to pick up a patch.
To catch builds that still use an end-of-life SDK, set the CheckSdkVulnerabilities MSBuild property to true. The build then warns with NETSDK1239 when the resolved SDK is out of support.
Common questions
Is .NET 8 still supported?
Is .NET 9 still supported?
What is the latest LTS version of .NET?
What is the latest version of .NET?
What is the difference between .NET LTS and STS?
Does .NET Framework follow the same dates?
Feeds and badge
Get told before the next Microsoft .NET version ends.
Calendar address
https://bumbletap.com/eol/calendar/dotnet.icsOpen in your calendar appAdd to Google CalendarEvery product in one feed
README badge for Microsoft .NET 11
[](https://bumbletap.com/eol/dotnet)Rendered by shields.io from a small JSON file rebuilt daily. Swap the version in the address for any other line. It turns yellow 90 days out and red once support ends.
Sources
Where these dates come from.
- .NET and .NET Core Support Policy
- .NET releases index (releases-index.json)
- .NET Blog: .NET STS releases supported for 24 months
- Microsoft Learn: .NET releases, patches, and support
- Microsoft Learn: Runtime roll forward for self-contained app deployments
Dates come from endoflife.date (MIT), and were last checked . The words on this page are written here. How we check datesReport a wrong date
Also on the calendar
End-of-life dates for the rest of your stack.
- Kubernetes end of life3 supportedNext to end: 1.35, 28 Feb 2027
- Node.js end of life3 supportedNext to end: 22, 30 Apr 2027
- OpenSSL end of life3 supportedNext to end: 4.0, 14 May 2027
- PHP end of life5 supportedNext to end: 8.2, 31 Dec 2026
- PostgreSQL end of life5 supportedNext to end: 15, 11 Nov 2027
- Python end of life5 supportedNext to end: 3.11, Oct 2027
- Ubuntu end of life4 supportedNext to end: 22.04, 1 Jun 2027