The installation errors of DOTNET Framework 3.5 found on Google are mainly caused by incomplete uninstallation, because version 3.5 is not compatible with the previous framework, while the Framework often leaves some tails during uninstallation, resulting in 3.5 frequent installation failure. In the reference articles at the end of the article, you can see Representative articles and solutions. Two software programs will be used here. One is the dotnetfix cleanup tool (this link is valid for the 20100331 test). This tool is used to completely uninstall all versions of DOTNET framework,msicu2.exe (this link is valid for the 20100331 test ), this is used to uninstall the installation information in Windows installer. These two tools can completely solve various installation problems caused by incomplete framework uninstallation. However, the installation error of DOTNET Framework 3.5 is caused by many reasons. This is definitely a cup of cake that Xiao Chen has encountered, so I can't help but share it with you. First, Xiao Yu thought it was a problem caused by incomplete uninstallation and version incompatibility. By chance, Xiao Yu gave a look at the system log and then suddenly realized. Open "Event Viewer" in "Computer Management" and view the abnormal status and information of the installer in "application.
Text Information on the right:Event Type: Information
Event Source: msiinstaller
Event Type: None
Event ID: 11707
Description: Product: Microsoft. NET Framework 3.5 -- installation is successful.
Text on the left:
Event Type: Error
Event Source: msiinstaller
Event Type: None
Event ID: 11933
Description: Product: MSXML 6.0 Parser (kb933579) -- error 1933. the Windows Installer Service cannot update one or more protected Windows files. SFP error: 21. list of protected files:/R/NC:/Windows/system32/msxml6.dll, C:/Windows/system32/msxml6r. DLL
Now it is clear that DOTNET has been successfully installed. Due to XML errors, the originally installed DOTNET is rolled back, causing the entire installation process to fail. Download msxml6.dll and msxml6r. dll, copy them to the System32 folder, and install them again.
Summary:
- Windows Installer and the installers of other companies are a double-edged sword in my opinion. While providing convenience, there will be some inexplicable problems. At this time, it is a good way to view analysis errors through the Event Viewer that comes with the system!
- In addition, if you encounter such a specific problem, you may find unexpected gains by searching on a Google Blog.
References:
- One solution to the failure of installing. NET Framework 3.5 Is to unload all versions of the framework and reinstall it.
- Removal Tool to fix. NET Framework install failures. This article describes the residual information of a tool to uninstall the framework and then reinstall it.
- When you try to install it on a Windows XP-based computer on the Windows Update site. net Framework 1.1 Service Package 1 is updated with an error message: "The update fails to be successfully installed." This article from Microsoft details various uninstallation. net Framework Method
Source: http://zypcaid.blog.163.com/blog/static/412768412010231111456150/
