.NET End of Support Dates by Version

.NET end of support dates: 22 versions are listed below. 18 are already past Microsoft's end of support, most recently .NET 8 (LTS) on Nov 10, 2026; the next to end is .NET Framework 4.6.2 on Jan 12, 2027. Third-party support keeps any of these versions in production after the vendor date, with 24x7 incident response, vulnerability mitigation and compliance documentation, typically at 40-70% below the vendor's renewal.

18
past vendor support
1
end within 12 months
22
versions with dates

.NET versions and end of support dates

"Vendor end of support" is the date Microsoft stops free fixes and security updates. "Extended end" is the end of the paid extension where Microsoft offers one. Each version links to its own page and quote form.

VersionVendor end of support
.NET Framework 3.5 SP1Jan 9, 2029Get support
.NET 10 (LTS)Nov 14, 2028Get support
.NET 11 (11)Nov 14, 2028Get support
.NET Framework 4.6.2Jan 12, 2027Get support
.NET 8 (LTS)Nov 10, 2026Get support
.NET 9Nov 10, 2026Get support
.NET 6 (LTS)Nov 12, 2024Get support
.NET 7May 14, 2024Get support
.NET Core 3.1 (LTS)Dec 13, 2022Get support
.NET 5May 10, 2022Get support
.NET Framework 4.5.2Apr 26, 2022Get support
.NET Framework 4.6Apr 26, 2022Get support
.NET Framework 4.6.1Apr 26, 2022Get support
.NET Core 2.1 (LTS)Aug 21, 2021Get support
.NET Core 3.0Mar 3, 2020Get support
.NET Core 2.2Dec 23, 2019Get support
.NET Core 1.0Jun 27, 2019Get support
.NET Core 1.1Jun 27, 2019Get support
.NET Core 2.0Oct 1, 2018Get support
.NET Framework 4.0Jan 12, 2016Get support
.NET Framework 4.5Jan 12, 2016Get support
.NET Framework 4.5.1Jan 12, 2016Get support

5 further .NET entries in the catalog have no published date: .NET Framework 4.7, .NET Framework 4.7.1, .NET Framework 4.7.2, .NET Framework 4.8, .NET Framework 4.8.1.

Why .NET versions stay in production

.NET releases ship on an annual cadence with alternating Long Term Support and Standard Term Support versions, and applications built on a given runtime stay there until someone funds the rebuild. The .NET Framework versions bundled with Windows follow the Windows lifecycle instead.

An application on an out-of-support runtime is a security review finding before it is an operational problem. Third-party support turns that finding into a managed risk with a plan.

How Microsoft's support lifecycle works for .NET

Microsoft supports each .NET (Core) release for a fixed period after launch, longer for LTS versions than for STS versions. After the end date no further security patches ship for that runtime. .NET Framework versions are tied to the Windows version they ship with and follow Windows end-of-support dates.

There is no paid extension for .NET runtimes; the choices are upgrading the application's target framework or managing the risk of the unpatched runtime.

What changes on the end of support date

  • Microsoft stops shipping security patches for the runtime and SDK.
  • Applications keep running; dependency scanners and auditors flag the runtime.
  • Hosting bundles and container base images for the version stop being updated.

Your options after .NET end of support

1. Upgrade to a supported version

Right when the application above it is ready and the budget exists. Wrong as a forced move: an upgrade driven by a support date rather than a business need is where regression bugs and surprise licence costs come from.

2. Stay on the version without vendor support

Microsoft offers no paid extension for this product, so staying put means managing the unpatched risk yourself.

3. Third-party support

Replaces the vendor contract with ours for the versions you run, with no deadline. For .NET that covers:

  • Runtime, hosting bundle and deployment incidents for applications on the version, 24x7
  • Vulnerability assessment of each new .NET CVE against your application and mitigation guidance
  • Compliance documentation for applications that must remain on a given runtime
  • Target-framework upgrade planning and assistance when you choose to move

Not included: new vendor patches or licences. Those stay with Microsoft; everything operational moves to us.

.NET end of support: frequently asked questions

Which .NET versions are out of support?

.NET 8 (LTS) (Nov 10, 2026), .NET 9 (Nov 10, 2026), .NET 6 (LTS) (Nov 12, 2024), .NET 7 (May 14, 2024), .NET Core 3.1 (LTS) (Dec 13, 2022), .NET 5 (May 10, 2022), .NET Framework 4.5.2 (Apr 26, 2022), .NET Framework 4.6 (Apr 26, 2022) and 10 earlier versions. All of them can be covered by third-party support.

Can an application on an unsupported .NET version be covered?

Yes. Third-party support covers runtime and deployment incidents and provides vulnerability mitigation and compliance documentation while an upgrade is planned.

Is there a Microsoft paid extension for .NET?

No. Unlike Windows and SQL Server, .NET runtimes have no ESU programme, which is why third-party support is the main option for staying on a version.

What does third-party support for .NET cost?

Typically 40 to 70% below the vendor renewal or extended-support price for the same versions, priced per instance, server or core depending on the product. We return an indicative price within 24 hours and a firm quote within 48.

How do we move .NET to third-party support without a gap?

Start before the vendor renewal date: inventory versions and instances, download all media and fixes you are entitled to, confirm no bundled contract depends on the renewal, then let the vendor support lapse as ours starts. We handle the hand-over checklist with you.

Version-by-version guides

Related

Price .NET support

Indicative price within 24 hours. Tell us the versions, instance count and how long you need them covered.

Your quote will be sent to this address.

By submitting this form, you agree to our Privacy Policy.

.NET support past end of life
Price in 24 hours · 40-70% below the vendor renewal
Get a support price