If no updates show up in Software Center (while there should be) you preferably start searching in you SCCM log files for errors.
Logfiles ScanAgent.log and WUAHandler.log are a good place to start. These are by default located in C:\Windows\CCM\Logs\
Hint: use CMTrace (Configuration Manager Trace Log Tool to get a readable log file with highlighted errors)
I found the following errors:
Failed to Add Update Source for WUAgent of type (2) and id ({82ADFE9C-FB95-4F72-B0B7-114F9A4A3A43}). Error = 0x800703ee.
Unable to read existing WUA Group Policy object. Error = 0x800703ee.
CScanJob::Execute- Failed at AddUpdateSource, Error = 0x800703ee
Error 0x800703ee
In case of error 0x800703ee, here’s how to fix it
- Browse to the following folder on the problematic machine:
C:\Windows\System32\GroupPolicy\Machine\
(note: this folder may be hidden) - Notice there’s a Registry.pol file, which file date is probably a while ago
Delete that file - From a command prompt, run GPUpdate /force
Notice the Registry.pol file is recreated. If not, reboot the machine. - From Control Panel, open Configuration Manager Properties. Go to tab Actions and choose Software Updates Scan Cycle
- In a few minutes new updates should appear in your Software Center. Recheck your logfiles for further errors if the problem remains.
Still having issues? Leave a comment! I will update this article if necessary.
For further reference, these are the lines you may see:
Its a WSUS Update Source type ({GUID string}), adding it. WUAHandler 3/4/2019 1:42:00 PM 404 (0x0194)
Not RS3+, this device is SCCM managed. WUAHandler 3/4/2019 1:42:00 PM 3872 (0x0F20)
SourceManager::GetIsWUfBEnabled – There is no Windows Update for Business settings assignment. Windows Update for Business is not enabled through ConfigMgr WUAHandler 3/4/2019 1:42:00 PM 3872 (0x0F20)
Unable to read existing WUA Group Policy object. Error = 0x800703ee. WUAHandler 3/4/2019 1:42:00 PM 404 (0x0194)
Enabling WUA Managed server policy to use server: http://SCCMserver:8530 WUAHandler 3/4/2019 1:42:00 PM 404 (0x0194)
Not RS3+, this device is SCCM managed. WUAHandler 3/4/2019 1:42:00 PM 4988 (0x137C)
SourceManager::GetIsWUfBEnabled – There is no Windows Update for Business settings assignment. Windows Update for Business is not enabled through ConfigMgr WUAHandler 3/4/2019 1:42:00 PM 4988 (0x137C)
Failed to Add Update Source for WUAgent of type (2) and id ({GUID string}). Error = 0x800703ee. WUAHandler 3/4/2019 1:42:00 PM 404 (0x0194)
Thanks, this helped me!
Perfect. Helped for me on a W2008 R2 and W2012 R2 server.
Thanks
Thats great Ruedi! Thnx for letting me know! It encourages me to keep this blog active!
Also worked great on Server 2016 🙂 Thanks, it saved my day,
I tried this but the file does not recreate after running gpupdate /force even after a restart. Any suggestions?
Just copy the file from a PC which does not have any issues and paste it on the affected machines. That fixed it for me.
Finally, something that works for me. Thanks
P.S. For those who say the file does not get created after gpupdate or restart, just copy the file from a PC which does not have any issues and paste it on the affected machines. That fixed for me.
esto me funciono, gracias por el aporte
make a temp change to local group policy, run gpupdate then remove the change and run again. File will be created after the first update.
Spent a couple of hours to troubleshoot it until found your article. Wouldn’t ever guess it can be related to registry.pol.
It worked, thank you John!
Thanks so much it works for me, but if possible could you tell us what’s the root cause. I experienced this issue with about 200 machine
Awesome! It worked like a charm! Thank you!
Thanks!!!
It worked like a charm.
Same issue, however couldnt find C:\Windows\System32\GroupPolicy in the computer
Worked as charm… awesome
Great! This workaround works but what is the root cause here? Any idea? Why deleting Registry.pol fix MECM Software Update?