Skip to main content
BumbleTap
Add to ChromeInstall

.NET 10 End of Life (EOL): 14 November 2028, and Moving From .NET 8 and 9

Microsoft supports .NET 10, the current LTS release, until 14 November 2028. It is where .NET 8 and 9 apps go now that both lost support on 10 November 2026: where it runs, and what breaks.

Written Shahzeb Umer

Subscribe

Status

SupportedLTS

Support ends .

Time left
726 days
Latest release
10.0.15
Support type
Long-term support

3 years of support

  • Supported11 Nov 2025 – 14 Nov 2028

Supported for 3 years, from 11 Nov 2025 to 14 Nov 2028.

Who still patches it

Eight places Microsoft .NET 10 runs, eight deadlines.

  • Microsoft (runtime, ASP.NET Core, SDK): Patched to 14 Nov 2028
  • Azure App Service (Windows and Linux): Follows Microsoft, 14 Nov 2028
  • Azure Functions (isolated worker model): Support ends 14 Nov 2028
  • AWS Lambda (dotnet10): Updates blocked 15 Jan 2029
  • Ubuntu 24.04, 26.04 (dotnet10, Main): Upstream fixes to 14 Nov 2028
  • RHEL 8.10, 9, 10 (dotnet-sdk-10.0): Follows Microsoft, 14 Nov 2028
  • Amazon Linux 2023 (dotnet-sdk-10.0): Patched to 14 Nov 2028
  • Container images (mcr.microsoft.com/dotnet, 10.0): Rebuilt to 14 Nov 2028
Sources: .NET support policy and release metadata, Azure App Service and Azure Functions language support, AWS Lambda runtimes, Ubuntu archive, Red Hat .NET life cycle, Amazon Linux 2023 package list, dotnet-docker. Checked 15 Nov 2026.

Where to move

Be on Microsoft .NET 10.

The short version

  • .NET 10 is the current long-term support (LTS) release, supported by Microsoft until 14 November 2028. It came out on 11 November 2025, and its latest patch is 10.0.15, from 10 November 2026: the day .NET 8 and .NET 9 reached end of support, with 8.0.34 and 9.0.23 as their final patches.
  • It runs where .NET 8 did: Azure App Service on Windows and Linux, Azure Functions' isolated worker model, AWS Lambda's dotnet10 runtime, Ubuntu 24.04 and 26.04's own archive, RHEL 8.10, 9 and 10, Amazon Linux 2023 and Microsoft's container images, whose 10.0 tags are Ubuntu 24.04 rather than Debian.
  • Move .NET 8 and 9 apps to 10 now. .NET 11 ends on the same day, so choosing 10 costs no support time, and 10 is the version AWS Lambda, Red Hat and Ubuntu's archive carry. Budget time for BinaryFormatter, NuGet's transitive audit, EF Core 10 and, on Azure Functions, leaving the in-process model.
On this page
  1. What support until 14 November 2028 means
  2. What 10 November 2026 ended
  3. Who runs or patches .NET 10, and until when
  4. Tools you need
  5. How to check what you run
  6. How to upgrade from .NET 8
  7. Changes most likely to bite from 8 to 10
  8. After .NET 10
  9. Sources

.NET 10 is supported until 14 November 2028. Microsoft released it on 11 November 2025 as a long-term support (LTS) release, which gets three years of free support and patches, and its end date falls on Microsoft's Patch Tuesday.

It is now the oldest .NET that Microsoft still patches. .NET 8 and .NET 9 both reached end of support on 10 November 2026, the day that brought 10.0.15 and the first release of .NET 11. This page covers the move from 8 or 9 to 10; the .NET hub has every version's dates.

What support until 14 November 2028 means

Only the newest patch is supported. Servicing updates arrive almost every month, the ones with security fixes on Patch Tuesday, and once 10.0.16 ships, 10.0.15 stops being a supported level. 10.0.15 itself carried more than a dozen CVE fixes, across ASP.NET Core, the runtime and Visual Studio components. The last six months before 14 November 2028 are maintenance support, with security fixes only. ASP.NET Core 10 and Entity Framework Core 10 follow the same lifecycle.

The SDK has its own dates. Each quarterly feature band is supported separately:

SDK band Ships with Visual Studio Supported until
10.0.1xx 18.0 November 2028
10.0.2xx 18.4 Ended May 2026
10.0.3xx 18.6 Ended August 2026
10.0.4xx 18.9 November 2028

Distributions such as Ubuntu build the 1xx band from source, which is why Ubuntu's dotnet-sdk-10.0 is 10.0.115 while Microsoft's download page leads with 10.0.404. Both carry the 10.0.15 runtime.

.NET 11 doesn't buy more time. Since Microsoft extended Standard Term Support (STS) to 24 months in September 2025, each odd-numbered release ends on the same day as the LTS release before it. .NET 11, released on 10 November 2026, also ends on 14 November 2028. The .NET 11 page covers when its features are worth taking.

What 10 November 2026 ended

  • Microsoft's patches for 8 and 9. .NET 8 shipped its final patch, 8.0.34, and .NET 9 shipped 9.0.23, both security releases. The next vulnerability found in either gets no fix.
  • Azure's support for them. App Service keeps running .NET 8 and 9 apps unchanged but "can't provide security patches or related customer support" for them, and hides outdated runtimes from the portal's create and configure pages. Azure Functions apps keep running and deploying without patches, and may be limited to a single instance.
  • The Azure Functions in-process model. Its support ended the same day. Its last supported version was .NET 8, so every in-process app has to move to the isolated worker model to reach .NET 10.
  • AWS Lambda's dotnet8 runtime, now deprecated. Lambda blocks creating dotnet8 functions from 29 July 2027 and updating them from 31 August 2027; invocations continue. .NET 9 was only ever a container base image there.
  • Microsoft's 8.0 and 9.0 container tags. They have left the supported tag list. Images still pull, but "will no longer receive updates for any reason".

Distribution packages are the exception people hope for. Ubuntu 22.04 and 24.04 keep dotnet8 in Main, and Microsoft's Ubuntu guide says Canonical supports archive versions "for the lifetime of that Ubuntu version, even beyond the Microsoft-provided support lifetime". The record so far is thin: 22.04's dotnet6 package hasn't moved past 6.0.136, its build of Microsoft's final .NET 6 release from November 2024, the month .NET 6 ended. Plan around Microsoft's date, on Ubuntu too.

Who runs or patches .NET 10, and until when

Where it runs Until / status What happens after Source
Microsoft: runtime, ASP.NET Core, SDK 14 November 2028; 10.0.15 since 10 November 2026 No more patches of any kind Support policy
Azure App Service, Windows and Linux Generally available since November 2025; follows Microsoft's date Apps keep running, without security patches App Service policy
Azure Functions, isolated worker model Generally available; end of support 14 November 2028. Not on Linux Consumption Apps run and deploy, unpatched; possibly one instance Functions languages
Azure Functions, in-process model Support ended 10 November 2026; never ran .NET 10 Migrate to the isolated worker model Functions languages
AWS Lambda, dotnet10 on Amazon Linux 2023 Generally available since 8 January 2026; deprecated 14 November 2028 Create blocked 14 December 2028, update blocked 15 January 2029; invocations continue Lambda runtimes
Ubuntu 24.04 and 26.04, dotnet10 in Main 10.0.15 (SDK 10.0.115) in the security and updates pockets Canonical's commitment past November 2028 is untested Ubuntu archive
RHEL 8.10, 9 and 10, dotnet-sdk-10.0 Shipped November 2025; "Microsoft establishes and maintains the life-cycle" Follows Microsoft's date Red Hat
Amazon Linux 2023, dotnet-sdk-10.0 End of support 14 November 2028 Leaves Amazon Linux's support AL2023 packages
mcr.microsoft.com/dotnet images, 10.0 Rebuilt for each release and monthly; 10.0 is Ubuntu 24.04 Tags stop updating at end of support, or when the base OS ends dotnet-docker
GitHub-hosted runners SDKs 10.0.115 to 10.0.404 preinstalled No end announced runner-images

Linux Consumption is a dead end. Azure Functions can't run .NET 10 or later on the Linux Consumption plan, which gets no new language versions and retires on 30 September 2028. Microsoft points those apps to Flex Consumption.

The container OS changes with the tag. mcr.microsoft.com/dotnet/aspnet:8.0 was Debian. 10.0 is Ubuntu 24.04, and Microsoft publishes no Debian images for .NET 10. Other 10.0 variants include 10.0-resolute (Ubuntu 26.04), 10.0-noble-chiseled, 10.0-alpine (Alpine 3.24), Azure Linux 3.0, and Windows Nano Server and Server Core for 2022 and 2025. latest now points to .NET 11, so pin 10.0.

Ubuntu's own packages are the simplest route on Ubuntu. sudo apt install dotnet-sdk-10.0 works on 24.04 and 26.04 without adding a repository. Microsoft stopped publishing .NET to its own package feed for Ubuntu starting with 24.04.

Tools you need

Visual Studio 2026, version 18.0 or later. Microsoft supports targeting net10.0 only from 18.0. Visual Studio 2022 version 17.14 can load the 10 SDK, but targeting .NET 10 from it isn't supported and produces a build warning.

In GitHub Actions, actions/setup-dotnet@v6 installs any band, and GitHub's Ubuntu and Windows images already include 10.0 SDKs, with windows-latest on Visual Studio 2026. A global.json keeps local machines and CI on the same SDK:

{
  "sdk": {
    "version": "10.0.100",
    "rollForward": "latestFeature"
  }
}

How to check what you run

On a machine or in a container:

dotnet --list-runtimes     # Microsoft.NETCore.App 10.0.15, Microsoft.AspNetCore.App 10.0.15
dotnet --list-sdks         # 10.0.404 or 10.0.115 is current
dotnet --info              # also shows which global.json, if any, picked the SDK

In your repositories:

grep -rhoE --include='*.csproj' --include='*.fsproj' --include='Directory.Build.props' \
  '<TargetFrameworks?>[^<]+' . | sort | uniq -c
cat global.json 2>/dev/null
grep -rnE --include='Dockerfile*' 'mcr\.microsoft\.com/dotnet/[a-z-]+:(8|9)\.0' .
grep -rnE "dotnet-version: *['\"]?(8|9)\." .github/workflows/
dotnet list package --vulnerable --include-transitive

On your platforms:

# Azure App Service on Linux: DOTNETCORE|8.0 means .NET 8
az webapp config show --name APP --resource-group RG --query linuxFxVersion -o tsv

# Azure Functions: "dotnet" is the in-process model, "dotnet-isolated" the isolated worker
az functionapp config appsettings list --name APP --resource-group RG \
  --query "[?name=='FUNCTIONS_WORKER_RUNTIME'].value" -o tsv

# AWS Lambda: once per region and account
aws lambda list-functions --function-version ALL --region us-east-1 --output text \
  --query "Functions[?Runtime=='dotnet8'].FunctionArn"

How to upgrade from .NET 8

  1. Install the tools first: Visual Studio 2026 or the 10.0.404 SDK, and update global.json.
  2. Retarget. Change <TargetFramework>net8.0</TargetFramework> to net10.0, then move every Microsoft.AspNetCore.*, Microsoft.EntityFrameworkCore.* and Microsoft.Extensions.* package to 10.0.x. Leaving EF Core on 8 or 9 means an out-of-support EF.
  3. Build with warnings visible and work through the obsoletions and NuGet audit warnings before suppressing anything.
  4. Change where it runs: FROM lines to 10.0, dotnet-version in CI, DOTNETCORE|10.0 on App Service for Linux, dotnet10 on Lambda, and the .NET 10 isolated worker stack on Functions.
  5. Test behind a slot or canary, then retire the .NET 8 build.

Going straight from 8 to 10 is normal: there is no reason to stop at 9, which is also out of support. Read Microsoft's breaking-change lists for both 9 and 10, because skipping a version doesn't skip its changes.

Changes most likely to bite from 8 to 10

From Microsoft's breaking-change lists for .NET 9 and .NET 10, ASP.NET Core and EF Core, roughly in order of how often they cause work.

1. BinaryFormatter always throws (9). High if you use it. The built-in implementation now throws PlatformNotSupportedException, and the old opt-in switches are gone. The unsupported System.Runtime.Serialization.Formatters package restores it, vulnerabilities included; migrating to another serializer is the real fix.

2. NuGet audits transitive packages (10). High for builds with warnings as errors. Projects targeting .NET 10 default to NuGetAuditMode all, so a vulnerable package deep in the graph now raises NU1901 to NU1904. dotnet nuget why <package> finds what pulled it in; upgrading that parent, or referencing the fixed version directly, clears it.

3. EF Core changes, and EF Core 10 needs .NET 10. High if you use EF. EF Core 9 still ran on .NET 8; EF Core 10 requires the .NET 10 runtime, and EF Core 8 and 9 support ended on 10 November 2026. Along the way:

  • EF 9: Migrate() and dotnet ef database update throw when the model has changes no migration captures, often from DateTime.Now or Guid.NewGuid() in HasData.
  • EF 10: Contains() over a parameter list becomes one SQL parameter per value instead of a JSON array, which changes query plans.
  • EF 10: with UseAzureSql or compatibility level 170, JSON columns map to SQL Server's json type, and the next migration alters existing nvarchar(max) JSON columns.
  • Microsoft.Data.Sqlite 10 treats timestamps without an offset as UTC.

4. Azure Functions in-process to isolated. High on Functions. [FunctionName] becomes [Function], Microsoft.Azure.WebJobs.* packages give way to Microsoft.Azure.Functions.Worker.Extensions.*, FUNCTIONS_WORKER_RUNTIME becomes dotnet-isolated, and serialization moves to System.Text.Json, which silently ignores Newtonsoft attributes such as [JsonProperty].

5. ASP.NET Core defaults (9 and 10). Medium.

  • Cookie authentication returns 401 and 403 instead of redirecting to the login page for API endpoints: [ApiController] controllers, minimal APIs that use JSON, and SignalR (10).
  • In Development, the host validates dependency injection scopes at startup, so a scoped service injected into a singleton now fails at launch (9).
  • WebHostBuilder, IWebHost, Razor runtime compilation and WithOpenApi are obsolete, which breaks builds that treat warnings as errors (10).

6. No default SIGTERM handler (10). Medium for containers. The runtime no longer handles SIGTERM itself, so a console app outside the Generic Host exits immediately on docker stop without raising ProcessExit. ASP.NET Core and apps using UseConsoleLifetime are unaffected.

7. The container base OS (10). Medium. Moving from 8.0 to 10.0 tags swaps Debian for Ubuntu 24.04, so apt-get package names and anything that inspects the OS need checking.

8. SDK and CLI details (10). Low to medium for scripts. dotnet new sln creates .slnx files, a PackageReference without a version is an error, NuGet's package pruning raises NU1510 for redundant references, and CLI commands write non-command output to stderr.

9. OpenSSL 1.1.1 or later on Linux (10). Low. Distributions still shipping 1.0.2 or 1.1.0 can't start .NET 10 apps.

After .NET 10

Microsoft releases a new .NET every November, and even-numbered releases are LTS. .NET 12, expected in November 2027, will be the next LTS release, and .NET 10 users have a year from then to move. .NET 11 is the in-between release for anyone who wants C# 15 sooner; it changes features, not dates.

Sources

Common questions

When is .NET 10 end of life?
On 14 November 2028, the second Tuesday of that month and Microsoft's Patch Tuesday. .NET 10 is a long-term support (LTS) release, supported for three years from its release on 11 November 2025. .NET 11, a Standard Term Support release, ends on the same day.
What is the .NET 10 support lifecycle?
Three years of free support and patches, as for every LTS release. Microsoft ships a servicing update almost every month and supports only the newest one, so staying supported means taking each patch. The last six months before 14 November 2028 are maintenance support, with security fixes only.
When did .NET 8 support end?
On 10 November 2026. .NET 8 was an LTS release from 14 November 2023, and its final patch, 8.0.34, shipped that day. .NET 9 ended the same day, with 9.0.23. Neither gets further fixes from Microsoft, and .NET 10 is the release to move to.
Is .NET Core 10 the same as .NET 10?
Yes. Microsoft dropped "Core" from the name with .NET 5 in 2020, so .NET Core 10 means .NET 10, which ends on 14 November 2028. The last release named .NET Core, 3.1, ended on 13 December 2022. The .NET hub lists every version's end date.
When does the .NET 10 SDK reach end of life?
It depends on the feature band. SDK 10.0.1xx and 10.0.4xx are supported until November 2028, while 10.0.2xx ended in May 2026 and 10.0.3xx in August 2026. The current SDKs, from 10 November 2026, are 10.0.404 and 10.0.115. A band that is out of support gets no fixes even while the runtime does.
Should I upgrade from .NET 8 to .NET 10 or .NET 11?
For most apps, .NET 10. Both are supported until 14 November 2028, so 11 adds features but no support time, and 10 is the one AWS Lambda, Red Hat and Ubuntu's archive carry. Either way you need .NET 12, expected in November 2027, before November 2028. The .NET 11 page covers when 11 is worth it.
Do .NET 8 apps still run after end of support?
Yes. Nothing in the runtime checks the date, and Azure App Service and Azure Functions keep running .NET 8 apps, without security patches; Functions may limit unsupported apps to one instance. AWS Lambda deprecated dotnet8 on 10 November 2026 and blocks creating functions from 29 July 2027 and updating them from 31 August 2027.
Which Visual Studio version supports .NET 10?
Visual Studio 2026, version 18.0 or later. Visual Studio 2022 version 17.14 can load the .NET 10 SDK, but Microsoft doesn't support targeting net10.0 from it, and the build warns. Outside Visual Studio, the dotnet CLI builds .NET 10 projects on Windows, Linux and macOS.

Also on the calendar

End-of-life dates for the rest of your stack.

Dates checked against endoflife.date (MIT). How we check datesReport a wrong dateEvery Microsoft .NET version