Error = 0x800703ee (Failed to Add Update Source for WUAgent) RESOLVED

Just recently, I’ve been wondering why I haven’t been prompted with any new Windows Updates from SCCM. I haven’t had too much time to look into this, but thought today is the day to get this sorted.

My colleagues on the other hand were ecstatic that they were receiving these updates. The ADR policy set for Windows 8.1 updates (critical and security updates ONLY) is to deploy 2 days after it’s release and wait a further 7 days until it is forced installed. We too have another ADR policy for Office 2013 updates. Same rule applies, 2 days deploy, 7 days install.

Having being well over that 7-9 day period, the boys are constantly prompted about a reboot (note – some of my colleagues reboot their PCs on an annually occurrence…….).

Identifying Problem

Firstly, when troubleshooting windows update issues on a PC this managed by SCCM, you will need to browse to the following directory;


This log file will more or less advise what the problem or at least, guide you in the right direction in terms of identifying update issues.

WSUS Error

Highlighted red, was the issue at hand – Failed to Add Update Source for WUAgent of type (2) and id {GUID string}. Error = 0x800703ee

After reviewing Matthew Hudson’s blog, even though the error message is different, the process that he advised worked for me.


Browse to the following directory;


You should see the Registry.pol file.

Rename It (i.e. Registry.pol.old).

WSUS Error 2

Once you’ve renamed said file, ensure you have the WUAHandler.log open.

Open up the Services (services.msc) window on the client PC and restart the SMSAgent service.

WSUS Error 6

Once reset, re-run the Software Update Scan Cycle under the Configuration Manager Actions Tab

WSUS Error 7

Once reset, you should see the WUAHandler.log file populate.

WSUS Error 3

Software Center should now display all missing updates.

WSUS Error 4

Hope this helps someone out there!

Good luck.

12 thoughts on “Error = 0x800703ee (Failed to Add Update Source for WUAgent) RESOLVED

  1. Pär October 21, 2015 / 7:37 pm

    Thank you for the tip!

    We had this error on our primary sccm server (!) and your solution seems to work. We had manually installed all available updates just before, but at least the error is gone from the wuahandle.log now.

    I guess we’ll know for sure after next patch tuesday. 🙂

    Liked by 1 person

      • Pär July 14, 2016 / 6:01 pm

        No problem! 🙂 It’s been working well since this problem.

        Liked by 1 person

  2. Shrikant Bhave August 5, 2016 / 12:11 am

    Thanks Robin, just to add, this solution works for the below error codes as well.


    Liked by 1 person

  3. Anonymouse September 13, 2016 / 9:03 pm

    Thanks, been really helpful.

    Liked by 1 person

  4. Thanker... June 30, 2017 / 3:53 am

    Thanks Robin..That helped me today(June 29, 2017) on a Windows 2012 R2 server. Been scratching my head for a long time…

    Liked by 1 person

    • Robin Hunuki April 4, 2018 / 11:58 pm

      No problem at all mate, appreciate the feedback and response! Glad you managed to get it resolve (and apologies for the delayed response!). Hope all is well.

      Liked by 1 person

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s