.NET & SQL Server

.NET 8, .NET 9 and SQL Server 2016 end of support: what now

By Jérôme Stéphan · November 17, 2026 · Reading time: 6 min

Read in: Español · English · Français

.NET 8, .NET 9 and SQL Server 2016 end of support: what now

On 10 November 2026, .NET 8 and .NET 9 stopped receiving updates. SQL Server 2016 had already been out of support since 14 July. If your site or system runs on one of these versions, it works exactly as it did yesterday, but it no longer gets security patches. Here's what changed, what's still supported and how to decide what to do.

The dates at a glance

ProductEnd of supportStatus today
.NET 612 November 2024Out of support
.NET 810 November 2026Out of support
.NET 910 November 2026Out of support
.NET 10 (LTS)November 2028Supported
.NET 11November 2028Supported, released 10 November 2026
.NET Framework 4.8 and 4.8.1No date: follows the Windows lifecycleSupported
.NET Framework 4.6.212 January 2027Final weeks
SQL Server 201614 July 2026Out of support
SQL Server 201712 October 2027Extended support
SQL Server 20198 January 2030Extended support
Windows Server 201612 January 2027Final weeks

The dates come from the .NET support policy and Microsoft's lifecycle pages, checked on 17 November 2026.

What "out of support" means

The application doesn't switch off. But Microsoft no longer publishes security fixes or updates, and no longer provides technical support for that version. Every flaw discovered from now on stays open. And in an audit or a corporate client's security questionnaire, an unsupported platform counts against you.

Case 1: you're on .NET 6, 8 or 9

This is the simplest case: the destination is .NET 10, the long-term support release, and the programming model is the same.

I've just done it with my Parcelas Patagonia portal: the .NET 10 and EF Core 10 version was ready on 17 November 2026. In practice:

The Parcelas Patagonia portal
Parcelas Patagonia, my real estate portal, migrated to .NET 10 in November 2026.

The code change is short. What takes time, and what you mustn't skip, is the testing.

Case 2: you're on .NET Framework (Web Forms, MVC 5)

There's no date forcing your hand here: .NET Framework 4.8 stays supported as long as your version of Windows is. But it gets no new features, and Web Forms doesn't exist in modern .NET.

Watch what surrounds it: .NET Framework 4.6.2 and Windows Server 2016 both end on 12 January 2027. If you decide to migrate, I explain the method in migrating ASP.NET Web Forms to .NET 10.

Case 3: your database is on SQL Server 2016

The second option is almost always the better one: you pay once to migrate, instead of paying every year to stay where you are.

Case 4: you still have classic ASP

Classic ASP stays supported as long as the Windows hosting it is. But nearly all of those sites are written in VBScript, which Microsoft deprecated in 2023 and plans to remove from a future version of Windows Server. Nothing is urgent today, but the direction is clear.

Where to start

First find out what you have installed. On the server, two commands will tell you:

dotnet --list-runtimes

SELECT @@VERSION;
  1. Take inventory: the .NET, SQL Server and Windows version behind each application.
  2. Sort by exposure: anything open to the Internet comes first.
  3. Test on a copy, never directly in production.
  4. Plan in stages, with a backup before each one.

If you'd like a second opinion, I do a free audit and give you a staged plan at a fixed price: it's all on my .NET migration and modernisation page. And if you're looking for someone to trust with the system, first read how to choose a freelance ASP.NET and SQL Server developer.

Got a .NET or SQL Server application to modernise?

Free audit and a staged plan at a fixed price. I reply in English, French or Spanish.

Ask for my free auditMessage me on WhatsApp
WhatsApp