- .NET Framework 4.x is updated in-place, and only one 4.x version can exist per computer.
- To apps older versions require .NET Framework 3.5, which can be enabled as a feature.
- Windows 11 (22H2+) includes 4.8.1; Windows 10 22H2 supports installing 4.8.1.
- Web/offline installers, language packs, and developer packs as needed.

If you've ever seen a prompt asking for the .NET Framework when opening a program, you're not alone: Many applications in Windows depend on this componentIn this guide, you'll find, all in one place, the versions of Windows that come with each version, how to update to the latest version, how to activate the .NET Framework 3.5 when an older app asks for it, and how to deal with common errors during installation.
Before we get into the nitty-gritty, it's worth getting our bearings: The most current version of the .NET Framework is 4.8.1, compatible with all applications built for the .NET Framework 4.x. However, if an app was developed for .NET 1.1 to 3.5, it will require the .NET Framework 3.5 component. That's why you'll sometimes see a window asking you to download this feature; this is normal, and except in strict corporate environments, simply accepting is usually sufficient.
Supported versions of the .NET Framework
In the Windows ecosystem there are two large families: on the one hand, . NET Framework 3.5 (intended to run old software) and, on the other hand, the 4.x line (4.0 through 4.8.1). Microsoft continues to support the .NET Framework 3.5 for running applications, but does not recommend creating new projects with that version. If an app targets 1.0–3.5 and the system doesn't have 3.5, Windows will prompt you to install it automatically.
The 4.x branch works as an in-place upgrade: Only one version 4.x can coexist on the same computer.If you try to install an older 4.x version and you already have a newer one, it won't let you. Similarly, if the system already comes with a certain 4.x version, it's not possible to downgrade to an older version, although you can upgrade to a newer version without uninstalling anything.
For developers, Visual Studio uses specific development packages (Developer Pack/Targeting Pack) to be able to target the project to specific versions of the .NET Framework 4.xIf you're maintaining legacy software, install the corresponding package so the IDE can compile against that version.
If you're not sure what you have, you can check from Windows: There are methods to view the installed versions of the .NET Framework.This way, you can avoid reinstalling something that's already there or trying to figure out why an installer refuses to continue.

Windows 11
Windows 11 initially came with the .NET Framework 4.8, but since version 22H2 (September 2022) includes .NET Framework 4.8.1 as standard. Thus, most current devices already have the latest version preinstalled. The following table provides a quick overview:
| Windows 11 (version) | .NET included | Latest .NET support |
|---|---|---|
| 24H2 (October 2024) | 4.8.1 | 4.8.1 |
| 23H2 (October 2023) | 4.8.1 | 4.8.1 |
| 22H2 (September 2022) | 4.8.1 | 4.8.1 |
| 21H2 (October 2021) | 4.8 | 4.8.1 |
If your computer is running Windows 11 21H2You can manually install 4.8.1 by downloading the installer. For all other editions of Windows 11, the modern version is already installed. If an older app asks for .NET 3.5, see how to enable it on demand below.

Installing the .NET Framework on Windows 11
In 21H2, download the .NET Framework 4.8.1 installer and run it with administrator permissions; you don't need to uninstall anything beforehandFor the .NET Framework 3.5 (running apps from 1.0 to 3.5), use Windows Features or install on demand when prompted.
Windows 10
Windows 10 originally included the .NET Framework 4.6, although newer versions were added over time. The latest supported version of Windows 10 is 22H2, whose useful life ends on October 14, 2025. Below is a summary of relevant versions:
| Windows 10 (version) | .NET included | Latest .NET support |
|---|---|---|
| 22H2 (October 2022) | 4.8 | 4.8.1 |
| 21H2 / 21H1 / 20H2 | 4.8 | 4.8.1 |
| 2004 / 1909 / 1903 | 4.8 | 4.8 |
| 1809 / 1803 | 4.7.2 | 4.8 |
| 1709 | 4.7.1 | 4.8 |
| 1703 | 4.7 | 4.8 |
| 1607 | 4.6.2 | 4.8 |
| 1511 | 4.6.1 | 4.6.2 |
| 1507 | 4.6 | 4.6.2 |
For 22H2 you can install 4.8.1 without any problem, while for previous series the maximum version may varyIf you need the .NET Framework 3.5, remember that it is only used to run older software (1.0 to 3.5) and is enabled as a system feature.

Installing the .NET Framework on Windows 10
Download the .NET Framework 4.8.1 installer for Windows 10 22H2 and run it with an administrative account. For .NET 3.5, use the “Turn Windows features on or off” panel or On-Demand mode when the app prompts you.
Windows Server
All Windows Servers come with some version of the .NET Framework, although not all are still supported. Currently, Windows Server 2022 and Windows Server 2025 are in support and support the latest version (4.8.1). Details by edition:
| Windows Server | .NET included | Latest .NET support |
|---|---|---|
| Windows Server 2025 | 4.8.1 | 4.8.1 |
| Windows Server 2022 | 4.8 | 4.8.1 |
| Windows Server 2019 | 4.7.2 | 4.8 |
| Windows Server 2016 | 4.6.2 | 4.8 |
| Windows Server 2012 / 2012 R2 | 4.5 / 4.5.1 | 4.8 |
| Windows Server 2008 R2 SP1 | 3.5 | 4.8 |
| Windows Server 2008 SP2 | 2.0 | 4.6 |
| Windows Server 2003 | 2.0 | 4.0 |
Server 2025 already comes with 4.8.1 installed. Server 2022 comes with 4.8.1 installed. You can upgrade to 4.8.1 with the installerTo run older apps, the .NET Framework 3.5 is enabled as a feature (see next block).

Install .NET Framework 3.5 on Windows Server
Open Server Manager and choose "Add Roles and Features." Navigate to "Features" and locate ".NET Framework 3.5 Features." Inside, select ".NET Framework 3.5 (includes .NET 2.0 and 3.0)." Click Install and, if prompted by the wizard, restart the server.This process is recommended when an installer tells you it can't add the feature by other means.
Windows 8.1, 8, 7, Vista and XP
These versions are no longer supported, but you may need to know what they came with and how far you can go. Historic information most relevant:
| Windows | .NET included | Latest .NET support |
|---|---|---|
| Windows 8.1 | 4.5.1 | 4.8 |
| Windows 8 | 4.5 | 4.6.1 |
| Windows 7 | 3.5 | 4.8 |
| Windows Vista | 3.0 | 4.6 |
| Windows XP SP3 | None | 4.0.3 |
| Windows XP SP2 | None | 3.5 |
| Windows XP | None | 1.0 |
Keep in mind that some downloads are no longer available and certain installers may not run on these systems. For example, the latest version of the 4.8 installer may not work on 8.1.In those cases, you may need to look for older binaries that Microsoft no longer distributes.
.NET Framework 3.5: When and How to Enable It
If you see a window asking you to “Download and install this feature” when you open an app, it means that the app is targeting .NET 1.1–3.5. Choose Continue to activate .NET Framework 3.5; you'll need an internet connection. On Windows, .NET 4.x won't run older apps on its own: for those, 3.5 is essential.
To manually enable it on Windows (client editions), go to the Start menu, search for "Windows Features," and open "Turn Windows features on or off." Select ".NET Framework 3.5 (includes .NET 2.0 and 3.0)" and click OK. You do not need to check the WCF activation options (HTTP or non-HTTP) unless you are a developer or admin who requires them.
Offline installation of .NET Framework 3.5
In versions prior to Windows 10 and Windows Server 2016, the .NET 3.5 SP1 offline installer is available. Starting with Windows 10/Server 2016, the only supported path to an offline environment is to use the CAB files from the original media and enable it with DISM. This is the recommended route when there is no Internet or download errors occur.. Consult the guide for install updates offline.
Types of installers and key notes
For .NET Framework 4.5 and later, there are two installer modes: web (download what you need in real time) y offline (includes all components)The first is lightweight but requires a stable connection; the second is heavier, doesn't include language packs, and is ideal for devices without or with limited internet access.
Both installers support x86 and x64 architectures, but They are not compatible with ItaniumDuring the download, select the language of the page (this affects the web text, not the framework resources), click "Download," and if prompted, grab the binary appropriate for your architecture. You can then "Run" to install it, or "Save" if you're redistributing it with your own installer.
Important notes: Installing .NET 4.5 or later replaces .NET 4.0Uninstalling 4.5+ also deletes the 4.0 files, and if you need to go back, you'll need to reinstall .NET 4.0 and its updates. Additionally, installing 4.5 or higher requires administrator credentials.
A historical note: The .NET 4.5 redistributable was updated in October 2012 to address an issue with a certificate timestamp. If you were using the August 2012 package, you should update to the latest one.This incident was documented in a Microsoft security advisory.
Language packs
Language packs add localized resources (interface text and error messages). If you don't install them, .NET Framework texts will appear in EnglishThe web installer automatically adds the language appropriate for your system; the offline installer doesn't include languages, and you'll need to download them separately.
Available languages and their associated culture (availability subject to each version): you can install more than one if you need it.
| Language | Culture |
|---|---|
| Arab | Ar |
| Czech | Cs |
| Danish | yes |
| Dutch | Nl |
| Finnish | Fi |
| English (US) | it-IT |
| French | France |
| German | de |
| Greek | El |
| Hebrew | he |
| Hungarian | hu |
| Italian | That |
| Japanese | ja |
| Korean | ko |
| Norwegian | No |
| Polish | pl |
| Portuguese (Brazil) | pt-BR |
| Portuguese (Portugal) | pt-PT |
| Russian | Ru |
| Simplified Chinese | zh-CHS |
| Spanish | es |
| Swedish | Sv |
| Traditional Chinese | zh-CHT |
| Turkish | Tr |
Downloads by version (.NET Framework 4.5 to 4.8.1)
If you need a specific package, here's a summary of where it's packaged and what platforms it can be installed on. For development, download the Developer Pack/Targeting Pack; To run applications, use the redistributable installer (web or offline):
| Version | Included in | Can be installed on (examples) |
|---|---|---|
| 4.8.1 | Windows 11 (22H2+), Visual Studio 2022 (17.3) | Windows 11; Windows 10 (21H1/21H2/20H2); Windows Server 2022 |
| 4.8 | Windows 11; Windows 10 May 2019 Update+; VS 2019 (16.3) | Windows 10 (Anniversary/Creators/Fall Creators/April 2018/October 2018); Windows 8.1; Server 2022/2019/1809/1803 |
| 4.7.2 | Windows 10 October/April 2018; Server 2019; VS 2017 (15.8) | Windows 10 (Anniversary/Creators/Fall Creators); Windows 8.1; Server 1709 and earlier |
| 4.7.1 | Windows 10 Fall Creators; Server 1709; VS 2017 (15.5) | Windows 10 (Creators/Anniversary); Windows 8.1; Server 2016 and earlier |
| 4.7 | Windows 10 Creators; VS 2017 (15.3) | Windows 10 Anniversary; Windows 8.1; Server 2016 and earlier |
| 4.6.2 | Windows 10 Anniversary | Windows 10 November Update; Windows 8.1; Server 2012 R2 and earlier |
| 4.6.1 | VS 2015 Update 2 | Windows 10/8.1; Server 2012 R2 and earlier |
| 4.6 | Windows 10; VS 2015 | Windows 8.1; Server 2012 R2 and earlier |
| 4.5.2 | — | Windows 8.1 and earlier; Server 2012 R2 and earlier |
| 4.5.1 | Windows 8.1; Server 2012 R2; VS 2013 | Windows 8 and earlier; Server 2012 and earlier |
| 4.5 | Windows 8; Server 2012; VS 2012 | Windows 7 and earlier; Server 2008 SP2 and earlier |
Remember A Developer Pack does not include previous versions (For example, the 4.8 package doesn't include 4.7.) If you're distributing your app, you can include the appropriate redistributable in your installer.
Developers and Visual Studio
If you're maintaining older projects, install the Developer Pack/Targeting Pack for that specific version and activate it from the Visual Studio Installer under "Desktop Development with .NET." If MSBuild shows you error MSB3644 ("Reference assemblies not found"), the solution is to install the package for the version you are targeting.
For .NET Framework 3.5 in development, first enable 3.5 on the system and then marks the .NET Framework 3.5 development tools in the "Individual Components" tab of Visual Studio. This will give you reference assemblies, language packs, and IntelliSense.
Current Microsoft recommendation: For new developments, use .NET 8 or laterModern versions of .NET are cross-platform, support more types of applications, and offer much better performance, while still allowing you to maintain software that still requires the .NET Framework.
Installation Troubleshooting
During installation you may see error codes such as 0x800f0906, 0x800f0907, 0x800f081f o 0x800F0922. Review the .NET Framework 3.5 installation error guide when it affects that feature. These are often resolved by enabling the feature using the installation media and DISM, or by verifying connectivity to the installation servers. Windows Update. You can also use This tool to troubleshoot problems with the .NET Framework 4.5.
If you don't have internet access or are still stuck, mount your official Windows installation media (ISO/USB) and use DISM to add .NET Framework 3.5 from the \sources\sxs folder. If you don't have the means, create one with the official Microsoft toolIn environments with Features on Demand, ensure that content sources are configured correctly.
With all of the above, you should be clear about which .NET Framework you need, how to activate it, and where to download it depending on your version of Windows or Windows Server. Remember: 3.5 for old apps, 4.8.1 as the latest branch, and Developer Packs for compiling.If something goes wrong, run DISM from the installation media and check for error codes to resolve the problem as quickly as possible.
Passionate writer about the world of bytes and technology in general. I love sharing my knowledge through writing, and that's what I'll do on this blog, show you all the most interesting things about gadgets, software, hardware, tech trends, and more. My goal is to help you navigate the digital world in a simple and entertaining way.