Solutions for Windows Update error 80072EE2

I’ve been building serveral small test servers and workstations, but I ran into a Windows Update error 80072EE2 putting a test server on my production network.  After a quick google, there seems to be a ton of different causes for this but they are all network related.  Here’s the steps I recommend for troubleshooting this:

  1. Verify connectivity to Windows Update or your WSUS server.
  2. Verify your IP address and DNS servers are correct.
  3. Ensure the following sites are listed in IE’s trusted sites list:
    1. Your WSUS server’s name if used.
    2. *.update.microsoft.com
    3. *.windowsupdate.com
    4. *.windowsupdate.microsoft.com
    5. update.microsoft.com
    6. Restart the Windows Update service once your made these changes.
  4. Reset the Software Distribution folder – start a command prompt in administrative mode then enter the following:
    1. net stop wuauserv
    2. net stop bits
    3. del /s /q c:windowssoftwaredistribution
    4. net start quauserv
    5. net start bits
    6. wuauctl /resetauthorization /detectnow
    7. Wait 15-20 minutes and see if the system detects updates.
  5. Run a GPUDPATE /FORCE, then run RSOP.MSC and verify the group policy settings for Window Update.  Try this even if you aren’t running domain group policy, as someone might have set the local policy.
  6. Some have reported deleting the NIC from Device Manager and rebooting corrects this problem.  If you have gotten to this point, it may be worth trying.  Windows Vista, 7, and 2008 should reinstall the NIC after a reboot.

I will update these steps as I discover more issues.  Remember – always troubleshoot the path of least resistance first.

(Migrated from https://normesysadmin.blogspot.com 6/16/16)

Leave a Comment

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