Skip to content
Trending
Simplify Windows Devices to Run Only the Required Applications using Intune Enhance macOS Compliance with Custom Security and Compliance Checks to Improve Device Security using Microsoft Intune Manage Samsung Galaxy Firmware Versions to Improve Security and Compliance using Microsoft Intune MS Intune Adds Windows Registry Data Collection to Device Inventory for Single Values All Key Values and Subkeys Updated Windows Device Sync Experience Enhances Per-Device Troubleshooting Configure Windows Sandbox vGPU Policy using Intune for Better Graphics Performance or Reduced Attack Surface Simplify Windows Devices to Run Only the Required Applications using Intune Enhance macOS Compliance with Custom Security and Compliance Checks to Improve Device Security using Microsoft Intune Manage Samsung Galaxy Firmware Versions to Improve Security and Compliance using Microsoft Intune MS Intune Adds Windows Registry Data Collection to Device Inventory for Single Values All Key Values and Subkeys Updated Windows Device Sync Experience Enhances Per-Device Troubleshooting Configure Windows Sandbox vGPU Policy using Intune for Better Graphics Performance or Reduced Attack Surface
Fix SCCM Scan Failed to Add Update Source for WUAgent | ConfigMgr

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

Written By Deepak Rai
Last Updated June 28, 2024
Posted In SCCM
SHARE

Let’s find a fix for SCCM Scan Failed to Add Update Source for WUAgent. Software Update Scan Issues in SCCM Due to Proxy Settings When the proxy settings are configured on the core servers. They can cause communication blocks for clients trying to reach the WSUS server. All client communications intended for the WSUS/SCCM server (FQDN) are halted at the proxy server.

Index
Fix SCCM Scan Failed to Add Update Source for WUAgent
Solution – Scan Failed to Add Update Source for WUAgent
Fix SCCM Scan Failed to Add Update Source for WUAgent | ConfigMgr – Table 1

Fix SCCM Scan Failed to Add Update Source for WUAgent

We deployed patches to Windows Server 2008 R2 SP1 using SCCM and waited until the deadline. Like any other error, this issue is a bit particular because it generates a single-line mistake with a generic code and two different errors and error codes.

The screenshot is given below:

Fix SCCM Scan Failed to Add Update Source for WUAgent | ConfigMgr - Fig.1
Fix SCCM Scan Failed to Add Update Source for WUAgent | ConfigMgr -Fig.1

When jumping directly to the solution, let’s understand the root cause for better understanding. The screenshot was taken from WUHandler.log during troubleshooting.

Patch My PC

For more details on how to collect or read SCCM logs, please refer to the article below: – https://www.anoopcnair.com/sccm-logs-files-configmgr-memcm/

We deployed patches to Windows Server 2008 R2 SP1 using SCCM and waited until the deadline. The deadline was crossed, and maintenance windows were over. Nothing triggered.

When we started troubleshooting, we found that the file that applies the group or SCCM policies shows the old modification date. However, it should look like the one below and have a recent date and time.

NameDate modified TypeSize
Registry.pol7/25/2020 11:04 PMPOL file79 KB
Fix SCCM Scan Failed to Add Update Source for WUAgent | ConfigMgr – Table 2
Fix SCCM Scan Failed to Add Update Source for WUAgent | ConfigMgr - Fig.2
Fix SCCM Scan Failed to Add Update Source for WUAgent | ConfigMgr – Fig.2

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

The scan was completed successfully, and after triggering the “Software Update Deployment Evaluation Cycle,” patches were exposed in the Software Center.

It was installed and rebooted. The server is Compliant. Happy Learning. You can also try renaming the 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

We are on WhatsApp. To get the latest step-by-step guides and news updates, Join our Channel. Click here –HTMD WhatsApp.

Author

Deepak Rai is a Technical Lead with over 14 years of experience in IT. He specializes in SCCM, Intune, and Azure. Throughout his career, he has worked on various platforms such as Active Directory, Exchange, Veritas NETBACKUP, Symantec Backup Exec, NDMP devices like Netapp, EMC Data Domain, Quantum using Backup Exec 2010 and 2012, and HP StorageWorks 4048 MSL G3. He also has experience in data deduplication-related troubleshooting. Ultimately, he returned to his roots as an IT Engineer focusing on SCCM technology.

Written by

My name is Deepak Rai and i am Technical Lead on SCCM and Intune with more than 14 years of experience in IT. My main domain is SCCM 2012, CB, MECM, 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, Quantam using Backup Exec 2010 and 2012, HP storage works 4048 MSL G3 , Data Deduplication related troubleshooting.) in these 13 years but finally ended up to the technology from which i started as IT Engineer (SCCM).

Discussion · 4 comments

  1. More than solution I would like to know y it’s happening, and renaming registry file is temporary solution

    Reply

    1. StaffGood 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

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

Join the discussion

Your email address will not be published. Required fields are marked *

Related guides

Intune

Windows 11 KB5101650 KB5099414 July 2026 Patch and 3 Zero Day Vulnerabilities and 570 Flaws

Key Takeaways Windows 11 KB5101650 KB5099414 July 2026 Patch and 3 Zero Day Vulnerabilities and 570 Flaws! In the July 2026 Patch, Microsoft introduced new features designed to improve the overall Windows experience. The update adds enhancements to Windows Update for more flexible update management and introduces Point-in-Time Restore, providing an additional recovery option for […]

AC Anoop C Nair 9 min read
Intune

2026 June KB5094126 KB5093998 Windows 11 Patch | 3 Zero Day Vulnerabilities and 200 Flaws

Key Takeaways 2026 June KB5094126 KB5093998 Windows 11 Patch | 3 Zero Day Vulnerabilities and 200 Flaws! The June 2026 Windows 11 Patch Tuesday update brings several improvements to File Explorer. It adds support for additional archive formats, including UU, CPIO, XAR, and NuGet Packages (NUPKG). The update also preserves View and Sort preferences in […]

AC Anoop C Nair 10 min read
Intune

2026 May KB5089549 KB5087420 Windows 11 Patch | 0 Zero Day Vulnerabilities and 120 Flaws

Key Takeaways The Windows 11 May 2026 Patch KB5089549 KB5087420 Update brings important security fixes, performance improvements, and reliability enhancements across the operating system. The update introduces new features such as Xbox Mode for gaming, File Explorer improvements, enhanced input and sharing experiences, better taskbar and Windows Hello reliability, and additional enterprise management capabilities for […]

AC Anoop C Nair 8 min read
SCCM

ConfigMgr 2603 Introduces New Early Update Enrollment Process

Key Takeaways In this post we are discussing the ConfigMgr 2603 Introduces New Early Update Enrollment Process. Microsoft has officially released Configuration Manager version 2603 to the Early Update Ring, giving organizations an opportunity to test upcoming improvements before the global production rollout. The release is targeted at enterprises running ConfigMgr version 2409 or later […]

AC Anoop C Nair 3 min read