Fix SCCM Scan Failed to Add Update Source for WUAgent | ConfigMgr

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:

Patch My PC
Fix SCCM Scan Failed to Add Update Source for WUAgent | ConfigMgr
Fix SCCM Scan Failed to Add Update Source for WUAgent | ConfigMgr

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 below and should have a recent date and time.

Fix SCCM Scan Failed to Add Update Source for WUAgent | ConfigMgr
Fix SCCM Scan Failed to Add Update Source for WUAgent | ConfigMgr

SolutionScan 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 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:
Fix SCCM Scan Failed to Add Update Source for WUAgent | ConfigMgr
Fix SCCM Scan Failed to Add Update Source for WUAgent | ConfigMgr

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:

  1. Start an elevated command prompt.
  2. Run the following commands hitting enter after each line:

    net stop wuauserv
    cd %systemroot%
    ren SoftwareDistribution SoftwareDistribution.old
    net start wuauserv
  3. Reboot

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.

Resources

Author

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).

3 thoughts on “Fix SCCM Scan Failed to Add Update Source for WUAgent | ConfigMgr”

    • Good Question. Characteristically it happens because of Corrupt local group policy.
      There are several methods to fix this and fix mention in this blog is one of them.

      Few more are:

      Most of them look self explainarry by reading the statement itself. The only way not clear is point 3 which i am mentioning below:

      1. Delete or move registry.pol file
      2. Move or delete secedit.sdb file
      3. Use Command Prompt
      4. Perform DISM and SFC scans
      5. Disable Certificate Services Client – Certificate Enrollment Policy
      6. Delete the contents of the History folder

      For No 3.

      Start Command Prompt as an administrator.
      When Command Prompt starts, run the following commands:
      RD /S /Q “%WinDir%\System32\GroupPolicyUsers”
      RD /S /Q “%WinDir%\System32\GroupPolicy”
      gpupdate /force

      Reply
  1. hi Deepak Rai,
    thank you for your instruction. they help me a lot in troubleshoot my SCCM.
    now i have bunch of error when client try to update / receive update from SCCM. as i checked log i got this msg ” Post to http://sccmsrv/ccm_system/request failed with 0x87d00323.” and ” Scan failed with error = 0x80240438 ” in WUAHandler.log
    Could you give me some instruction how to troubleshoot the issue?

    Reply

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.