---
title: '.NET Framework 4.6.2 end of life: which versions end and which do not'
description: '.NET Framework 4.6.2 support ends on 2027-01-12, while 4.7–4.8.1 follow Windows. Check your runtime and when an in-place update is enough.'
url: 'https://dfuture.co/insights/dotnet-framework-end-of-life-versions/'
type: 'article'
typeLabel: 'Article'
language: 'en'
date: '2026-11-18'
categories: 'legacy-modernization'
---

# .NET Framework 4.6.2 end of life: which versions end and which do not

> .NET Framework 4.6.2 support ends on 2027-01-12, while 4.7–4.8.1 follow Windows. Check your runtime and when an in-place update is enough.

The .NET Framework 4.6.2 end of life date is 2027-01-12. Versions 4.7, 4.7.1, 4.7.2 and 4.8 have no fixed end date and are supported as long as the Windows version they run on is supported; 4.8.1 is supported while installed on a supported Windows version. For an application built for 4.6.2, the first question is which runtime is installed and whether an in-place update to 4.8 or 4.8.1 removes the end of support before any code work is discussed.

Dates were checked against Microsoft's pages on 2026-11-17.

## .NET Framework versions and their support dates

The table combines Microsoft's .NET Framework support policy and the Microsoft Lifecycle entry for .NET Framework.

| Version | Status | End of support | Note |
|---|---|---|---|
| 4.8.1 | Supported | Follows Windows | Latest version |
| 4.8 | Supported | Follows Windows | |
| 4.7, 4.7.1, 4.7.2 | Supported | Follows Windows | |
| 4.6.2 | Supported until the end date | 2027-01-12 | The only supported 4.x version with a published end date |
| 4.5.2, 4.6, 4.6.1 | Ended | 2022-04-26 | Retired together; signed with SHA-1 certificates |
| 3.5 SP1 | Supported | 2029-01-09 | Separate product, see below |

The Lifecycle page displays the 4.6.2 end as "1/13/2027 6:59:59 AM", while the support policy page gives January 12, 2027. The calendar date to plan around is 2027-01-12.

.NET Framework 3.5 SP1 is a standalone product from Windows 10 version 1809 and Windows Server 2019, with five years of mainstream and five years of extended support; on earlier Windows versions it follows the operating system.

### Why most 4.x versions have no end date

Beginning with version 4.5.2, Microsoft defines .NET Framework as a component of the Windows operating system, and "components receive the same support as their parent products". A search for the .NET Framework 4.8 end of life therefore has no single date as an answer: the .NET Framework 4.8 end of support is the end of support of the Windows version where 4.8 is installed. Microsoft describes 4.8.1 as "the latest version of .NET Framework" that "will continue to be distributed with future releases of Windows".

## .NET Framework 4.8 is not .NET 8

The numbers look close, and search results for 4.8 mix the two. They are two product lines with two lifecycle models.

| | .NET Framework 4.8 and 4.8.1 | Modern .NET (.NET 8, .NET 10) |
|---|---|---|
| Where it runs | Windows, as a Windows component | Several operating systems |
| Support model | Follows the Windows version | Each release has its own end date: three years for LTS, two for STS |
| State on 2026-11-17 | 4.8.1 is the latest version | .NET 8 support ended on 2026-11-10; .NET 10 (LTS) is supported until 2028-11-14 |
| Moving within the line | In-place runtime update, in most cases without recompilation | New target platform for the project, then rebuild and retest |

Moving an application to modern .NET is one possible route, with its own scope and a fixed end date for the release it lands on. The end of 4.6.2 does not by itself require that move.

## Check what the application actually uses

The target framework records what the build was compiled against; the installed runtime executes it. Only one 4.x version is present on a machine, so an application built for 4.6.2 on a server with 4.8 runs on 4.8.

The check for one application takes five steps:

1. **Installed runtime.** On each server, read the `Release` value under `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full`. Microsoft's minimum values are 394802 for 4.6.2, 528040 for 4.8 and 533320 for 4.8.1.
2. **Target framework.** Find the target version in the project files and the application configuration file. It decides which retargeting changes apply if the application is recompiled.
3. **Windows version.** Compare each server's Windows version with Microsoft's system requirements to see whether 4.8, 4.8.1 or neither can be installed.
4. **Third-party components.** List each component, its version and the vendor's statement on 4.8 or 4.8.1. Each component runs on the same runtime as the application.
5. **Named workflows.** Name the business workflows that must keep working, the expected result of each and the person who accepts them.

## Update in place before planning code work

A request to upgrade .NET Framework 4.6.2 to 4.8 can mean two things: installing the 4.8 runtime on the server or retargeting the build to 4.8. The runtime update comes first, because it can remove the end of support without changing code.

Microsoft's lifecycle FAQ describes 4.6.2 and later as "compatible, in-place updates" on top of earlier 4.x versions, and the migration guide states that an application that does not have to be migrated can run on 4.6.2 or later without recompiling. When 4.5.2, 4.6 and 4.6.1 retired, Microsoft asked customers to complete the in-place update to 4.6.2 or later.

The route depends on Windows:

- **Windows Server 2016 and 2019** accept 4.8; Microsoft does not list 4.8.1 for them.
- **Windows Server 2022** comes with 4.8 and accepts 4.8.1.
- **Windows Server 2025** comes with 4.8.1.

The in-place update still leaves work to check:

- **Runtime changes.** Microsoft lists a small number of changes in 4.6.2 and later that are not fully compatible with earlier versions. They apply on the new runtime without recompilation; some can be switched back through `AppContextSwitchOverrides` in the configuration file.
- **Third-party components.** Each one now runs on the new runtime, whether or not its vendor has tested it there.
- **Named workflows.** Microsoft recommends validating the update in pre-production first. Compare each workflow's result before and after.
- **The way back.** Once a later 4.x version is installed, an earlier one cannot be installed on that machine. Plan how the server returns to its previous state.

A clean pre-production run does not prove that production will show no regressions.

### Work through an illustrative application

*Illustrative example: the application is synthetic and describes no client.*

An insurance carrier runs an internal claims reporting application built for .NET Framework 4.6.2, with one third-party reporting component. The completed check record:

| Check | Record |
|---|---|
| Installed runtime | 4.6.2 (`Release` 394802) on Windows Server 2016 |
| Target framework | 4.6.2 |
| Windows accepts | 4.8; 4.8.1 is not listed for this Windows version |
| Third-party component | One reporting component; no vendor statement on 4.8 yet |
| Named workflows | Monthly open-claims report; export of a report to PDF; overnight scheduled report run |
| Route | In-place update to 4.8 in pre-production, then compare the three workflows with their current output |

Open questions:

- Does the vendor support this component version on 4.8, or only a later version?
- Does pre-production match production in Windows version, runtime and component version?
- Who in the claims function accepts the report output?

Windows Server 2016 itself is a separate decision about the server and its environment.

## When a component blocks the update

If the reporting component fails on 4.8, the first options are a newer component version and a configuration switch that restores the previous behavior. When neither works, the option is a bounded code change: replacing the component or changing the code around it. Its boundary:

- **Scope.** One application, one component, the named workflows.
- **Before the change.** The current output of each workflow is recorded while the old behavior can still be observed.
- **Handed over.** The code change, build instructions that reproduce the build, regression evidence against the named workflows, known differences.
- **Acceptance.** The workflow owner accepts the result against the named workflows; a successful build is one check among several.
- **Outside the change.** Release to production, data migration, further applications and ongoing support.

When the route itself is unclear, for example when several components fail or nobody can build the application, a diagnosis of the application comes before any code change. Moving to modern .NET can appear among its options, decided on the evidence for that application.

## Record the version, the route and the open question

The completed record for one application:

- **Version.** Installed runtime per server and the target framework of the build.
- **Windows.** Each server's Windows version and the highest 4.x version it accepts.
- **Route.** In-place update to 4.8 or 4.8.1, a bounded code change around a named component, or an environment decision first.
- **Workflows.** The named workflows, their expected results and who accepts them.
- **Open question.** The one fact still missing, such as a vendor statement.

If one application is blocking a platform step, bring the component, version and workflow to discuss the next justified result.

[Discuss one application](https://dfuture.co/enterprise-application-modernization/)

---
HTML: https://dfuture.co/insights/dotnet-framework-end-of-life-versions/
Markdown: https://dfuture.co/insights/dotnet-framework-end-of-life-versions.md
