Skip to main content
BumbleTap
Add to ChromeInstall

.NET 6 End of Life (EOL): Support Ended 12 November 2024, What to Do Now

.NET 6 reached end of support on 12 November 2024 with its final patch, 6.0.36. Apps keep running, but Microsoft no longer fixes it, and .NET 8, the usual next step, ended in November 2026. Who still carries .NET 6, what has broken since, and how to move to .NET 10.

Written Shahzeb Umer

Subscribe

Status

No longer supportedLTS

Support ended .

Since end of life
737 days
Final release
6.0.36
Move to
Microsoft .NET 10fixed until 14 Nov 2028

3 years of support

  • Supported8 Nov 2021 – 12 Nov 2024
  • No fixes12 Nov 2024 – today

Supported for 3 years, from 8 Nov 2021 to 12 Nov 2024.

Who still patches it

Nine places Microsoft .NET 6 runs, five deadlines.

  • Microsoft (runtime, ASP.NET Core, SDK): Ended 12 Nov 2024, final 6.0.36
  • Azure App Service (Windows and Linux): Runs unpatched, no end set
  • Azure Functions (isolated and in-process): Runs unpatched, may get 1 instance
  • AWS Lambda (dotnet6): Updates blocked 31 Aug 2027
  • Ubuntu 22.04 (dotnet6, Main): 6.0.136; later CVEs deferred
  • RHEL 8, 9 (dotnet6.0): Ended 12 Nov 2024
  • Amazon Linux 2023 (dotnet6.0): End of support 12 Nov 2024
  • Container images (mcr.microsoft.com/dotnet, 6.0): Last built Jan 2025
  • HeroDevs NES (paid, third party): Paid, price on request
Sources: .NET support policy and release metadata, Microsoft Lifecycle, Azure App Service and Azure Functions documentation, AWS Lambda runtimes, Ubuntu archive and CVE tracker, Red Hat .NET life cycle and errata, Amazon Linux 2023 package list, Microsoft Container Registry and dotnet-docker, HeroDevs. Checked 17 Nov 2026.

Where to move

Be on Microsoft .NET 10.

The short version

  • .NET 6 reached end of support on 12 November 2024, three years after its release as a long-term support (LTS) release on 8 November 2021. Its final patch, 6.0.36, with SDKs 6.0.428 and 6.0.136, shipped that day with no security fixes; the last security patch was 6.0.35, on 8 October 2024. Microsoft's release metadata lists no .NET 6 release since.
  • Apps keep running, unpatched. Azure App Service and Azure Functions still run them, and AWS Lambda accepts updates to dotnet6 functions until 31 August 2027. Ubuntu 22.04 still ships dotnet6 in Main, but its CVE tracker shows no fix since: 69 later CVEs are marked deferred. HeroDevs sells patched builds.
  • Move to .NET 10, supported until 14 November 2028. Don't stop at .NET 8, which reached end of support on 10 November 2026. Budget for four versions of breaking changes, chiefly EF Core's Encrypt=True default, the container port moving to 8080, BinaryFormatter and, on Azure Functions, leaving the in-process model.
On this page
  1. What ended on 12 November 2024
  2. What has happened since
  3. Who still patches .NET 6
  4. What ends next
  5. How to check what you run
  6. Which version to move to: 10
  7. How to upgrade from .NET 6 to .NET 10
  8. Sources

.NET 6 reached end of support on 12 November 2024. That day Microsoft released its final patch, 6.0.36, with SDKs 6.0.428 and 6.0.136, and stopped servicing the release. Its announcement put it plainly: "Security fixes and technical support will no longer be available for .NET 6."

Your apps keep running. Nothing in the runtime checks the date, and a service on 6.0.36 behaves now as it did in November 2024. What ended is the supply of fixes, and two years on the gap is wide: vulnerabilities found since in ASP.NET Core and the runtime have been fixed for supported versions only.

.NET 6 came out on 8 November 2021 as a long-term support (LTS) release, which Microsoft supports for three years. The usual next step, .NET 8, reached end of support itself on 10 November 2026, so the oldest .NET that Microsoft still patches is now .NET 10, supported until 14 November 2028. The .NET hub has every version's dates.

What ended on 12 November 2024

The last patch shipped, without security fixes. Microsoft had said .NET 6 "may be updated one last time, on that day, if there is a known critical issue", and 6.0.36 "carries non-security fixes" only. The last security release was 6.0.35, on 8 October 2024, which fixed three denial-of-service vulnerabilities: CVE-2024-43483, CVE-2024-43484 and CVE-2024-43485. Over its three years, Microsoft's release metadata lists 49 distinct CVEs fixed in .NET 6.

ASP.NET Core 6 and Entity Framework Core 6 ended with it. Both follow the .NET lifecycle. EF Core 7, which also ran on .NET 6, had already ended on 14 May 2024, alongside .NET 7.

Azure stopped patching it. Microsoft's Lifecycle site lists ".NET 6 LTS on App Service" and "Azure Functions - .NET 6 community EOS" among its retirements on 12 November 2024. App Service keeps such apps running "unchanged", but "can't provide security patches or related customer support" for the runtime, and removes outdated runtimes from the portal's create and configure pages. Azure Functions apps on .NET 6 "can still be created and deployed, and they continue to run", without security patches, and Microsoft may limit them to a single instance.

Visual Studio marked it out of support. Microsoft said the January 2025 servicing updates for Visual Studio 2022 17.8, 17.10 and 17.12 would mark the .NET 6 component out of support, that existing installations wouldn't be affected, and that the installer's "remove out of support components" option takes it out.

Builds started to warn, some of them. Newer SDKs raise NETSDK1138 for a project that targets net6.0: "The target framework 'net6.0' is out of support and will not receive security updates in the future." The check is on by default only for projects that aren't class libraries, so net6.0 libraries build without a word. Someone may also have set CheckEolTargetFramework to false to silence it.

What has happened since

AWS Lambda deprecated dotnet6 on 20 December 2024. AWS may no longer apply security patches to the runtime, functions using it are no longer eligible for technical support, and the Lambda console no longer creates or updates them.

Microsoft's container images stopped. Microsoft removed the .NET 6 images from its dotnet-docker repository on 4 December 2024. The registry shows the 6.0 and 6.0-alpine images were last built in January 2025, with 6.0.36 on Debian 11 and Alpine 3.20. They still pull, but unsupported tags "will no longer receive updates for any reason", so the operating system underneath hasn't been patched since either.

The one Microsoft extension ran out. Microsoft said it would provide security updates for .NET 6 in the Windows Server 2022 Azure Marketplace image "through August 12, 2025", because those images had bundled .NET 6. Newer images include no .NET at all, so a VM built from one needs .NET deployed separately.

Critical fixes went to other versions. In October 2025 Microsoft fixed CVE-2025-55315, an HTTP request-smuggling flaw in ASP.NET Core rated 9.9 out of 10, for ASP.NET Core 8 and 9 and the .NET 10 release candidate, and even for the Kestrel package of ASP.NET Core 2.3, which runs on .NET Framework and is still supported. There was no .NET 6 fix. Ubuntu marked its .NET 6 package "deferred until information is available to determine if it is impacted".

Microsoft's NuGet packages dropped net6.0. From version 9.0, released with .NET 9 in November 2024, packages such as System.Text.Json and Microsoft.Extensions.Logging have no net6.0 build: they target net8.0 and net9.0, plus .NET Standard and .NET Framework. A .NET 6 project that takes one gets the .NET Standard build and a build warning that the package "doesn't support net6.0 and has not been tested with it". Their 8.0 versions were the last with net6.0 builds, and they belong to .NET 8, which has now ended too.

The Azure Functions in-process model ended. Its support ended on 10 November 2026, the same day as .NET 8's. The model stops at .NET 8, so a .NET 6 in-process app has to move to the isolated worker model to reach any supported .NET.

Who still patches .NET 6

Where it runs Status as of 17 November 2026 What happens next Source
Microsoft: runtime, ASP.NET Core, SDK Ended 12 November 2024; final patch 6.0.36, SDKs 6.0.428 and 6.0.136 No fixes or technical support Support policy
Windows Server 2022 Azure Marketplace image Microsoft security updates for its bundled .NET 6 ran to 12 August 2025 Ended; newer images include no .NET Microsoft
Azure App Service, Windows and Linux Runs unchanged, without security patches or related support; removed from the portal's create pages No removal date; subscription owners get an email before a runtime is removed App Service policy
Azure Functions, isolated worker model Apps can still be created, deployed and run, without security patches; may be limited to one instance Move to .NET 10; from Linux Consumption, via Flex Consumption Functions policy
Azure Functions, in-process model .NET 6 support ended 12 November 2024; the model's own support ended 10 November 2026 Migrate to the isolated worker model Functions languages
AWS Lambda, dotnet6 on Amazon Linux 2 Deprecated 20 December 2024: no guaranteed patches, no technical support, no console create or update Create blocked 29 July 2027, update blocked 31 August 2027; invocations continue Lambda runtimes
Ubuntu 22.04, dotnet6 in Main 6.0.136 in the updates pocket since 8 January 2025, 6.0.135 in the security pocket 69 later CVEs marked deferred, none fixed Ubuntu CVE tracker
Ubuntu 24.04, ppa:dotnet/backports Canonical lists it as no longer maintained Best-effort support stopped at Microsoft's date Canonical
RHEL 8 and 9, dotnet6.0 Red Hat's life cycle ended it on 12 November 2024; its last .NET 6 security advisories, in October 2024, shipped 6.0.35 Red Hat follows Microsoft's life cycle Red Hat, RHSA-2024:7867
Amazon Linux 2023, dotnet6.0 Still in the repository at 6.0.36, marked End of Support since 12 November 2024 No updates AL2023 packages
mcr.microsoft.com/dotnet images, 6.0 Last built January 2025 with 6.0.36; removed from the repository 4 December 2024 Still pull, never updated Supported tags
HeroDevs NES for .NET Paid patched builds for .NET 6, 8 and 9 No end date announced; price on request HeroDevs

Ubuntu's promise and Ubuntu's record disagree. Microsoft's Ubuntu guide says Canonical supports .NET versions in the built-in feed "for the lifetime of that Ubuntu version, even beyond the Microsoft-provided support lifetime", and Microsoft's end-of-support post quoted Canonical's Ubuntu Pro promise of ten years of security coverage for packages in Main and Universe. The CVE tracker shows something else for dotnet6 on 22.04. Of the CVEs published since 12 November 2024 that it tracks against the package, as of 17 November 2026 it marks 69 "deferred", 3 "ignored", with the note ".NET 6 and .NET 7 are end of life upstream", and 64 "not affected". It has released a fix for none of them. The package hasn't changed since 6.0.136, Ubuntu's build of Microsoft's final release, and the security pocket still holds 6.0.135. Treat Ubuntu's .NET 6 as unpatched, and plan around Microsoft's date. Ubuntu 22.04 has its own dates.

Red Hat follows Microsoft. Red Hat's life cycle page says "Microsoft establishes and maintains the life-cycle support policy for .NET on Red Hat Enterprise Linux", and lists .NET 6 on RHEL 8 and 9 as ending on 12 November 2024. Support for .NET on RHEL 7 ended earlier, on 30 June 2024.

Paid support comes from a third party. HeroDevs says NES for .NET covers the runtime, SDK, ASP.NET Core, Entity Framework, WPF and WinForms, and lets you "stay on your current version and remain supported until you are ready to upgrade". It publishes no prices and licenses by the number of users who commit code. Microsoft's Lifecycle site says end of support brings no "free or paid assisted support options".

What ends next

AWS Lambda: 29 July and 31 August 2027. Until the first date you can still create dotnet6 functions through the AWS CLI, AWS SAM or CloudFormation, though not in the console, and until the second you can update them. After 31 August a deploy to a dotnet6 function fails. You can still move it to a supported runtime, but rolling back may be blocked. The runtime also sits on Amazon Linux 2, whose end of life AWS set for 30 June 2026, and dotnet6 isn't among the Amazon Linux 2 runtimes AWS says still get operating system patches.

Azure Functions on Linux Consumption. .NET 9 is the last .NET version that plan supports, and the plan itself retires on 30 September 2028. A .NET 6 app on Linux Consumption has to move to Flex Consumption before it can run .NET 10.

How to check what you run

On a machine or in a container:

dotnet --list-runtimes   # Microsoft.NETCore.App 6.0.x or Microsoft.AspNetCore.App 6.0.x means .NET 6
dotnet --list-sdks       # 6.0.428 and 6.0.136 are the last .NET 6 SDKs
dotnet --info            # also shows which global.json, if any, picked the SDK
apt list --installed 'dotnet*' 'aspnetcore*' 2>/dev/null   # Ubuntu's packages
rpm -qa 'dotnet*' 'aspnetcore*' 2>/dev/null                # RHEL and Amazon Linux packages

In your repositories:

grep -rhoE --include='*.csproj' --include='*.fsproj' --include='*.vbproj' --include='Directory.Build.props' \
  '<TargetFrameworks?>[^<]+' . | sort | uniq -c        # net6.0 needs to move, and so does net8.0
cat global.json 2>/dev/null                            # a 6.0.xxx SDK pins an out-of-support SDK
grep -rnE --include='Dockerfile*' 'mcr\.microsoft\.com/dotnet/[a-z-]+:6\.0' .
grep -rnE "dotnet-version: *['\"]?6\." .github/workflows/
grep -rn 'CheckEolTargetFramework' .                   # someone switched off the NETSDK1138 warning

On your platforms:

# Azure App Service on Linux: DOTNETCORE|6.0 means .NET 6
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
az functionapp show --name APP --resource-group RG --query "siteConfig.netFrameworkVersion" -o tsv   # v6.0 on Windows

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

Which version to move to: 10

Move to .NET 10. It is the current LTS release, supported until 14 November 2028, and its latest patch is 10.0.15, from 10 November 2026. AWS Lambda has a dotnet10 runtime, Azure Functions runs it on the isolated worker model, and Ubuntu 24.04 ships it in its own archive.

Don't stop at .NET 8. Microsoft's 2024 advice was to retarget .NET 6 apps to .NET 8, but .NET 8 reached end of support on 10 November 2026, with 8.0.34 as its final patch. An app moved to 8 now is on an unsupported release again. The .NET 8 page covers what ended.

.NET 11 buys features, not time. It came out on 10 November 2026 as a Standard Term Support release and also ends on 14 November 2028, and Lambda has no dotnet11 runtime. The .NET 11 page covers when its features are worth taking.

Version Support Latest patch Visual Studio to target it AWS Lambda
6 (LTS) Ended 12 November 2024 6.0.36, final 2022, 17.0 or later dotnet6, deprecated
8 (LTS) Ended 10 November 2026 8.0.34, final 2022, 17.8 or later dotnet8, deprecated
10 (LTS) Until 14 November 2028 10.0.15 2026, 18.0 or later dotnet10, deprecated 14 November 2028
11 (STS) Until 14 November 2028 11.0.0 2026, 18.12 or later None

Whichever you pick, you move again before November 2028. .NET 12, expected in November 2027, will be the next LTS release: Microsoft ships a major version every November, and the even-numbered ones are LTS.

How to upgrade from .NET 6 to .NET 10

  1. Install the tools first: Visual Studio 2026 or the .NET 10 SDK, 10.0.404 at present, and update global.json. The new SDK still builds net6.0 projects, because Microsoft keeps targeting support for out-of-support versions, so the SDK can move before the code does.
  2. Retarget. Change <TargetFramework>net6.0</TargetFramework> to net10.0, then move every Microsoft.AspNetCore.*, Microsoft.EntityFrameworkCore.* and Microsoft.Extensions.* package to 10.0.x.
  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 6 build.

Going straight from 6 to 10 is normal, but skipping 7, 8 and 9 doesn't skip their breaking changes. These are the ones most likely to cost time, with the version that brought each; Microsoft's lists for 7, 8, 9 and 10 have the rest, and the .NET 10 page covers the later ones in more detail.

SQL Server connections encrypt by default (EF Core 7). Microsoft.Data.SqlClient, which EF Core 7 and later use, defaults to Encrypt=True, so a server without a certificate the client trusts now fails at login with "The certificate chain was issued by an authority that is not trusted." Installing a trusted certificate is the fix. TrustServerCertificate=True or Encrypt=False also work, but Microsoft warns both leave the server "in a potentially insecure state".

SQL Server tables with triggers (EF Core 7). EF Core saves changes with a faster technique that SQL Server doesn't support on tables with triggers or certain computed columns. Tell EF about such tables with ToTable(tb => tb.UseSqlOutputClause(false)), the EF Core 8 and later form.

BinaryFormatter is gone (7, 8 and 9). Its Serialize and Deserialize calls became compile errors in 7 and threw at runtime in most app types in 8, and in 9 the built-in implementation "throws exceptions on use, even with the settings that previously enabled its use". A separate, unsupported NuGet package restores it; moving to another serializer is the real fix.

The container port moved to 8080 (8). Microsoft's ASP.NET Core images listen on 8080 instead of 80 from 8.0 on, so a -p 8000:80 mapping, a Kubernetes service or an App Service WEBSITES_PORT that assumed 80 stops connecting. Move the mapping to 8080 or set ASPNETCORE_HTTP_PORTS=80. Apps built on the older WebHost.CreateDefaultBuilder() ignore that variable and fall back to http://localhost:5000, so set ASPNETCORE_URLS for them instead.

Publishing changed (8). dotnet publish uses the Release configuration by default, which breaks scripts that hard-code a Debug output path. An app with a RuntimeIdentifier is no longer self-contained by default either, so a machine without the .NET runtime can't start it unless you set SelfContained explicitly.

The container OS changed (10). The default 6.0 tags were Debian 11. 10.0 is Ubuntu 24.04, and Microsoft publishes no Debian images for .NET 10, so apt-get package names and anything that inspects the OS need checking.

NuGet audits transitive packages (10). For projects targeting .NET 10, NuGetAuditMode defaults to all, so a vulnerable package deep in the dependency graph raises a warning, which fails restores that treat warnings as errors. dotnet nuget why <package> finds what pulled it in.

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

Azure Functions in-process to isolated. If FUNCTIONS_WORKER_RUNTIME is dotnet, there is no in-process version to move to. [FunctionName] becomes [Function], Microsoft.Azure.WebJobs.* packages give way to Microsoft.Azure.Functions.Worker.Extensions.*, and the setting becomes dotnet-isolated. Serialization moves to System.Text.Json, which ignores Newtonsoft attributes such as [JsonProperty] without an error. Changing the setting and publishing the code are two restarts with a mismatch between them, so do both in a staging slot and swap.

For ASP.NET Core apps, Microsoft's migration guides go one version at a time: 6 to 7, 7 to 8, 8 to 9 and 9 to 10.

Sources

Common questions

What is the .NET 6 end of support date?
12 November 2024, Microsoft's Patch Tuesday that month. .NET 6 was a long-term support (LTS) release, supported for three years from its release on 8 November 2021. Its final patch, 6.0.36, shipped the same day. Microsoft's support policy, its release metadata and its Lifecycle site all give the same date.
Is .NET 6 still supported?
Not by Microsoft. Since 12 November 2024 it has provided no security fixes or technical support for .NET 6. A few places still carry it on their own terms: Azure App Service and Azure Functions run it unpatched, AWS Lambda accepts updates to dotnet6 functions until 31 August 2027, and HeroDevs sells patched builds. Move to .NET 10.
What is the last version of .NET 6?
6.0.36, released on 12 November 2024, with SDKs 6.0.428 and 6.0.136. It carried only non-security fixes. The last .NET 6 security release was 6.0.35, on 8 October 2024, which fixed three denial-of-service vulnerabilities. If you must run .NET 6 a while longer, run 6.0.36: no later build will come from Microsoft.
Do .NET 6 apps still run after end of support?
Yes. Microsoft said apps that use .NET 6 "will continue to run", and nothing in the runtime checks the date. What stopped is the fixes. Vulnerabilities found since, such as CVE-2025-55315, an ASP.NET Core request-smuggling flaw rated critical in October 2025, were fixed for supported versions only.
Is .NET Core 6 the same as .NET 6?
Yes. Microsoft dropped "Core" from the name with .NET 5 in 2020, so .NET Core 6 means .NET 6, which reached end of support on 12 November 2024. ASP.NET Core 6 and Entity Framework Core 6 ended the same day. The last release actually named .NET Core, 3.1, ended on 13 December 2022.
Should I upgrade from .NET 6 to .NET 8 or .NET 10?
To .NET 10. Microsoft's advice in 2024 was .NET 8, but .NET 8 reached end of support on 10 November 2026, so moving to it now lands you on another unsupported release. .NET 10 is the current LTS release, supported until 14 November 2028, with runtimes on AWS Lambda and Azure Functions. .NET 11 ends on the same day, so it adds features but no time.
What happens to .NET 6 on Azure App Service and Azure Functions?
Apps keep running. App Service "can't provide security patches or related customer support" for an end-of-support runtime and removes it from the portal's create and configure pages. Functions apps on .NET 6 can still be deployed and run, without security patches, and may be limited to one instance. In-process apps have a second problem: that model's own support ended on 10 November 2026.
What happens to .NET 6 on AWS Lambda?
AWS deprecated the dotnet6 runtime on 20 December 2024. Since then AWS may no longer patch it, functions using it get no technical support, and the console no longer creates or updates them. Lambda blocks creating dotnet6 functions from 29 July 2027 and updating them from 31 August 2027. Existing functions can still be invoked. Move to dotnet10.
Can I pay for extended support for .NET 6?
Not from Microsoft. Its Lifecycle site says end of support leaves no "free or paid assisted support options", and its one exception, security updates for .NET 6 in the Windows Server 2022 Azure Marketplace image, ran only to 12 August 2025. HeroDevs sells Never-Ending Support (NES) for .NET 6, 8 and 9: patched builds of the runtime, SDK, ASP.NET Core and Entity Framework, with prices on request.

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