Dexaloop › Tech › Software and development

Software and development · How-to

.NET 8 end of support: how to check your .NET version and what to upgrade to

Microsoft's end-of-support date for both .NET 8 and .NET 9 is 10 November 2026, so here is how to find out what you run, what changes after that date, and how to move to .NET 10.

By DexaloopPublished 9 November 20268 min readSources listed below

Key takeaways

  • Microsoft's support policy lists 10 November 2026 as the end of support for both .NET 8 (LTS) and .NET 9 (STS). .NET 10 (LTS) is supported until 14 November 2028.
  • After end of support, Microsoft says it will no longer provide servicing updates, security fixes or technical support. Apps built on .NET 8 or 9 keep running.
  • Run dotnet --list-runtimes to see the runtimes on a machine, and check the TargetFramework in each project file to see what an app targets.
  • The only required code change to upgrade is setting TargetFramework to net10.0. You also need to update the SDK, packages, container images, CI and hosting.
  • As of 9 November 2026, .NET 11 is a release candidate with general availability expected in November 2026. It is an odd-numbered STS release, so .NET 10 is the long-support target.
On this page
  1. What you need before you start
  2. The short version for beginners
  3. Every supported .NET version and its end date
  4. What end of support actually means
  5. How to check your .NET version
  6. What to upgrade to: .NET 10 or .NET 11
  7. How to upgrade from .NET 8 or 9 to .NET 10
  8. Troubleshooting
  9. What is confirmed and what is not yet known

.NET 8 end of support is on 10 November 2026, and .NET 9 ends on the same day. The .NET support policy lists that date for both, and the .NET Blog announcement says that after it, "Microsoft will no longer provide servicing updates, security fixes, or technical support for these versions." The upgrade target Microsoft recommends is .NET 10, a long-term support release supported until 14 November 2028.

This how-to explains what the support labels mean, how to check which .NET versions you run, what to upgrade to and the steps to do it. The steps are the same whether you read this before or after the deadline.

What you need before you start

  • A terminal on Windows, macOS or Linux, to run the dotnet commands below.
  • Access to each app's project file (the TargetFramework value) and to any global.json.
  • Access to your CI pipelines, Dockerfiles and hosting settings, because the upgrade touches those too.
  • The .NET 10 SDK, installed in step 1 of the upgrade steps.

The short version for beginners

Microsoft ships one major .NET version every November. Each one gets a support label, and the label decides how long it gets free fixes:

LTS

Long Term Support. Even-numbered releases such as .NET 8 and .NET 10. The policy says they "get free support and patches for three years."

STS

Standard Term Support. Odd-numbered releases such as .NET 9 and .NET 11. The policy says they "get free support and patches for two years."

End of support

The policy defines it as "the date when Microsoft no longer provides fixes, updates, or online technical assistance."

If you only remember one rule: run a supported version, and plan to move before its end date. If you follow Node.js too, the idea is the same as Node.js LTS vs Current, with different lengths.

Every supported .NET version and its end date

This table comes from the .NET support policy page as it read on 9 November 2026.

VersionRelease typeReleasedLatest patch listedEnd of support
.NET 10LTS11 November 202510.0.1414 November 2028
.NET 9STS12 November 20249.0.2210 November 2026
.NET 8LTS14 November 20238.0.3310 November 2026
.NET 8 (LTS) .NET 9 (STS) .NET 10 (LTS) Released 14 November 2023 Released 12 November 2024 Released 11 November 2025 Ends 10 November 2026 Ends 10 November 2026 Supported until 14 November 2028
Support windows from the .NET support policy. Bar lengths are illustrative, not to scale. .NET 8 and .NET 9 reach end of support on the same day.

Why do an LTS and an STS release end together? STS used to mean 18 months. In September 2025 the .NET team announced it was increasing STS support from 18 months to 24 months, starting with .NET 9. That moved the .NET 9 end date from 12 May 2026 to 10 November 2026, the same day .NET 8 reaches the end of its three years.

What end of support actually means

Your apps do not switch off. The announcement says: "Applications built on .NET 8 or .NET 9 will continue to run." What ends is maintenance:

  • "No new security updates will be issued for either version."
  • "Technical support will no longer be available for .NET 8 or .NET 9 applications."
  • The post adds that ".NET 8 and .NET 9 may each receive one final update on that day if there is a known critical issue."
  • In Visual Studio, "the .NET 8 and .NET 9 components will be marked as out of support." The post says existing installations won't be affected.

The risk grows over time. Any vulnerability found later in the .NET 8 or 9 runtime will not get a Microsoft fix. The support policy puts it plainly: using out-of-support versions "may put your applications, application data, and computing environment at risk."

How to check your .NET version

There are two questions here: what is installed on a machine, and what each app targets. Check both.

What is installed on a machine

Open a terminal on Windows, macOS or Linux and run the commands from Microsoft's install check guide:

  1. dotnet --list-runtimes lists every runtime, such as Microsoft.NETCore.App and Microsoft.AspNetCore.App, with its version and folder.
  2. dotnet --list-sdks lists every SDK used to build apps.
  3. dotnet --info shows both, plus the operating system and runtime identifier.

Here is the kind of output you might see on a Windows server. Any runtime whose version number starts with 8 or 9 is a version that loses support on 10 November 2026.

Microsoft.AspNetCore.App 8.0.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 8.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 10.0.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

If the commands fail, .NET may be installed but missing from your PATH. The guide lists the default folders to look in, such as C:\program files\dotnet\shared on Windows and /usr/local/share/dotnet/shared on macOS.

What an app targets

Open the project file (.csproj, .vbproj or .fsproj) and find TargetFramework. A value of net8.0 or net9.0 means the app needs upgrading. In code, the RuntimeInformation.FrameworkDescription property returns the runtime the app is running on, such as ".NET 5.0.0" in Microsoft's example. For containers, check the tag in each Dockerfile FROM line.

.NET Framework is a different product

Many searches for "how to check .NET version in Windows" are about .NET Framework, the older Windows-only product. It is not affected by this date. It follows Microsoft's Component Lifecycle Policy, and the .NET Framework lifecycle page lists no end date for 4.8 or 4.8.1. To check it, Microsoft's guide reads the Release value from the registry. This PowerShell line returns True if .NET Framework 4.8 or later is installed:

(Get-ItemPropertyValue -LiteralPath 'HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' -Name Release) -ge 528040

What to upgrade to: .NET 10 or .NET 11

.NET 10.NET 11
Status on 9 November 2026Released 11 November 2025Release candidate
Release typeLTS (even number)STS (odd number)
Support lengthThree yearsTwo years
End of support14 November 2028Not yet published

For most teams the answer is .NET 10. It is the version Microsoft's announcement recommends, describing it as "an LTS release supported through November 2028." The What's new in .NET 11 page says ".NET 11 is currently in release candidate. General availability is expected in November 2026." Going from 8 to 11 means moving to a release that was still a release candidate on 9 November 2026, for a two-year rather than three-year support window.

How to upgrade from .NET 8 or 9 to .NET 10

Microsoft's upgrade guide says "the only required change to upgrade an app is updating the TargetFramework property." The rest of the work is the environment around the code.

  1. Install the .NET 10 SDK from the .NET download page or your package manager. Visual Studio users can update Visual Studio, which installs new SDKs.
  2. Change the target. In each project file set <TargetFramework>net10.0</TargetFramework>. Do the same for TargetFrameworks if you use it.
  3. Build and fix. The SDK reports warnings and errors for anything else that must change. You may need dotnet workload restore.
  4. Read the breaking changes. The .NET 10 breaking changes list includes "Default .NET images use Ubuntu" for containers and "OpenSSL 1.1.1 or later required on Unix." ASP.NET Core and EF Core have their own lists.
  5. Update packages and pins. Move NuGet packages to versions that support .NET 10, and update any global.json that pins an 8 or 9 SDK.
  6. Update CI and hosting. Change version values in CI pipelines and Dockerfile FROM lines, install the .NET 10 runtime on servers, and change the runtime setting in cloud services such as Azure App Service.

The upgrade guide also notes that the GitHub Copilot modernization agent can make the project file changes for you, and the announcement lists the .NET Upgrade Assistant as a resource.

A worked example: an ASP.NET Core API in a container

Say you run an API on .NET 8 in Docker, built by a GitHub Actions workflow. The upgrade touches four places:

  • Project file: net8.0 becomes net10.0.
  • Dockerfile: FROM mcr.microsoft.com/dotnet/aspnet:8.0 becomes aspnet:10.0, and the SDK build image changes the same way. Because default .NET 10 images use Ubuntu, check that any package install commands in the file still work.
  • global.json: if it pins an 8.0 SDK, change it to a 10.0 version.
  • Workflow: the dotnet-version input of the setup-dotnet action becomes 10.0. While you are editing workflows, check your triggers too: our explainer on pull_request_target vs pull_request covers a common risk.

Then build, run your tests and deploy to a test environment before production.

Troubleshooting

  • The build fails after you change TargetFramework. The SDK reports warnings and errors for anything else that must change. Try dotnet workload restore, then read the .NET 10 breaking changes list.
  • The container build or image fails. Default .NET 10 images use Ubuntu, so check that any package install commands in the Dockerfile still work, and that the SDK build image was changed too.
  • The old version still shows up. Check global.json for an 8 or 9 SDK pin, the version value in your CI pipeline, and the runtime setting in your cloud service. Then run dotnet --list-runtimes and dotnet --list-sdks again on the machine.
  • The runtime list shows versions starting with 8 or 9. Those versions lose support on 10 November 2026. Microsoft's advice is to uninstall versions you no longer use.
  • You are on .NET Framework 4.8. It is a different product and is not covered by this date. See the .NET Framework section above.
  • You cannot upgrade in time. Install the latest patch and "accelerate your plans to remove your use of that .NET version," as Microsoft's policy advises.

What is confirmed and what is not yet known

Confirmed

.NET 8 and .NET 9 end of support is 10 November 2026. .NET 10 is LTS with support to 14 November 2028. As of 9 November 2026, .NET 11 is a release candidate and, as an odd-numbered release, STS.

Not yet known

As of 9 November 2026, Microsoft had not published the .NET 11 release date or its end-of-support date.

If you cannot upgrade in time, Microsoft's policy advice is to install the latest patch, uninstall versions you no longer use, and "accelerate your plans to remove your use of that .NET version." For apps you bought rather than wrote, the announcement suggests asking the vendor for a .NET 10 version. You can find more explainers like this on the Dexaloop Tech hub.

Questions

When does .NET 8 support end?

Microsoft's support policy lists 10 November 2026 as the end of support for .NET 8. It is a Patch Tuesday, the date Microsoft aligns .NET end-of-life dates with.

Why does .NET 9 end on the same day as .NET 8?

In September 2025 Microsoft increased support for STS releases from 18 months to 24 months, starting with .NET 9. That moved the .NET 9 end of support from 12 May 2026 to 10 November 2026.

Will my .NET 8 app stop working after end of support?

No. Microsoft says applications built on .NET 8 or .NET 9 will continue to run. What stops is servicing: no new security fixes, updates or technical support for those versions.

Should I upgrade to .NET 10 or wait for .NET 11?

For most apps, .NET 10. It is an LTS release supported until 14 November 2028. As of 9 November 2026, .NET 11 is a release candidate, and as an odd-numbered STS release it gets two years of support once it ships.

Does this affect .NET Framework 4.8?

No. .NET Framework is a separate product that follows Microsoft's Component Lifecycle Policy. Microsoft's lifecycle page lists no end date for .NET Framework 4.8 or 4.8.1.

How do I check which .NET version my app uses?

Open the project file and read the TargetFramework value, such as net8.0. To see what is installed on a machine, run dotnet --list-runtimes and dotnet --list-sdks.

Sources

Written from the sources above and checked against them before publishing. Found a mistake? Email support@dexaloop.com and we will correct it.

More in Software and development