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

2
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 hits the deadline

Fix SCCM Scan Failed to Add Update Source for WUAgent | ConfigMgr 1Issue Description:

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 along with two different error codes.

Screenshot given below:

Fix SCCM Scan Failed to Add Update Source for WUAgent | ConfigMgr
Fix SCCM Scan Failed to Add Update Source for WUAgent | ConfigMgr
  • At the place of 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://alphasoftx.com/?big=sccm-logs-files-configmgr-memcm/

We deployed patches to Windows Server 2008 R2 SP1 using SCCM and waited till it hits the deadline. Deadline crossed and maintenance windows over. Nothing triggered.

When started troubleshooting we found that file that applies group policy or SCCM policy is showing the old date of modification. 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

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

Installed, Rebooted. Server is Compliant. Happy Learning.

You can also try renaming Software Distribution Folder if you are still seeing 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

2 COMMENTS

    • 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

LEAVE A REPLY

Please enter your comment!
Please enter your name here

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