Quick note: WSUS was uninstalled for troubleshooting purposes sometime ago. After fixing whatever caused me to uninstall WSUS (don’t ask, don’t remember, just something to do with network connectivity, new server install and some other conflicting IP on network), I couldn’t reinstall WSUS. Time passed and I noticed that the Windows Updates stopped working as well. Finally got some spare time to track this one down.
Windows update kept giving error 80072EFD – network connectivity message. Microsoft articles didn’t help. The referenced network connection, firewall, AV, host file and Internet security trusted site fixes, but none of those worked.
Quick search on Google found a site that had the exact same issue, although not quite the same failure way. Root of his cause was the same, WSUS was pointing the Windows Update back to itself thus causing the error and apparent network connection issues. (Duh – Windows Update couldn’t find Microsoft Update Servers in my systems!)
So what to do.
Remove the invalid entry in the registry for the mis-pointing URL reference.
Navigate to HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate and notice the entries: “WUServer”=”http://BrokenServer:8530″ & “WUStatusServer”=”http://BrokenServer:8530″.
These tell Windows Update where to find the latest updates. Obviously if WSUS isn’t running on your server, it’s not going to have it.
Solution was to remove the entire key “WindowsUpdate” key from the registry at HKLM\Software\Policies\Microsoft\Windows.
Make sure you backup the key just in case.
Once that’s done, restart the Windows Update Service within the services mmc.
Now try to get the updates. If everything else is good to go, then updates will process and install.
Thanks to Daniel Ihonvbere for this fix. Saved me time today. Here’s his article that I found.