Windows System Update Issues Encyclopedia

These days just install the server system, how many encounter some system upgrades updated update problem. Check some information, summed up the solution, next time easier to solve.

When the system installation finishes updating the update, sometimes the system prompts you not to update and the reboot system cannot be resolved. The display interface is shown below:

An update's false positives are typically caused by an update component or the temporary folder in which it is used.

The workaround steps are as follows:

1, download run Fixit 50202 Tool repair Update component.

http://go.microsoft.com/?linkid=9665683

After running the Fixit 50202 tool, select the aggressive Option checkbox in its wizard to force the repair of the update component, and then restart Windows. The test is repaired.

2, Clean softwaredistribution temporary folder.

First turn off system services Automatic Updates, and then manually clean up the windows\softwaredistribution datastore and Download temporary folders by emptying or renaming them before restarting Automatic Updates Service.

This will reset the update download cache. If the issue of update false positives is caused by softwaredistribution temporary folder clutter, resetting the datastore and Download temporary folders can fix all u with Office SP1 Update and Windows Update Pdate false alarm problem.

3. The reason for updating cannot update is that the version of the Update agent (update Client proxy) used by the Windows system does not meet the requirements of update V6. Update V6 requires that the update Agent installed by the system must contain either a WUPS2.DLL file (Windows\System32 folder) or a higher version file in the future.

Sometimes we install Windows with a fix, or reinstall Windows Service Pack patches after installing the update agent without rebooting, which may cause WUPS2. Invalid registration information for DLL. At this time even WUPS2. DLL files will not work. We can use REGSVR32 C:\Windows\system32\WUPS2 by disabling the Automatic Updates service first. DLL command to re-register the file, and then re-enable the Automatic Updates service to fix the WUPS2. The registration information for the DLL.