WIN10 installing the. NET Framework 4.0 failure prompt is already part of the operating system how to resolve

There is a user who wants to install the Microsoft. NET Framework 4.0 on the WIN10 system computer because of job requirements. However, during the installation process failed, but also encountered the prompt "Microsoft.NET Framework 4 is already part of this operating system." You do not need to install the. NET Framework 4 Redistributable package. The same or later version of the. NET Framework 4 "is installed on this computer. What should we do about it? The following small series to share with you the specific solution.

The reason is that the WIN10 system is already integrated by default. NET Framework 4.6 is theoretically backwards compatible, so we don't need to install the. NET Framework 4.0, even if the installation is not complete.
If you have a. NET Framework 4.0 that is required to run some software, you can try to uncheck the. NET Framework 4.6 After you check the "Enable or disable Windows features" in the WIN10 system.

Or you can trick your software by modifying the registry. NET Framework version number.

Steps:

Microsoft logo key Win+r Enter regedit to open the registry.

Find Location HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework setup\ndp\v4\client

The full version number of the net Framework 4.0 you need is 4.0.30319.1.

You can try to change this value to the desired version number. Note Permissions are required to modify the registry.

The WIN10 installation of the. NET Framework 4.0 failure hint is already part of the operating system workaround. In the process of installing the. NET Framework 4.0, WIN10 users who encounter the same problem may wish to use the above method to solve it!

Related recommendations:

Quick offline installation of the. NET framework techniques under the WIN10 system "graphics"
WIN10 system installation. NET 3.5 failure hint Error 0x80070003 workaround

article turned from:http://www.xitongcheng.com/jiaocheng/win10_article_13715.html

WIN10 installing the. NET Framework 4.0 failure prompt is already part of the operating system how to resolve