Installation of. NET Framework components fails after a computer restarts unexpectedly

Because the software runtime needs to install the. Net Framework, I install the 2.0SP version, you can install the computer unexpectedly shut down, re-open after the installation failed to install the prompt, the specific content is:

Product: Microsoft. NET Framework 2.0 SP2-Setup encountered an error while installing this package. This package may indicate an error. The error code is 2711. The parameters are: Servicing_key,,

After finding a solution on the internet, I have tried it, and solved it! Now record the settlement process (organized from the original part)

1. Log out of Windows Installer. To do this, click Start and Run, type Msiexec/unregister in the Open box, and then click OK.
2. Re-enroll Windows Installer. To do this, click Start and Run, type Msiexec/regserver in the Open box, and then click OK.
3. Click Start and run, type installer in the Open box, and then click OK.
4. In Windows Installer, on the View menu, click Details, right-click the Name column heading, and then click Notes.
Right-click the cached Windows Installer file that has the comment "Microsoft. NET Framework 2.0 RTL x86 enu", and then click Repair.
5. After the repair process is complete, the. Net framework is used normally, and running its own software is available.

The following is the solution found on the Internet, it may be cumbersome (because I think the word too much, but people say the details)

This article steps through how to troubleshoot issues that you may experience when you install the. NET Framework 2.0.

If Microsoft Windows Installer is registered incorrectly in the Windows registry, the. NET Framework 2.0 Setup program will not be able to access some Windows Installer components. This article discusses how to resolve this issue by logging off and then re-registering Windows Installer.

You may not always be able to completely remove the. NET Framework 2.0 by using the Add/Remove Programs tool in Control Panel. This article also discusses ways to fix the. NET Framework 2.0 or manually remove the. NET Framework 2.0 from the computer, and then reinstall the. NET Framework 2.0.
Back to the top
Requirements
The recommended hardware, software, network infrastructure, and required Service packs are listed below:
Microsoft Windows Server 2003, Microsoft Windows Service Pack 3 (SP3), or Microsoft Windows XP Service Pack 2 (SP2)
Microsoft. NET Framework 2.0.
To obtain the Microsoft. NET Framework version 2.0 redistributable Package (x86), visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?displaylang=zh-cn&FamilyID= 0856eacb-4362-4b0d-8edd-aab15c5e04f5 (http://www.microsoft.com/downloads/details.aspx?displaylang=zh-cn& FAMILYID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5) to obtain the Microsoft. NET Framework version 2.0 redistributable Package (IA64), visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?displaylang=zh-cn&FamilyID= 0856eacb-4362-4b0d-8edd-aab15c5e04f5 (http://www.microsoft.com/downloads/details.aspx?displaylang=zh-cn& FAMILYID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5) Note: To troubleshoot installation problems with the. NET Framework 2.0, you must use the. NET Framework 2.0 The account in the local Administrators user group on the computer.

This article assumes that you are familiar with the following topics:
Microsoft. NET Framework 2.0
• Registry Editor
Windows Installer
Back to the top
Log off and then re-enroll Windows Installer
This action corrects problems that occur in most cases. Additionally, this operation does not affect any currently installed programs that use Windows Installer.
1. Log out of Windows Installer. To do this, click Start and Run, type Msiexec/unregister in the Open box, and then click OK.
2. Re-enroll Windows Installer. To do this, click Start and Run, type Msiexec/regserver in the Open box, and then click OK.
Back to the top
Fix the. NET Framework 2.0
Here are three ways to fix the. NET Framework.
Using the Repair command in a Windows Installer cache file
To repair the. NET Framework 2.0 using the Windows Installer cache file, follow these steps:
1. Click Start and run, type installer in the Open box, and then click OK.
2. In Windows Installer, on the View menu, click Details, right-click the Name column heading, and then click Notes.
3. Right-click the cached Windows Installer file that has the comment "Microsoft. NET Framework 2.0 RTL x86 enu", and then click Repair.
4. After completing the repair process, exit Windows Installer.
To run the. NET Framework 2.0 Redistributable Package at a command prompt
To repair the. NET Framework 2.0 by using the command prompt, follow these steps:
1. Locate the Dotnetfx.exe file that is used to install the. NET Framework 2.0. To do this, use one of the following methods:
? If the. NET Framework 2.0 is installed from a CD or DVD, insert the installation disk into the CD drive or DVD drive.
? If the. NET Framework 2.0 is installed from a hard disk, download the. NET Framework 2.0 Setup program to your hard disk.
? If the. NET Framework 2.0 is installed from a network drive, reconnect to this network drive.
2. Click Start and run, type cmd in the Open box, and then click OK.
3. At the command prompt, run the following command:
%installationpath%\dotnetfx.exe/t:%temp%/C: "Msiexec.exe/fvecms%temp%\netfx.msi" Note:%installationpath% was found in step 1 A placeholder for the path to the Dotnetfx.exe file.
Manually remove and then reinstall the. NET Framework 2.0
Warning: If you modify the registry incorrectly by using Registry Editor or other methods, you may cause serious problems. These issues may require you to reinstall your operating system to resolve. Microsoft cannot guarantee that these issues can be resolved. Modifications to the registry are at your own risk.

Important: These steps may increase your security risk. It can also make your computer or network more vulnerable to attacks by malicious users or by malicious software such as viruses. We recommend the process described in this article to enable the program to run according to design intent, or to implement specific program functions. We recommend that you consider the possible risks of implementing this process in your particular environment before making changes. If you choose to implement this process, please take any appropriate additional steps to protect your system. We recommend that you use this process only if you really need it.
1. Remove the. NET Framework 2.0 from the Windows Installer cache:
• Click Start and run, type installer in the Open box, and then click OK.
• In Windows Installer, on the View menu, click Details.
• Right-click the Name column heading, and then click Notes.
• Right-click the cached Windows Installer file that has the comment "Microsoft. NET Framework 2.0 RTL x86 enu", and then click Uninstall.
• After completing the uninstallation process, exit Windows Installer.
2. Manually remove the following from the computer. Note: These items may not exist on your computer, depending on the current conditions of the. NET Framework installation.
? Urttemp folder
? Mscoree.dll file
? v2.0.50727 folder
To do this, follow these steps:
• Click Start and Run, type System32 in the Open box, and then click OK. The contents of the System32 folder will be displayed in Windows Explorer.
• Locate the "Urttemp" folder and delete it.
• Locate the "mscoree.dll" file, and then delete it.

Note if the. NET Framework 1.1 or. NET Framework 1.0 is also installed on the computer, and you do not intend to reinstall the. NET Framework 2.0, you must repair the. NET Framework 1.1 or. NET Framewor K 1.0. For more information, see the "fixing the. NET Framework" section in the following Microsoft Knowledge Base article:
824643 (http://support.microsoft.com/kb/824643/) How to troubleshoot Microsoft. NET Framework 1.1 Installation issues
• Click Start and run, type Microsoft.NET in the Open box, and then click OK. The contents of the Microsoft.NET folder will be displayed in Windows Explorer.
• In the Microsoft.NET folder, double-click the "Framework" folder.
• In the Framework folder, delete the "v2.0.50727" folder.
• Close the Framework folder.
3. Manually delete the related registry key:
• Click Start and run, type regedit in the Open box, and then click OK to start Registry Editor.
• In Registry Editor, locate and delete the following registry key.

Note: These registry keys may not exist on the computer, depending on the current conditions of the. NET Framework installation.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework setup\ndp\v2.0.50727
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\. netframework\policy\v2.0
• Quit Registry Editor.
4. Use the Windows Installer CleanUp utility (Msizap.exe) to remove Windows Installer information from the registry. The Microsoft Download Center provides the Windows Installer CleanUp utility.

The following files can be downloaded from the Microsoft Download Center:

Close this image to expand this image download the Windows Installer CleanUp Utility (Msicuu2.exe) package now. (http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=3138) For more information about how to download Microsoft Support files, Please click the article number below to view the article in the Microsoft Knowledge Base:
119591 (http://support.microsoft.com/kb/119591/) How to obtain Microsoft Support files from an online service
Microsoft has scanned this file for viruses. Microsoft is using the latest virus detection software available when the file is published. This file is stored on security-enhanced servers that can help prevent unauthorized changes to the file.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
290301 (http://support.microsoft.com/kb/290301/) Windows Installer Cleanup Utility description
To remove Windows Installer information from the registry, follow these steps:
• Click Start and run, type cmd in the Open box, and then click OK.
• At the command prompt, locate the directory that contains the Windows Installer CleanUp utility, and then run the following command:
MSIZap TP {7131646d-cd3c-40f4-97b9-cd9e4e6262ef} restart the computer.
5. Disable all anti-virus programs and all firewall programs that are installed on the computer. To do this, use the System Configuration Utility (Msconfig.exe) to perform a clean boot of the computer. Thereafter, all services that are not needed are disabled.

When you use the System Configuration Utility in diagnostic mode, re-enable the Windows Installer service on the Services tab.

To start the System Configuration Utility, click Start and Run, type msconfig in the Open box, and then click OK.
6. Delete the contents of the Temp folder:
• Click Start and run, type%temp% in the Open box, and then click OK. The contents of the temporary folder will be displayed in Windows Explorer.
• In the temporary folder, on the Edit menu, click Select All.
• On the File menu, click Delete.

Note: Remove as many files and folders as possible from the Temp folder.
7. Reinstall the. NET Framework 2.0. To obtain the Microsoft. NET Framework version 2.0 redistributable Package (x86), visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?displaylang=zh-cn&FamilyID= 0856eacb-4362-4b0d-8edd-aab15c5e04f5 (http://www.microsoft.com/downloads/details.aspx?displaylang=zh-cn& FAMILYID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5) to obtain the Microsoft. NET Framework version 2.0 redistributable Package (IA64), visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?displaylang=zh-cn&FamilyID= 0856eacb-4362-4b0d-8edd-aab15c5e04f5 (http://www.microsoft.com/downloads/details.aspx?displaylang=zh-cn& FAMILYID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5) Note: If you do not want to reinstall the. NET Framework 2.0, and the. NET Framework 1.1 or. NET is installed on your computer Framework 1.0, you must repair the. NET Framework 1.1 or. NET Framework 1.0. These installations must be repaired to replace the Mscoree.dll file and the Urttemp folder

Installation of. NET Framework components fails after a computer restarts unexpectedly