Is .NET Framework Still Supported? End-of-Life Dates (2026)

Short answer

.NET Framework is supported, with no end date announced. CISA’s Known Exploited Vulnerabilities catalog lists 4 vulnerabilities in .NET Framework (1 added in the last 24 months).

.NET Framework 4.8 and 4.8.1 have no end date of their own: Microsoft supports them for as long as the Windows version they run on, so the date that matters is your Windows lifecycle, while 4.6.2 ends on 12 January 2027.

Legacy Technology Tracker · Status as of 21 Nov 2026. Data checked 12 Nov 2026; refreshed monthly, with quarterly snapshots kept unchanged.

What to do now

Windows Server 2016 ships with .NET Framework 4.6.2, so 2016 servers that were never moved to 4.7 or later are the first machines to look for (system requirements).

  • Find the machines on 4.6.2. The Release value under HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full is 394802 (Windows Server 2016) or 394806 (other Windows versions) for 4.6.2; 528040 or higher means 4.8 or later (Microsoft).
  • On Windows Server 2019 or later, update in place. Install 4.8 on 2019, or 4.8.1 on 2022; 2025 ships with 4.8.1. The runtime then follows the server's own support dates: January 2029 on 2019, October 2031 on 2022 and November 2034 on 2025.
  • On Windows Server 2016, the server sets the deadline. 4.8 is the newest version 2016 can run, and there it is supported only until the server's own end of support, also 12 January 2027. Updating the runtime alone does not move the date; upgrading the server does. Paying for the server's Extended Security Updates (from $42 a month per virtual machine at Microsoft's list price) may also cover it: Microsoft delivered .NET Framework fixes as ESUs for Windows Server 2012 R2 (KB5087049), but its Windows Server 2016 ESU pages do not say so. Confirm it with Microsoft before relying on it. See Windows Server 2016.

Risk rating

Low

Low: supported with no end date announced; no licence change recorded in the last 24 months; 4 vulnerabilities on CISA's KEV list (supported versions receive security fixes). How ratings work

Support end dates by version

7 of 13 versions still get vendor support. Next to lose standard support: 4.6.2, 12 Jan 2027.

  • 4.7No end announced, Supported
  • 4.7.1No end announced, Supported
  • 4.7.2No end announced, Supported
  • 4.8No end announced, Supported
  • 4.8.1No end announced, Supported
  • 3.5-sp1, Supported
  • 4.6.2, Supported
  • 4.5.2, Unsupported
  • 4.6, Unsupported
  • 4.6.1, Unsupported
  • 4.0, Unsupported
  • 4.5, Unsupported
Each row is one version; a dot marks the end of standard support. An arrow running from today means no end date is announced. The vertical line is today, 21 Nov 2026. Showing the 12 versions with the latest end dates, out of 13. Every date is in the versions table with its source.

Key facts

Every value links to its source and shows when we last checked or retrieved it. Data checked 12 Nov 2026; status as of 21 Nov 2026.

FactValueSourceChecked
Support statusSupported.NET Framework 1.x–4.8.1 (not .NET Core / .NET 5+).
Support end dateNo end date announced
Known exploited vulnerabilities (CISA KEV)4 CVEs all time; 1 added in the last 24 monthsNewest added 4 Feb 2025Matched by vendor and product name in the KEV catalog.
Job postings and salariesNot published: the job-posting source is on hold pending a data licence.——

Versions in scope

.NET Framework 1.x–4.8.1 (not .NET Core / .NET 5+). Dates per version, each with its source.

VersionStatusStandard support endsExtended support endsLatest releaseSourceChecked
3.5-sp1Supported——
4.0Unsupported——
4.5Unsupported——
4.5.1Unsupported——
4.5.2Unsupported——
4.6Unsupported——
4.6.1Unsupported——
4.6.2Supported——
4.7Supported———
4.7.1Supported———
4.7.2Supported———
4.8Supported———
4.8.1Supported———

If you still run .NET Framework

If you are on .NET Framework 4.5.2, 4.6 or 4.6.1, support already ended on 26 April 2022, and 4.0, 4.5 and 4.5.1 ended in January 2016. Version 4.6.2 ends on 12 January 2027. Versions 4.7 to 4.8.1 have no end date of their own; they follow your Windows version, so that Windows version's end of support is the deadline.

The realistic options:

  • Update in place to 4.8.1 or 4.8. Microsoft says 4.6.2 and later are compatible in-place updates, and applications built on earlier 4.x versions are expected to keep running without a recompile. This is the quick fix for the 4.6.2 date, except on Windows Server 2016, where 4.8 ends on the same day as the server. Validate in a pre-production environment first, as Microsoft advises.
  • Keep the Windows version supported. Once you are on 4.8.x, the runtime stays supported for as long as its Windows version does. Plan Windows Server upgrades alongside application changes.
  • Migrate to modern .NET. This removes the tie to Windows and allows Linux and containers, but WebForms, WCF and other Framework-only parts need rework. The .NET Framework to .NET guide covers scope, cost ranges and risks.

Legacy system modernization companies lists suppliers for .NET migrations, and modernization costs gives budget ranges.

Frequently asked questions

Is .NET Framework still supported?

Yes. Microsoft's lifecycle page lists no end date for .NET Framework 4.8.1, 4.8, 4.7.2, 4.7.1 or 4.7. From version 4.5.2 onward, .NET Framework is a component of Windows and follows the lifecycle of the Windows version it is installed on (Microsoft lifecycle FAQ).

When does .NET Framework 4.8 reach end of support?

It has no date of its own. It is supported while the Windows version it runs on is supported, so check that version's end date on Microsoft's Windows lifecycle FAQ.

When does .NET Framework 4.8 support end on Windows Server?

On the day that Windows Server version leaves extended support, because .NET Framework 4.5.2 and later follows the lifecycle of the Windows version it is installed on (Microsoft lifecycle FAQ). That is 12 January 2027 on Windows Server 2016, 9 January 2029 on Windows Server 2019, 14 October 2031 on Windows Server 2022 and 14 November 2034 on Windows Server 2025. Windows Server 2016 and 2019 cannot install 4.8.1, so 4.8 is the newest version there; 4.8.1 needs Windows Server 2022 or later (system requirements).

Which .NET Framework versions are out of support?

Microsoft ended support for 4.0, 4.5 and 4.5.1 on 12 January 2016, and for 4.5.2, 4.6 and 4.6.1 on 26 April 2022. Version 4.6.2 ends on 12 January 2027. Microsoft says 4.6.2 and later are in-place updates over earlier 4.x versions, so most applications need no recompile to move up.

What can replace .NET Framework?

Teams move to modern .NET (formerly .NET Core), which also runs on Linux. The .NET Framework to .NET migration guide covers scope, cost ranges and risks.