.NET 8 end of life and end of support
Support for .NET 8 ended on 10 November 2026, and .NET 9 ended the same day, so the version to move to is .NET 10, supported until 14 November 2028. This page is for IT and operations managers responsible for .NET applications that someone else built, who need to know what stops, whether they are affected and what to do next.
Status on 12 November 2026
- .NET 8
- Support ended
- Security fixes
- Ended 10 November 2026
- Released
- 14 November 2023
- Security fixes ended
- 10 November 20262 days ago
Dates come from the Microsoft .NET support policy; check there before relying on them for a decision.
What ends, and what carries on
Modern .NET has a new version every November. Even-numbered versions are long-term support releases, supported for three years. Odd-numbered versions get two. .NET 8 was a long-term support release: released on 14 November 2023, with support ending on 10 November 2026. In its last six months Microsoft fixed security vulnerabilities only.
Since the end date Microsoft issues no further fixes or updates for the .NET 8 runtime or the libraries that ship with it. Applications built on it carry on running.
Do not confuse .NET 8 with .NET Framework 4.8, a different product that follows the support dates of Windows. Our .NET dates page lists both.
.NET 9 ended on the same day
.NET 9 is a standard-term release, and its support also ended on 10 November 2026. Moving from .NET 8 to .NET 9 now gains nothing. Go straight to .NET 10, which is supported until 14 November 2028. Plan for the next move before then: a long-term support release needs replacing every two to three years.
How to find out whether you are affected
You do not need to be a developer to find out. Ask whoever supports each application, or check these yourself:
- The project file. Each .NET project has a file ending
.csproj(or.vbproj). The line<TargetFramework>net8.0</TargetFramework>means .NET 8.net9.0means .NET 9, andnet10.0means .NET 10. - The server. On a server or PC that runs the application, the command
dotnet --list-runtimeslists the installed runtimes. Lines startingMicrosoft.NETCore.App 8.orMicrosoft.AspNetCore.App 8.show .NET 8 is installed. Installed is not the same as used, so check the project file too. - Containers. An image tag such as
mcr.microsoft.com/dotnet/aspnet:8.0means .NET 8. - Cloud hosting. An Azure App Service or similar shows the runtime stack in its configuration settings.
Our free end-of-support check is a script that lists what a Windows server is running, including .NET runtimes, with the end date for each.
A short inventory, filled in for each application, is enough to plan from:
| Application | Who supports it | .NET version | Automated tests? | Hosted where | Internet-facing? |
|---|---|---|---|---|---|
What it means for the applications built on .NET 8
- The change itself is usually small. Update the target framework, update the package references, fix a small number of breaking changes and run the tests. Microsoft publishes the breaking changes for each release, so there is a list to work through.
- The tests decide the risk. With a good set of automated tests, the upgrade can be made and checked quickly. With none, the application compiles and starts, and nobody can say whether a calculation, a date format or a sort order now behaves differently. The work then becomes manual testing by people who know the business process.
- One stale package can hold everything up. Most libraries support a new .NET version promptly. One that its author has stopped maintaining may not, and replacing it can be the largest part of the job.
- Hosting moves on. Cloud platforms eventually stop offering an unsupported runtime. Container base images for it stop being updated, so a container built on one also stops receiving fixes for the layers beneath the application.
Upgrade, replace or run on: how to decide
| Your situation | Usual choice |
|---|---|
| The application builds, has automated tests and its packages are maintained | Upgrade to .NET 10 now. This is routine work. |
| No tests, stale packages, or nobody has built it recently | Find out the size first: get it building, write tests for what the business relies on, then upgrade. |
| The application is due to be replaced or retired for business reasons anyway | Run on for a short, planned period with the risk recorded, and put the effort into the replacement. |
Running on past the date is a decision, not a default. The application keeps working. The exposure grows with each vulnerability found in the runtime, and it is greatest for anything reachable from the internet. Write down who accepted the risk and until when.
Third-party extended support. Microsoft sells no paid extension for .NET 8. Some other companies sell security fixes for out-of-support .NET versions. If you consider one, ask exactly what it covers. It does not change your own code or the third-party packages the application uses, so it buys time for the upgrade rather than replacing it.
What to tell the board
Three sentences are usually enough:
- Microsoft stopped fixing security problems in .NET 8, which our application runs on, on 10 November 2026; the application keeps working, but new vulnerabilities in it will not be fixed.
- Moving to .NET 10, supported until November 2028, is normally a contained piece of work; how big it is for us depends on our tests, our packages and whether we can build the application.
- We propose to size the work now and schedule it, and to record the risk of running on until it is done.
Our guide to writing the business case before end of support goes further.
What we would check first
We would check four things. Does the application build from source on a clean machine? Are there automated tests, and do they pass? Which packages does it use, and is each still maintained? Where is it hosted, and how is a release made?
Our .NET upgrade assessment answers those questions at a fixed price. If the people who built the application have gone, start with our software takeover service. Because a long-term support release needs replacing every two to three years, the upgrade is best treated as routine upkeep, which is what our software maintenance service is for.
Sources
- .NET and .NET Core support policy (Microsoft)
- Check installed .NET versions (Microsoft Learn)
Not sure where .NET 8 is still running?
Most organisations find more copies than they expected. Two ways to find out, depending on how much you want to know.
Check which version you have
A server can have several .NET versions installed side by side. What matters is the version each application is built for, not the newest one on the machine.
How to check every productFor modern .NET, this command lists every runtime installed. For .NET Framework, the version is recorded in the registry, and our free script reads it for you.
dotnet --list-runtimes When it is not yours to upgrade
Applications are held on an old .NET version by the components they were built with: a grid or reporting control bought years ago, a payment or document library whose vendor has stopped trading, or a component for which nobody holds the source code.
Find these before estimating an upgrade. Each one has to be upgraded, replaced or wrapped, and they decide how large the job is far more than the amount of your own code.
Making the case for the work
An upgrade nobody outside IT can see is easy to defer. These are the reasons that tend to move it up the list.
- Cyber Essentials
- The scheme requires software in scope to be supported by its vendor. Anything past its end-of-support date has to be removed, or cut off from the internet, before you can certify or renew.
- Cyber insurance
- Proposal forms commonly ask whether you run unsupported software. Check what yours asked, and what you answered.
- Customer questionnaires
- Larger customers ask the same question of their suppliers. An honest "yes, and here is the plan" is a better answer than a late discovery.
- Personal data
- UK data protection law expects appropriate technical measures to protect personal data. Software that can no longer be patched is hard to square with that.
- The cost of waiting
- An upgrade done to a deadline, after something has failed, costs more than the same upgrade planned. Where Microsoft sells a paid security extension, its price has risen each year it runs.
- Official guidance
- The National Cyber Security Centre is blunt: "The only fully effective way to mitigate this risk is to stop using the obsolete product." See its guidance on obsolete products.
What we do and do not sell: we do not sell Microsoft licences or Extended Security Updates, so we have no stake in which version you choose. Our part is the application: finding what depends on the old version, testing it against the new one and fixing what breaks.
Supported versions to move to
How long each would keep you in support. All .NET and .NET Framework versions
| Version | Released | Security fixes end | Status today |
|---|---|---|---|
| .NET 10 | 11 November 2025 | 14 November 2028 | Supported |
Questions we are asked
When does .NET 8 reach end of life?
Support for .NET 8 ended on 10 November 2026. It was a long-term support release that came out on 14 November 2023, and .NET 9 went out of support on the same day.
Do we have to upgrade now that support has ended?
Nothing forces you to. The application keeps running. Since 10 November 2026, security vulnerabilities found in the .NET 8 runtime are not fixed, so the risk grows the longer you stay, fastest for anything reachable from the internet. If you cannot move straight away, record the decision, put a date on the upgrade and start by finding out how big it is.
What happens to our .NET 8 application now support has ended?
Nothing visible. It carries on running. What stops is security fixes for the runtime, and later hosting platforms and container base images stop offering the version.
Is there extended support for .NET 8?
Not from Microsoft. It sells no paid extension for .NET 8. Some other companies sell security fixes for out-of-support .NET versions; treat them as a stop-gap while the upgrade is done, not a plan. They do not change your own code or the third-party packages your application depends on.
Should we move from .NET 8 to .NET 9 or to .NET 10?
To .NET 10. .NET 9 went out of support on 10 November 2026, the same day as .NET 8. .NET 10 is a long-term support release and is supported until 14 November 2028. .NET 11, released on 10 November 2026, is a standard-term release supported until the same date, so it gains nothing for a business application.
How long does an upgrade from .NET 8 to .NET 10 take?
It depends on the application, not on .NET. The things that make it bigger are a lack of automated tests, packages that are no longer maintained, and a build or release process nobody has run recently. A short assessment of those three answers the question for your system.
What if the people who built the application have gone?
The upgrade can still be done by another developer, provided you have the source code and can build it. Check first that you have the code and the right to change it. Our software takeover service is for exactly this situation.
Send us your version list
Paste the output of the free check, or list the Windows, SQL Server, .NET and Office versions your application runs on and how it is hosted. We reply within a working day with what is exposed, what to fix first and what each step is likely to involve. No charge and no commitment; it is the same first look we do before any takeover.
Still running .NET 8?
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.