


Please see How to enable WMI monitoring on a single Windows device for complete instructions.Īuvik uses the Windows Remote Management (WinRM) protocol to access Windows Management Instrumentation (WMI) data. I have renamed Registry.pol to you don't have a domain controller but would still like to monitor your Windows devices, you'll need to enable WMI device by device. Finally re-run the Software Updates Scan Cycle in the Configuration Manager Actions tab.Restart the SMS agent host service(SCCM client agent service-CCMEXEC) and that should fix Error 0x80004005.You may also delete the Registry.pol file from the machine folder.Backup the Registry.pol file to a different folder or simply rename it, something like.On the client computer, go to C:\Windows\System32\GroupPolicy\Machine.Perform the below steps if you are noticing the Failed to Add Update Source for WUAgent of type (2) message in WUAHandler.log. Fix Failed to Add Update Source for WUAgent of type (2) Error 0x80004005 However before you delete it, it is recommended that you back up the file. One file contains computer settings and the other file contains user settings.ĭeleting the Registry.pol will not cause any issue because it creates a new file with same name. These are stored in folders under the :\Windows\System32\GroupPolicy\ folder. What is Registry.pol ?.Īccording to Microsoft, the Group Policy Object Editor stores registry-based configuration settings in two Registry.pol files. I think this could be due to the corrupt local group policies on the client machine. While there is no exact answer to this, here is my assumption. Now the question here is why was that error logged in WUAHandler.log.

GetUpdateInfo - failed to get targeted update, error = 0x87d00215. Failed to Add Update Source for WUAgent of type 2 Failed to Add Update Source for WUAgent of type (2) and id () successfully.
