Back to blog

OSSeva Blog

Operations

.NET Framework 4.8 End of Life vs .NET 8: Why the Support Rules Differ

6 min read

.NET Framework 4.8 end of life

.NET Framework 4.8 has no end-of-life date of its own: it is supported for as long as the version of Windows it is installed on. .NET 8 is the opposite, a standalone runtime with a fixed date, 10 November 2026, that has passed. Teams that run both need two plans. If your applications are on .NET 8 or 9, see .NET 8 extended support.

.NET Framework 4.8 and 4.8.1.NET 8
What it isA component of WindowsA separate, cross-platform runtime you install and update
Support clockThe lifecycle of the Windows version it runs onThree years from release (LTS), fixed
End dateNone of its own10 November 2026, passed
ExtensionWindows ESU, where Microsoft offers oneNone from Microsoft
Path forwardStay on supported Windows, or port to modern .NETUpgrade to .NET 10

Sources: Microsoft's .NET Framework and .NET support policies, read 17 November 2026.

Running .NET in production? OSSeva patches and supports it, end-of-life versions included.

.NET extended support: what is covered

Why .NET Framework is tied to Windows

Since version 4.5.2, Microsoft defines .NET Framework as a component of the Windows operating system, and components get the same support as their parent product. The policy says 4.8.1 will keep being distributed with future Windows releases and stays supported while it sits on a supported Windows. The Windows lifecycle fact sheet is therefore the place to check the date, not the .NET page.

Some individual releases do have dates. Microsoft's policy page lists .NET Framework 4.6.2 ending on 12 January 2027 and 3.5 SP1 on 9 January 2029, and 4.6.1, 4.6 and 4.5.2 ended on 26 April 2022. A Windows ending support, for example Windows Server 2016 on 12 January 2027, ends the clock for the Framework on it too; see Windows Server 2016 end of support.

Why modern .NET works differently

Modern .NET is independent of the operating system, so it has its own release train and its own fixed window. A new major ships every November; even numbers get three years and odd numbers two. That is why .NET 8 and .NET 9 ended on the same day. See .NET LTS vs STS and .NET 8 end of life.

What to do if you run both

  • List Framework apps and the Windows versions under them. Their risk date is the Windows date.
  • Move .NET 8 and 9 apps to .NET 10 or cover them with patches; Microsoft sells no ESU for .NET (why).
  • Treat a Framework to modern .NET move as a port, not an upgrade. It is a separate project and a separate decision.

OSSeva's patched builds cover .NET (Core and 5 and later); Windows .NET Framework 4.x is a services engagement, not a patched build. The .NET end-of-life tracker shows every modern line.

Frequently asked questions

When does .NET Framework 4.8 reach end of life?

It has no date of its own. Microsoft supports it while it is installed on a supported version of Windows.

Is .NET Framework 4.8 still supported?

Yes, on supported Windows versions. It is listed as active on Microsoft's policy page, read 17 November 2026.

Can I upgrade .NET Framework 4.8 to .NET 8?

Not as an in-place upgrade, and .NET 8 has ended; target .NET 10. Moving from Framework to modern .NET is a port that touches APIs and hosting.

Does .NET Framework have ESU?

Not on its own. It follows the Windows version's lifecycle and any Windows ESU Microsoft offers.

Where OSSeva fits

OSSeva patches modern .NET after Microsoft's dates, not .NET Framework. For .NET 8 and .NET 9 workloads, see .NET 8 extended support.

Sources

Read 17 November 2026: .NET Framework support policy, .NET Framework lifecycle and .NET support policy.

Tags

.NET.NET Framework.NET 8End of LifeWindows

Get a quote

Ready to get your open source under control?

Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call