Let’s find out a fix to SCCM Scan Failed to Add Update Source for WUAgent. We deployed patches to Windows Server 2008 R2 SP1 using SCCM and waited till it hit the deadline.
Like any other error, this issue is a bit particular because it’s not generating only a single line error with a generic code but two different errors and two different error codes.
The screenshot is given below:
When jumping directly to the solution, let’s understand the root cause for better understanding. The screenshot was taken from WUHandler.log at the time of troubleshooting.
For more details on how to collect or read SCCM logs, please refer article below: – https://www.anoopcnair.com/sccm-logs-files-configmgr-memcm/
We deployed patches to Windows Server 2008 R2 SP1 using SCCM and waited till it hit the deadline. Deadline crossed and maintenance windows over. Nothing triggered.
When we started troubleshooting, we found that the file that applies group policy or SCCM policy shows the old modification date. But it should look like the below and should have a recent date and time.
Solution – Scan Failed to Add Update Source for WUAgent
The fix for the issue is to rename the registry.pol and restart the SMS agent services.
- Go to the below path: C:\Windows\System32\GroupPolicy\Machine
- Rename the Registry.pol file.
- Take a copy of this file before you rename it.
- Now restart CCMEXEC- SMS Agent Host service and trigger SCAN
- After this step we started reading WUAhandler:
Scan completed successfully and after triggering “Software Update Deployment Evaluation Cycle” patches exposed in Software Center.
It was installed, Rebooted. The server is Compliant. Happy Learning. You can also try renaming Software Distribution Folder if you still see any errors in WUAHandler. Steps below:
- Start an elevated command prompt.
- Run the following commands hitting enter after each line:
net stop wuauserv
ren SoftwareDistribution SoftwareDistribution.old
net start wuauserv
Disclaimer – The information provided on the site is for general informational purposes only. All information on the site is provided in good faith; however, we make no representation or warranty of any kind, express or implied, regarding the accuracy, adequacy, validity, reliability, availability, or completeness of any information on the website.
- Fix SCCM Scan Issues with Software Updates Patching | ConfigMgr
- SCCM How to Get a Troubleshooting Report for Patching Software Update Related Scan Errors
- How to troubleshoot software update scan failures in System Center 2012 Configuration Manager
My name is Deepak Rai, and I am a Technical Lead on SCCM and Intune with more than 14 years of experience in IT. My main domain is SCCM (AKA ConfigMgr, CB, MECM, etc.), Intune, and Azure (Runbooks). I have worked on several platforms (Active Directory, Exchange, Veritas NETBACKUP, Symantec Backup Exec, NDMP devices Like Netapp, EMC Data Domain, Quantum using Backup Exec 2010 and 2012, HP storage works 4048 MSL G3, Data Deduplication related troubleshooting.) in these 13 years but at last ended up to the technology from which I started as IT Engineer (SCCM).