.NET and .NET Framework end-of-support dates
Modern .NET versions are supported for two or three years. .NET Framework follows the Windows version it runs on. This page lists every version, its end-of-support date and where it stands today.
Support dates by version
Status as of 3 October 2026. Dates come from the Microsoft .NET support policy; check there before relying on them for a decision.
| Version | Released | Security fixes end | Status today |
|---|---|---|---|
| .NET Framework 3.5 SP1 | 19 November 2007 | 9 January 2029 | Supported |
| .NET Framework 4.0, 4.5 and 4.5.1 | 12 April 2010 | 12 January 2016 | Support ended |
| .NET Framework 4.5.2, 4.6 and 4.6.1 | 5 May 2014 | 26 April 2022 | Support ended |
| .NET Framework 4.6.2 | 2 August 2016 | 12 January 2027 | Ending within a year |
| .NET Framework 4.7 to 4.8.1Supported for as long as the Windows version it is installed on. No new features. | 5 April 2017 | No date announced | Supported |
| .NET Core 2.1 | 30 May 2018 | 21 August 2021 | Support ended |
| .NET Core 3.1 | 3 December 2019 | 13 December 2022 | Support ended |
| .NET 5 | 10 November 2020 | 10 May 2022 | Support ended |
| .NET 6 | 8 November 2021 | 12 November 2024 | Support ended |
| .NET 7 | 8 November 2022 | 14 May 2024 | Support ended |
| .NET 8 | 14 November 2023 | 10 November 2026 | Ending within a year |
| .NET 9 | 12 November 2024 | 10 November 2026 | Ending within a year |
| .NET 10 | 11 November 2025 | 14 November 2028 | Supported |
How .NET support works
Modern .NET (.NET 5 onwards, and .NET Core before it) releases a new version every November. Even-numbered versions are long-term support (LTS) releases, supported for three years. Odd-numbered versions are standard-term releases, now supported for two years. In practice a business application should sit on an LTS version and move to the next one every two to three years.
.NET Framework works differently. It is a component of Windows, and versions 4.7 to 4.8.1 are supported for as long as the Windows version underneath them. Older 4.x versions have fixed end dates, several of which have already passed.
What to do if you are out of support
- On .NET Core 3.1, .NET 5, 6 or 7: move to .NET 10. For most applications this is days or weeks of work, mostly testing.
- On .NET 8 or 9: plan the move to .NET 10 before November 2026.
- On .NET Framework 4.6.1 or earlier: move to 4.8 as an immediate step. It is generally a small change and puts the runtime back in support.
- On .NET Framework 4.8: you are supported. Whether to migrate to modern .NET is a business decision; our .NET Framework page sets out the considerations.
Things that are easy to miss
The runtime version is only part of the picture. An application can be on a supported .NET version and still depend on an out-of-support database, operating system or third-party library. A .NET upgrade assessment lists every dependency and its status.
Questions we are asked
When does .NET 8 support end?
.NET 8 is a long-term support release and its support ends on 10 November 2026. Applications should move to .NET 10, the current long-term support release, which is supported until November 2028.
Is .NET Framework 4.8 end of life?
No. .NET Framework 4.8 and 4.8.1 are supported for as long as the Windows version they are installed on, and Microsoft has announced no end date. They receive security and reliability fixes but no new features.
What happens when a .NET version reaches end of support?
Microsoft stops releasing security patches for it. The application keeps running, but any vulnerability found afterwards in the runtime stays unpatched, and hosting platforms eventually stop offering the version.
How hard is it to move from .NET 6 or .NET 8 to .NET 10?
Usually straightforward: update the target version and package references, fix a small number of breaking changes and run the tests. It is a far smaller job than moving from .NET Framework to modern .NET.
Is .NET Framework 3.5 still supported?
Yes. .NET Framework 3.5 SP1 has its own end date of 9 January 2029, later than some 4.x versions, because of how it ships with Windows.
Running a version that is out of support?
Tell us which version, what depends on it and how it is hosted. We will set out the upgrade route and what it is likely to involve.