.NET Framework 4.6.2 End of Support (EOL): January 12, 2027
.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.
Key Dates at a Glance
- .NET Framework 4.6.2: start date 2016-08-02; end of support 2027-01-12
- .NET Framework 3.5 SP1: end of support 2029-01-09
- .NET Framework 4.8.1: start date 2022-08-09; no end date on Microsoft's lifecycle page
- .NET Framework 4.8: start date 2019-04-18; no end date on Microsoft's lifecycle page
- .NET Framework 4.7.2: start date 2018-04-30; no end date on Microsoft's lifecycle page
- .NET Framework 4.7.1: start date 2017-10-17; no end date on Microsoft's lifecycle page
- .NET Framework 4.7: no end date on Microsoft's lifecycle page
- .NET Framework 4.6.1: support ended 2022-04-26
- .NET Framework 4.6: support ended 2022-04-26
- .NET Framework 4.5.2: support ended 2022-04-26
- .NET Framework 4.5.1: support ended 2016-01-12
- .NET Framework 4.5: support ended 2016-01-12
- .NET Framework 4.0: support ended 2016-01-12
- Windows Server 2016: Extended Support ends 2027-01-12
.NET Framework versions and their end dates
| Version | End date on Microsoft's lifecycle page | Support phase on Microsoft's .NET policy page | What Microsoft's lifecycle FAQ says |
|---|---|---|---|
| .NET Framework 4.8.1 | No end date listed | Active | Follows the lifecycle policy of the parent operating system |
| .NET Framework 4.8 | No end date listed | Active | Follows the lifecycle policy of the parent operating system. Microsoft recommends upgrading to this version. |
| .NET Framework 4.7.2 | No end date listed | Active | Follows the lifecycle policy of the parent operating system |
| .NET Framework 4.7.1 | No end date listed | Active | Follows the lifecycle policy of the parent operating system |
| .NET Framework 4.7 | No end date listed | Active | Follows the lifecycle policy of the parent operating system |
| .NET Framework 4.6.2 | January 12, 2027 | Active | Follows the lifecycle policy of the parent operating system. The FAQ entry prints no date. The lifecycle page does. |
| .NET Framework 3.5 SP1 | January 9, 2029 | Active | A 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.1 | April 26, 2022 | Inactive | Retired. It was signed with SHA-1 certificates. |
| .NET Framework 4.6 | April 26, 2022 | Inactive | Retired. It was signed with SHA-1 certificates. |
| .NET Framework 4.5.2 | April 26, 2022 | Inactive | Retired. It was signed with SHA-1 certificates. |
| .NET Framework 4.5.1 | January 12, 2016 | Inactive | Support ended on all operating systems |
| .NET Framework 4.5 | January 12, 2016 | Inactive | Support ended on all operating systems |
| .NET Framework 4 | January 12, 2016 | Inactive | Support 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.
- The lifecycle page. The Releases table lists .NET Framework 4.6.2 with a start date of August 2, 2016 and an End Date of January 12, 2027. It is the only 4.x version from 4.6.2 upward with an End Date on the page.
- The Ending Support in 2027 list. Microsoft's Ending Support in 2027 list names .NET Framework 4.6.2 under January 12, 2027, in the same row as Windows Server 2016. The list says that upon end of support there will be no new security updates, no non-security updates, no free or paid assisted support options and no online technical content updates.
- The .NET Framework support policy page. It lists 4.6.2 with the support phase Active and the same end of support day.
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.
- 4.5.2 and later are components of Windows. The FAQ says that beginning with version 4.5.2, .NET Framework is defined as a component of the Windows operating system. It says components receive the same support as their parent products, so .NET Framework 4.5.2 and later follows the lifecycle policy of the underlying Windows version on which it is installed.
- When Windows ends, the component ends. Microsoft's Fixed Lifecycle Policy FAQ says that when a parent product reaches the end of support, so does the component. Its example is a component licensed for Windows: support for the component ends on the same date that support ends for Windows.
- Each version from 4.6.2 to 4.8.1 has the same sentence. The FAQ has an entry for 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 and 4.8.1. Each one says support for that version follows the Lifecycle Policy of the parent operating system. Each entry lists the Windows versions the release is supported on.
- 4.6.2 also has a fixed End Date. The FAQ entry for 4.6.2 prints no date. The lifecycle page, the Ending Support in 2027 list and the support policy page all print January 12, 2027.
- 4.8.1 is the latest version. Microsoft's support policy page says .NET Framework 4.8.1 is the latest version of .NET Framework and will continue to be distributed with future releases of Windows. It says that as long as 4.8.1 is installed on a supported version of Windows, it will continue to be supported.
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.
- The recommendation. The FAQ entry for .NET Framework 4.8 says Microsoft recommends customers upgrade to .NET Framework 4.8 to receive the highest level of performance, reliability and security.
- In-place update. Microsoft's install guide says all .NET Framework versions since .NET Framework 4 are in-place updates, so only a single 4.x version can be present on a system. It says you do not have to uninstall the previous version first. It also says that once a later 4.x version is installed, an earlier 4.x version cannot be installed on that machine.
- Same runtime, updated assemblies. Microsoft's versions page says .NET Framework 4.6.2, 4.7, 4.7.1, 4.7.2 and 4.8 are in-place updates to .NET Framework 4.5. It says in-place update means they use the same runtime version, with updated assembly versions that include new types and members.
- No recompiling required. The versions page says 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. It says the reverse is not true: Microsoft does not recommend running an app that targets a later version on an earlier version.
- A small number of breaking changes. The FAQ says a very small number of changes in .NET Framework 4.6.2 and later versions are not fully compatible with earlier versions. It says other fixes, called retargeting changes, apply only if you recompile the application against the newer version.
- Test first. The FAQ recommends that customers validate their deployments by updating the runtime in a pre-production environment before rolling out a newer version in production.
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 default | Later versions Microsoft lists as installable |
|---|---|---|
| Windows Server 2016 | 4.6.2 | 4.7, 4.7.1, 4.7.2 and 4.8 |
| Windows Server 2019 | 4.7.2 | 4.8 |
| Windows Server 2022 | 4.8 | 4.8.1 |
| Windows Server 2025 | 4.8.1 | None 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 version | Minimum Release value in Microsoft's table |
|---|---|
| .NET Framework 4.6.2 | 394802 |
| .NET Framework 4.7 | 460798 |
| .NET Framework 4.7.1 | 461308 |
| .NET Framework 4.7.2 | 461808 |
| .NET Framework 4.8 | 528040 |
| .NET Framework 4.8.1 | 533320 |
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.
- Standalone product on newer Windows. A note on the lifecycle page says .NET Framework 3.5 SP1 is a standalone product following the Fixed Policy, beginning with Windows 10 version 1809 and Windows Server 2019. The FAQ says that as a product it receives 5 years of mainstream support followed by 5 years of extended support, and that future Windows releases will not affect its lifecycle.
- Component on older Windows. The same note says that before those releases, 3.5 SP1 is considered a component of the Windows operating system on which it is installed. The FAQ says it assumes the same lifecycle policy as that operating system.
- The 2.0 and 3.0 layers. The FAQ says that where .NET Framework 3.5 relies on 2.0 or 3.0 to operate, Microsoft supports the .NET Framework 2.0 SP2 and 3.0 SP2 components for customers who install 3.5 SP1, for as long as 3.5 SP1 remains in support.
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
- 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.
- 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.
- 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.
- 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.
- 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.
- 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
- .NET Framework: live status and EOL Risk Score for every version
- .NET end of life dates: modern .NET, with a section on .NET Framework
- Microsoft products ending support in January 2027: the other products with the same end date
- Windows Server 2016 end of life: the same end date as .NET Framework 4.6.2
- Windows Server 2016 ESU: what Microsoft has published about the program
- Windows Server end of life dates: every version
- EOL Checker and How we verify our dates