Windows system update problem summary

The server system has been installed in the past few days, and some system UPDATE and UPDATE problems have occurred. I checked some information and summarized the solution to facilitate the next solution.
 
After the system is installed and updated, sometimes the system prompts that the UPDATE cannot be performed, and the system cannot be restarted. The display page is shown as follows:
 
 

 
The false positive of UPDATE is usually caused by damage to the Update component or the Temporary Folder used by the UPDATE component.
The solution is as follows:
 
1. download and run the Fixit 50202 tool to fix the Update component.
Http://go.microsoft.com /? Linkid = 9665683
 
After running the Fixit 50202 tool, select the "Aggressive Option" check box in the Wizard to forcibly repair the Update component and restart Windows. Test whether to fix the vulnerability.
 
2. Clear the temporary SoftwareDistribution folder.
First, disable the system service Automatic Updates, and then manually clear the DataStore and Download Temporary Folder of Windows \ SoftwareDistribution by clearing or renaming the system service, and then restart the Automatic Updates service.
 
This allows you to reset the Update download cache. If the Update false positive is caused by the confusion of the SoftwareDistribution Temporary Folder, resetting the DataStore and Download temporary folders can fix all UPDATE false positive errors, including Office 2010 SP1 Update and Windows UPDATE.
 
3. The reason for UPDATE failure may be that the UPDATE Client Proxy Stub version used in Windows does not meet the Update v6 requirements. Update v6 requires that the UPDATE Agent installed by the system must contain WUPS2.DLL files (in the Windows \ system32 folder) or later versions.
 
Sometimes we have fixed Windows installation, or reinstall the Windows Service Pack patch package without restarting the UPDATE Agent, which may cause WUPS2.DLL registration information to fail. In this case, even if the WUPS2.DLL file exists, it cannot be used. We can fix WUPS2.DLL registration information by first disabling the Automatic Updates service, then using the REGSVR32 C: \ Windows \ system32 \ WUPS2.DLL command to re-register the file, and then re-enabling the Automatic Updates service.
 
If the WUPS2.DLL file does not exist in the system or the file cannot be re-registered, you need to re-install the UPDATE Agent.
 
Install the Windows UPDATE agent:
 
Http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.4.7600.226/WindowsUpdateAgent30-x86.exe
 
(For x86 Windows)
 
Http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.4.7600.226/WindowsUpdateAgent30-x64.exe
 
(For x64 Windows)
 
Http://download.windowsupdate.com/windowsupdate/redist/standalone/7.4.7600.226/windowsupdateagent30-ia64.exe
 
(For IA64 Windows)
 
If you confirm that WUPS2.DLL has been correctly installed, You need to monitor whether the IE add-on works properly.
 
Open "Manage Add-on" of IE and check whether there is an add-on named MUWebControl Class from Microsoft.
If you do not have this add-on or it has been disabled, reinstall the UPDATE Agent and re-enable the add-on.
 
 
 
 
 
Additional Notes:
 
1. Pay attention to the installation sequence when updating the SP update Patch and IE browser. Improper installation may cause failure to uninstall IE. The best way is to first update the patch package with SP, and then consider upgrading IE. If You Cannot uninstall IE, you should first uninstall the SP update Patch and then uninstall IE.
 
(When we launched IE8 earlier, we upgraded the browser. It is said that a large number of people are in bad luck and the installation sequence is incorrect. They were crashed and Cannot uninstall IE8)
 
2. Upgrade and install Windows Service Pack. (Maybe no one pays attention to this issue. In short, I just hope you can pay more attention to some official Microsoft installation instructions. Many inexplicable problems are caused by not reading the documentation before installation .)
Before Windows XP SP2 (inclusive), all Windows Service packs are completely backward compatible and can be upgraded from any old version to the latest version. For example, Windows 2000 SP4 and Windows NT SP6 can be upgraded directly from RTM.
However, since Windows XP SP3 & Windows Vista SP2, the old version of the Service Pack is gradually discarded. You must install the old version of the Service Pack before installation.
 
Windows XP SP3 (SP1 or SP2 must be installed first, but RTM is not supported); Windows Vista SP2 (SP1 must be installed first, but RTM is not supported ). Fortunately, Windows 7 currently only has SP1, or you have to study it again.
 
3. Integrate the Windows Service Pack file into the Windows Installation Folder.
 
Please refer to the Microsoft forum post "Integrating the Windows XP Service Pack 3 file into the Windows XP installation folder"
 
 
This article is from the "Network" blog