On few client machines I noticed Failed to Add Update Source for WUAgent of type (2) Error = 0x80004005 in WUAHandler.log. You may also encounter this same issue with error 0x8007000d.

Let me show you what I saw in WUAHandler.log file on the client machine. Failed to Add Update Source for WUAgent of type (2) repeats for every ID. The error code could be either 0x80004005 or 0x8007000d.

The second error that we see is unable to read existing WUA Group Policy object. Error = 0x80004005.

Install and Update Third Party Applications with Patch My PC
Install and Update Third Party Applications with Patch My PC
Failed to Add Update Source for WUAgent of type 2
Failed to Add Update Source for WUAgent of type 2
Failed to Add Update Source for WUAgent of type (2) and id ({AA5DBF4A-0002-4D92-BD93-8972BED9C201}). Error = 0x80004005. WUAHandler 14-12-2020 18:05:45 11460 (0x2CC4)
Its a WSUS Update Source type ({AA5DBF4A-0002-4D92-BD93-8972BED9C201}), adding it. WUAHandler 14-12-2020 18:05:46 23352 (0x5B38)
Device is not MDM enrolled yet. All workloads are managed by SCCM. WUAHandler 14-12-2020 18:05:46 21356 (0x536C)
SourceManager::GetIsWUfBEnabled - There is no Windows Update for Business settings assignment. Windows Update for Business is not enabled through ConfigMgr WUAHandler 14-12-2020 18:05:46 21356 (0x536C)
Unable to read existing WUA Group Policy object. Error = 0x80004005. WUAHandler 14-12-2020 18:05:46 23352 (0x5B38)
Enabling WUA Managed server policy to use server: https://corpsccm.prajwal.org:8531 WUAHandler 14-12-2020 18:05:46 23352 (0x5B38)
Device is not MDM enrolled yet. All workloads are managed by SCCM. WUAHandler 14-12-2020 18:05:46 4352 (0x1100)
SourceManager::GetIsWUfBEnabled - There is no Windows Update for Business settings assignment. Windows Update for Business is not enabled through ConfigMgr WUAHandler 14-12-2020 18:05:46 4352 (0x1100)
Failed to Add Update Source for WUAgent of type (2) and id ({AA5DBF4A-0002-4D92-BD93-8972BED9C201}). Error = 0x80004005. WUAHandler 14-12-2020 18:05:46 23352 (0x5B38)

The software updates deployment wasn’t working on these client machines. These machines were on VPN and I observed same errors on these machines.

The UpdatesDeployment.log file reported failed to get targeted update, error = 0x87d00215. This clearly explains that something was wrong.

Failed to Add Update Source for WUAgent Snap2
GetUpdateInfo - failed to get targeted update, error = 0x87d00215. UpdatesDeploymentAgent 14-12-2020 18:46:30 484 (0x01E4)
Assignment {27ac5caa-8f4a-4379-a13d-9a34f395ae3f} has total CI = 257 UpdatesDeploymentAgent 14-12-2020 18:46:30 484 (0x01E4)
Assignment ({27ac5caa-8f4a-4379-a13d-9a34f395ae3f}) reconnected to the existing job ({B8921FF0-0675-4B22-933D-EB75E405CA42}) successfully. UpdatesDeploymentAgent 14-12-2020 18:46:30 484 (0x01E4)
GetUpdateInfo - failed to get targeted update, error = 0x87d00215. UpdatesDeploymentAgent 14-12-2020 18:46:30 484 (0x01E4)

Now the question here is why was that error logged in WUAHandler.log. While there is no exact answer to this, here is my assumption. I think this could be due to the corrupt local group policies on the client machine.

What is Registry.pol ?.

According to Microsoft, the Group Policy Object Editor stores registry-based configuration settings in two Registry.pol files. These are stored in folders under the <drive>:\Windows\System32\GroupPolicy\ folder. One file contains computer settings and the other file contains user settings.

Deleting the Registry.pol will not cause any issue because it creates a new file with same name. However before you delete it, it is recommended that you back up the file.

Fix Failed to Add Update Source for WUAgent of type (2) Error 0x80004005

Perform the below steps if you are noticing the Failed to Add Update Source for WUAgent of type (2) message in WUAHandler.log.

  • On the client computer, go to C:\Windows\System32\GroupPolicy\Machine.
  • Backup the Registry.pol file to a different folder or simply rename it, something like Registry.old.pol.
  • You may also delete the Registry.pol file from the machine folder.
  • Restart the SMS agent host service(SCCM client agent service-CCMEXEC) and that should fix Error 0x80004005.
  • Finally re-run the Software Updates Scan Cycle in the Configuration Manager Actions tab.

I have renamed Registry.pol to Registry.old.pol.

Rename Registry.pol file
Rename Registry.pol file

Next, on the client machine, go to services console and restart SMS Agent Host service.

Restart SMS Agent Host Service
Restart SMS Agent Host Service

After you restart SMS agent host service, go back to C:\Windows\System32\GroupPolicy\Machine. Notice that we have a new Registry.pol file. You may delete the old file now.

New Registry.Pol file Created
New Registry.Pol file Created

Now re-run the Software Updates Scan Cycle in the Configuration Manager Actions tab. Open the WUAHandler.log and notice that we don’t see Failed to Add Update Source for WUAgent Error = 0x80004005 anymore.

Failed to Add Update Source for WUAgent
Failed to Add Update Source for WUAgent

Still Need Help?

If you need further assistance on the above article or want to discuss other technical issues, check out some of these options.

Forums Telegram Contact Me

Prajwal Desai

Prajwal Desai is a technology expert and 10 time Dual Microsoft MVP (Most Valuable Professional) with a strong focus on Microsoft Intune, SCCM, Windows 365, Enterprise Mobility, and Windows. He is a renowned author, speaker, & community leader, known for sharing his expertise & knowledge through his blog, YouTube, conferences, webinars etc.