![]() Rename the C:\Windows\SoftwareDistribution folder to C:\Windows\SoftwareDistribution.old. ![]() Stop the Windows Update service by running the following command: net stop wuauserv ![]() If running the Windows Update Troubleshooter doesn't fix the problem, reset the Windows Update Agent data store on the client by following these steps: It's also a good idea to make sure that you're running the latest version of the Windows Update Agent. A good place to start is to run the Windows Update Troubleshooter to detect and fix these issues automatically. Several issues can be caused by missing or corrupted files or registry keys, component registrations, and so on. For more information about how to read the WindowsUpdate.log file, see Windows Update log files. Most information about the error will likely be found in the WindowsUpdate.log file. So the error in the WUAHandler.log file would be the same error that was reported by the Windows Update Agent itself. WUAHandler just reports what the Windows Update Agent reported. When you troubleshoot software update scan failures, focus on the WUAHandler.log and WindowsUpdate.log files. For more information about Windows Update common errors, see Windows Update common errors and mitigation.įor more information about software updates in Configuration Manager, see Software updates introduction. We describe some of the most common error conditions and their associated resolutions and troubleshooting tips here. Most problems involve communication or firewall issues between the client and the software update point computer. There are several reasons that a software update scan could fail. Original product version: Microsoft System Center 2012 Configuration Manager, Microsoft System Center 2012 R2 Configuration Manager Original KB number: 3090184 Summary This article describes how to troubleshoot software update scan failures in Configuration Manager.
0 Comments
Leave a Reply. |