endoflife.ai
.NET Framework .NET Framework 4.6.2 .NET Framework 4.8 EOL Checker

.NET Framework 4.6.2 End of Support (EOL): January 12, 2027

By Scott Bissett  ·  Published: November 22, 2026  ·  Reference guide  ·  Dates and wording read on the day of publication from Microsoft's lifecycle page for .NET Framework, its .NET Framework lifecycle FAQ, its .NET Framework support policy page, its Ending Support lists and its .NET Framework install documentation.

.NET Framework 4.6.2 reaches end of support on January 12, 2027: Microsoft's lifecycle page for .NET Framework gives that day as the End Date for version 4.6.2. The same page lists no end date for .NET Framework 4.7, 4.7.1, 4.7.2, 4.8 or 4.8.1. Microsoft's lifecycle FAQ says each of those versions follows the lifecycle policy of the Windows version it is installed on. The FAQ recommends .NET Framework 4.8, and Microsoft's install guide says every 4.x version is an in-place update. .NET Framework 3.5 Service Pack 1 has its own End Date, January 9, 2029.

On Windows Server 2016, two things end on the same day. Microsoft's versions page shows .NET Framework 4.6.2 as the version installed by default on Windows Server 2016. Windows Server 2016 reaches the end of Extended Support on January 12, 2027. Installing .NET Framework 4.8 moves a server off the 4.6.2 End Date. Microsoft's FAQ then says support for 4.8 follows the lifecycle policy of the parent operating system. A Windows Server 2016 host needs a plan for the operating system as well as the framework. Details are in the Windows Server section below.
Quick answer: The .NET Framework 4.6.2 end-of-life (EOL) date is January 12, 2027. Every .NET Framework version's release and end-of-support date is on the .NET Framework lifecycle page. Running a .NET Framework version that is past end of life? See the support options on this page ↓

Key Dates at a Glance

Running .NET Framework past end of life?
Extended support past the official EOL date exists for many products in this position — whether it covers .NET Framework is exactly what we check. Tell us where to reach you and we’ll reply with matched options and pricing guidance — or an honest “no vendor covers this.” Free, no obligation.

Free · No obligation · Independent — we track the dates, vendors don’t pay for placement · dates verified against vendor sources. See all support options →
If you choose a provider we introduce, we may receive a referral fee from that provider. It never changes a date or a score.

.NET Framework versions and their end dates

VersionEnd date on Microsoft's lifecycle pageSupport phase on Microsoft's .NET policy pageWhat Microsoft's lifecycle FAQ says
.NET Framework 4.8.1No end date listedActiveFollows the lifecycle policy of the parent operating system
.NET Framework 4.8No end date listedActiveFollows the lifecycle policy of the parent operating system. Microsoft recommends upgrading to this version.
.NET Framework 4.7.2No end date listedActiveFollows the lifecycle policy of the parent operating system
.NET Framework 4.7.1No end date listedActiveFollows the lifecycle policy of the parent operating system
.NET Framework 4.7No end date listedActiveFollows the lifecycle policy of the parent operating system
.NET Framework 4.6.2January 12, 2027ActiveFollows the lifecycle policy of the parent operating system. The FAQ entry prints no date. The lifecycle page does.
.NET Framework 3.5 SP1January 9, 2029ActiveA standalone product beginning with Windows 10 version 1809 and Windows Server 2019. A component of the operating system on earlier Windows versions.
.NET Framework 4.6.1April 26, 2022InactiveRetired. It was signed with SHA-1 certificates.
.NET Framework 4.6April 26, 2022InactiveRetired. It was signed with SHA-1 certificates.
.NET Framework 4.5.2April 26, 2022InactiveRetired. It was signed with SHA-1 certificates.
.NET Framework 4.5.1January 12, 2016InactiveSupport ended on all operating systems
.NET Framework 4.5January 12, 2016InactiveSupport ended on all operating systems
.NET Framework 4January 12, 2016InactiveSupport ended

The end dates are from the Releases table on Microsoft's .NET Framework lifecycle page. That page shows dates in Pacific time, and the day here is the last supported day. The support phases are from Microsoft's .NET Framework support policy page, which prints the same end dates for 4.6.2 and 3.5 SP1. The last column is from Microsoft's lifecycle FAQ for .NET Framework. Live status for every version is on our .NET Framework page.

What ends on the end date

Three Microsoft pages give the same day for .NET Framework 4.6.2.

Microsoft's policy page also shows what the end of support meant for the versions before 4.6.2. It says support for .NET Framework 4.5.2, 4.6 and 4.6.1 ended on April 26, 2022, so security fixes, updates and technical support for those versions are no longer provided. It told customers to update the deployed runtime to a more recent version.

Nothing on Microsoft's pages says an application stops running on the end date. What ends is the supply of updates and assisted support for that version of the runtime.

Extended Security Updates. The .NET Framework lifecycle page lists no Extended Security Update rows for 4.6.2. Microsoft's Windows Server 2016 lifecycle page and its lifecycle FAQ on Extended Security Updates do not mention .NET Framework. If your plan depends on Extended Security Updates covering a 4.6.2 application, ask Microsoft or your licensing provider and get the answer in writing.

How Microsoft's lifecycle works for .NET Framework 4.x

Microsoft's lifecycle page says .NET Framework follows the Component Lifecycle Policy. Its lifecycle FAQ for .NET Framework explains what that means.

The practical reading is in two parts. A version with no End Date on Microsoft's page is supported for as long as the Windows version under it is supported. A version with an End Date, such as 4.6.2, ends on that day at the latest.

The move Microsoft names: .NET Framework 4.8 or 4.8.1

Microsoft's pages point 4.6.2 users to a later 4.x version. They describe the move as an update to the installed runtime, not a rewrite of the application.

An in-place update replaces the 4.x runtime for every 4.x application on the machine at once. That is why Microsoft's advice to test first matters on a server that hosts several applications.

Which version each Windows Server release can take

Microsoft's versions page marks, for each .NET Framework version, the Windows releases where it is installed by default and the ones where it can be installed.

Windows Server release.NET Framework 4.x installed by defaultLater versions Microsoft lists as installable
Windows Server 20164.6.24.7, 4.7.1, 4.7.2 and 4.8
Windows Server 20194.7.24.8
Windows Server 20224.84.8.1
Windows Server 20254.8.1None later. 4.8.1 is the latest version.

The versions page does not list Windows Server 2016 or Windows Server 2019 for .NET Framework 4.8.1. The FAQ's list for 4.8.1 names Windows Server 2022 and Windows Server 2025. On Windows Server 2016 and Windows Server 2019, the highest version Microsoft lists is 4.8.

The Windows version still sets the limit. Windows Server 2016 reaches the end of Extended Support on January 12, 2027, the same day as the 4.6.2 End Date. Under Microsoft's component rule, .NET Framework 4.8 on that server follows Windows Server 2016. Our Windows Server 2016 end of life guide and Windows Server 2016 ESU guide cover what Microsoft has published for the operating system. Our Windows Server end of life guide lists the dates for every release.

The FAQ and the versions page also list Windows client releases for each version. Check the page for your Windows 10 or Windows 11 release before you choose 4.8 or 4.8.1 on a desktop.

How to check which version is installed

Microsoft's page on determining which .NET Framework versions are installed uses one registry value. Open the subkey HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full and read the Release REG_DWORD value. Microsoft says to check for a value greater than or equal to the minimum in its table.

.NET Framework versionMinimum Release value in Microsoft's table
.NET Framework 4.6.2394802
.NET Framework 4.7460798
.NET Framework 4.7.1461308
.NET Framework 4.7.2461808
.NET Framework 4.8528040
.NET Framework 4.8.1533320

A machine whose Release value is at least 394802 and below 460798 has .NET Framework 4.6.2. A value of 528040 or higher means 4.8 or later. Microsoft's page says that if the Full subkey is missing, .NET Framework 4.5 or later is not installed.

The installed runtime and the version an application targets are different things. An application built for 4.6.2 runs on the 4.x runtime installed on the machine, which can be a later version. The end date applies to the installed runtime, so the registry value is the one to check.

.NET Framework 3.5 SP1 has a separate date

Microsoft's lifecycle page lists .NET Framework 3.5 Service Pack 1 with an End Date of January 9, 2029. Microsoft's Ending Support in 2029 list names it under the same day.

Microsoft's versions page describes .NET Framework 2.0, 3.0 and 3.5 as layers of one installation, and .NET Framework 4 and later releases as layers of another. Moving a 4.6.2 application to 4.8 does not change the 3.5 SP1 date, and the 3.5 SP1 date does not apply to 4.x.

What a .NET Framework 4.6.2 owner should plan

  1. Find every machine on 4.6.2. Read the Release value on each server and desktop. Windows Server 2016 installs 4.6.2 by default, so start there.
  2. Choose the target for each Windows version. Microsoft lists 4.8 for Windows Server 2016 and Windows Server 2019, and 4.8.1 for Windows Server 2022 and Windows Server 2025.
  3. Test before you roll out. The update replaces the 4.x runtime for every application on the machine. Microsoft recommends validating in a pre-production environment first.
  4. Finish before January 12, 2027. After that day Microsoft's list says there are no new security updates and no assisted support for 4.6.2.
  5. Plan the Windows version too. A later 4.x version follows the Windows version under it. On Windows Server 2016 that means the operating system needs its own plan for the same day.
  6. List any 3.5 SP1 applications separately. They have their own End Date, January 9, 2029, on Windows 10 version 1809, Windows Server 2019 and later.

.NET Framework is a separate product from modern .NET. Our .NET end of life guide covers .NET 8, .NET 9 and .NET 10, which have their own support policy. The EOL Checker looks up one product and version. Our .NET Framework page carries the live status and EOL Risk Score for each version.

Frequently Asked Questions

When does .NET Framework 4.6.2 reach end of support?

January 12, 2027. Microsoft's lifecycle page for .NET Framework gives that day as the End Date for version 4.6.2. Microsoft's list of products ending support in 2027 names .NET Framework 4.6.2 under the same day. The list says that upon end of support there will be no new security updates, non-security updates, free or paid assisted support options or online technical content updates.

Is .NET Framework 4.6.2 still supported?

Yes, until January 12, 2027. Microsoft's .NET Framework support policy page lists version 4.6.2 with the support phase Active and that day as its end of support. Microsoft's lifecycle FAQ says support for 4.6.2 follows the lifecycle policy of the parent operating system, so it also depends on the Windows version being supported.

Is .NET Framework 4.8 still supported?

Yes, on a supported version of Windows. Microsoft's lifecycle page lists no end date for .NET Framework 4.8. Microsoft's lifecycle FAQ says support for 4.8 follows the lifecycle policy of the parent operating system, and it recommends that customers upgrade to .NET Framework 4.8. Microsoft's .NET Framework support policy page lists 4.8 with the support phase Active and no end of support date.

Is .NET Framework 4.8.1 still supported?

Yes, on a supported version of Windows. Microsoft's .NET Framework support policy page says 4.8.1 is the latest version of .NET Framework and that it will continue to be supported as long as it is installed on a supported version of Windows. Microsoft's lifecycle page lists no end date for it.

Are .NET Framework 4.7, 4.7.1 and 4.7.2 still supported?

Yes, on a supported version of Windows. Microsoft's lifecycle page lists no end date for .NET Framework 4.7, 4.7.1 or 4.7.2. Microsoft's lifecycle FAQ says support for each of them follows the lifecycle policy of the parent operating system. Microsoft's .NET Framework support policy page lists all three with the support phase Active.

Do applications need to be recompiled to move from .NET Framework 4.6.2 to 4.8?

Microsoft says recompiling is not required. Its versions page says .NET Framework 4.6.2 through 4.8 are in-place updates to .NET Framework 4.5, and that after one of these updates is installed, .NET Framework 4, 4.5, 4.6 and 4.7 apps should continue to run without requiring recompilation. Microsoft's lifecycle FAQ adds that a very small number of changes in 4.6.2 and later versions are not fully compatible with earlier versions, and it recommends validating in a pre-production environment before rolling out a newer runtime in production.

Can .NET Framework 4.8.1 be installed on Windows Server 2016 or Windows Server 2019?

Microsoft's pages do not list either one for 4.8.1. Microsoft's versions page shows .NET Framework 4.8.1 installed by default on Windows Server 2025 and installable on Windows Server 2022. Microsoft's lifecycle FAQ lists Windows Server 2022 and Windows Server 2025 for 4.8.1. Both pages list Windows Server 2016 and Windows Server 2019 for .NET Framework 4.8.

Do Extended Security Updates for Windows Server 2016 cover .NET Framework 4.6.2?

Microsoft's pages do not say. The .NET Framework lifecycle page lists a start date and an End Date for 4.6.2 and no Extended Security Update rows. Microsoft's Windows Server 2016 lifecycle page and its lifecycle FAQ on Extended Security Updates do not mention .NET Framework. Ask Microsoft or your licensing provider in writing before you plan on Extended Security Updates for a 4.6.2 application. Microsoft's own recommendation in its .NET Framework FAQ is to upgrade to .NET Framework 4.8.

When does .NET Framework 3.5 SP1 reach end of support?

January 9, 2029. Microsoft's lifecycle page gives that day as the End Date for .NET Framework 3.5 Service Pack 1. A note on the page says 3.5 SP1 is a standalone product following the Fixed Policy, beginning with Windows 10 version 1809 and Windows Server 2019. Before those releases, the note says, it is considered a component of the Windows operating system on which it is installed.

Is .NET Framework 3.5 SP1 still supported?

Yes. On Windows 10 version 1809, Windows Server 2019 and later releases it is a standalone product with an End Date of January 9, 2029. On earlier Windows versions, Microsoft's lifecycle FAQ says .NET Framework 3.5 SP1 assumes the same lifecycle policy as the operating system it is installed on, so its support depends on that Windows version.

Is .NET Framework the same product as .NET 8 or .NET 10?

No. .NET Framework is the Windows framework whose latest version is 4.8.1. Modern .NET, which began as .NET Core, is a separate product with its own support policy and its own end dates. The .NET Framework 4.6.2 end date does not apply to modern .NET, and modern .NET end dates do not apply to .NET Framework.

Related

© 2026 endoflife.ai · How we verify our dates · API · About