.NET support dates in November 2026: .NET 8 and 9 have ended, .NET Framework 4.6.2 goes in January
On Tuesday 10 November 2026 Microsoft shipped .NET 11 and, the same day, stopped supporting both .NET 8 and .NET 9. Eight weeks later, on 12 January 2027, .NET Framework 4.6.2 reaches the end of its own support, together with Windows Server 2016. If you maintain ASP.NET sites, old or new, this is the busiest stretch of the support calendar in years. We put every support window Microsoft publishes into one table, a chart and a CSV file.
- 10 Nov 2026end of support for .NET 8 (LTS) and .NET 9 (STS), on the same day
- 12 Jan 2027end of support for .NET Framework 4.6.2 and Windows Server 2016
- 14 Nov 2028end of support for .NET 10 (LTS) and, per Microsoft's release metadata, .NET 11
- 24 monthsnew length of an STS release's support, up from 18, starting with .NET 9
Download the data (CSV, 29 versions)
Two families, two kinds of calendar
The dates below only make sense once you separate the two products that share the ".NET" name, because Microsoft supports them under different policies.
.NET (formerly .NET Core) follows the Modern Lifecycle Policy. A new major version ships every November; even numbers are Long Term Support (LTS) releases with three years of patches, odd numbers are Standard Term Support (STS) releases. Each version has a fixed end date, published on the Microsoft Lifecycle page for .NET and .NET Core. ASP.NET Core and Entity Framework Core share the lifecycle of the .NET version they belong to.
.NET Framework works differently. From version 4.5.2 onwards it is a component of Windows, and the .NET Framework lifecycle FAQ states that it "follows the lifecycle policy of the underlying Windows OS on which it is installed". Versions 4.7 to 4.8.1 therefore have no end date of their own. Some older versions were retired early, on a fixed date, which is what is about to happen to 4.6.2.
For Web Forms the second family is the one that counts. Microsoft's ASP.NET support policy says that "ASP.NET Web Forms, Controls, Modules, Handlers, and more" are part of the .NET Framework and inherit its support. Web Forms was never ported to ASP.NET Core, which is why the three classic ASP.NET programming models still run on .NET Framework today.
The chart: who is still covered on 22 November 2026
The full table
Every version of .NET and .NET Core, with the support start and end dates shown by Microsoft, the number of days of support each one received and the last patch listed in the official release metadata. Rows in the shaded band are still supported.
| Version | Type | Support start | Support end | Days | Last patch |
|---|---|---|---|---|---|
| .NET 11 | STS | 10 Nov 2026 | 14 Nov 2028* | 735 | 11.0.0 |
| .NET 10 | LTS | 11 Nov 2025 | 14 Nov 2028 | 1,099 | 10.0.15 |
| .NET 9 | STS | 12 Nov 2024 | 10 Nov 2026 | 728 | 9.0.23 |
| .NET 8 | LTS | 14 Nov 2023 | 10 Nov 2026 | 1,092 | 8.0.34 |
| .NET 7 | STS | 8 Nov 2022 | 14 May 2024 | 553 | 7.0.20 |
| .NET 6 | LTS | 8 Nov 2021 | 12 Nov 2024 | 1,100 | 6.0.36 |
| .NET 5 | STS | 10 Nov 2020 | 10 May 2022 | 546 | 5.0.17 |
| .NET Core 3.1 | LTS | 3 Dec 2019 | 13 Dec 2022 | 1,106 | 3.1.32 |
| .NET Core 3.0 | STS | 23 Sep 2019 | 3 Mar 2020 | 162 | 3.0.3 |
| .NET Core 2.2 | STS | 4 Dec 2018 | 23 Dec 2019 | 384 | 2.2.8 |
| .NET Core 2.1 | LTS | 30 May 2018 | 21 Aug 2021 | 1,179 | 2.1.30 |
| .NET Core 2.0 | STS | 14 Aug 2017 | 1 Oct 2018 | 413 | 2.0.9 |
| .NET Core 1.1 | LTS | 16 Nov 2016 | 27 Jun 2019 | 953 | 1.1.13 |
| .NET Core 1.0 | LTS | 27 Jun 2016 | 27 Jun 2019 | 1,095 | 1.0.16 |
* The lifecycle page leaves the end date of .NET 11 blank for now; the date shown is the eol-date in Microsoft's releases index, consistent with the 24-month STS rule.
And .NET Framework, as listed on the Microsoft Lifecycle page for .NET Framework:
| Version | Released | Support end |
|---|---|---|
| 4.8.1 | 9 Aug 2022 | follows Windows |
| 4.8 | 18 Apr 2019 | follows Windows |
| 4.7, 4.7.1, 4.7.2 | 2017–2018 | follows Windows |
| 4.6.2 | 2 Aug 2016 | 12 Jan 2027 |
| 4.5.2, 4.6, 4.6.1 | 2014–2015 | 26 Apr 2022 (SHA-1 retirement) |
| 4.0, 4.5, 4.5.1 | 2010–2014 | 12 Jan 2016 |
| 3.5 SP1 | 19 Nov 2007 | 9 Jan 2029 as a standalone product** |
| 2.0, 3.0 | 2006 | 12 Jul 2011 |
** Only from Windows 10 version 1809 and Windows Server 2019; on older Windows versions 3.5 SP1 follows the operating system.
What the numbers show
Two releases expired on one day. That is new. Under the previous rule, applied to .NET 5 and .NET 7, an STS release lasted 18 months and ended roughly six months before the LTS release that preceded it. In September 2025 the .NET team announced: "We are increasing the length of support offered for .NET Standard Term Support (STS) releases from 18 months to 24 months" (.NET Blog, 16 September 2025). The stated reason is out-of-band packages: "Sometimes, an OOB release includes a dependency on an updated version of a package that ships in the annual release train", which could pull an LTS application onto a shorter-lived STS component. InfoQ's report on the change noted at the time that .NET 9 would now be patched until 10 November 2026, the same day as .NET 8.
.NET 9 got 728 days instead of about 550. Measured from start to end date, the STS releases before it got 546 (.NET 5) and 553 days (.NET 7). LTS releases have been remarkably steady: between 1,092 and 1,106 days for every LTS since .NET Core 3.1.
The end is final. In its June 2026 reminder the .NET team wrote that after 10 November 2026 "Microsoft will no longer provide servicing updates, security fixes, or technical support for these versions", and recommended moving to .NET 10. Applications keep running; they just stop receiving patches. The last ones were 8.0.34 and 9.0.23, both dated 10 November.
.NET Framework 4.6.2 is the odd one out. It is the only 4.x version still supported that carries a fixed end date. Microsoft's .NET Framework support policy lists it as active until 12 January 2027. The same day appears on Microsoft's list of products ending support in 2027, alongside Windows Server 2016 and IIS 10 on Windows Server 2016.
What to check on an ASP.NET site this winter
Web Forms, MVC 5 or Web API 2 on .NET Framework. Find out which framework the server actually runs and which one the project targets. The targetFramework attribute of <httpRuntime> and <compilation> in web.config shows what the application was built for; the server can have a newer 4.x installed in place. Because 4.7 to 4.8.1 are in-place updates, the lifecycle FAQ says applications built for earlier 4.x versions are expected to keep running without recompilation, but test before you switch: a small number of changes are not fully compatible. A mismatch between the declared version and what is installed is also a classic cause of the Parser Error at deployment.
Windows Server 2016 hosts. This is the more pressing deadline for many intranet sites. If your server is a 2016 machine, the operating system, IIS 10 and .NET Framework 4.6.2 all leave support on 12 January 2027. Moving to Windows Server 2022 or 2025 also gives you .NET Framework 4.8.1, which the FAQ lists as supported on those versions. If you rent a VPS, ask the host which image you are on; the questions in our guide to choosing ASP.NET hosting apply here too.
ASP.NET Core on .NET 8 or 9. Change the TargetFramework in the project file to net10.0, update the Microsoft.AspNetCore.* and EF Core packages to 10.x, and redeploy. .NET 10 is supported until November 2028; .NET 11, the new STS release, ends on the same day, so the choice between them is about features, not about length of support.
Tooling. Visual Studio 2017 reaches end of support on 13 April 2027, and Visual Studio 2022 leaves mainstream support for extended support on 12 January 2027, according to the same 2027 list. Neither changes how your sites run, but both matter if a build server still uses them.
Read next
- The three ASP.NET programming models: Web Forms, MVC and Web Pages
- Connect to a Windows VPS or server with Remote Desktop
Method, sources and licence
Data. Start and end dates of .NET and .NET Core come from the Microsoft Lifecycle page for .NET and .NET Core (updated 11 November 2026); the end date of .NET 11, release types and last patch versions come from releases-index.json and the per-version releases.json files of Microsoft's .NET release metadata, read on 22 November 2026. .NET Framework dates come from the Microsoft Lifecycle page for .NET Framework, the .NET Framework support policy page and the lifecycle FAQ. All sources were checked on 22 November 2026.
Calculations. "Days" is the end date minus the start date. The lifecycle pages give .NET Framework end times as 6:59:59 a.m. Pacific Time on the following day; we use the calendar date that Microsoft's support policy and FAQ pages give (for example 12 January 2027 for 4.6.2, 26 April 2022 for 4.5.2 to 4.6.1). Versions that follow the Windows lifecycle have no end date in the CSV. We did not add any date that Microsoft does not publish.
Licence. Our tables, chart and CSV file are free to reuse with a link to this page. The underlying dates are Microsoft's; check the lifecycle pages before making a decision, as they can change. Published 22 November 2026 by Postback Notes.