Log on to the server directly or using a third-party remote control program.

Microsoft has a released a fix to address problems with its Windows Server Update Services (WSUS) tool.

But deep inside the WSUS server, things are a mess: The WSUS server is the only computer that can get updates from itself, it cannot communicate with clients, and after a few days, all computers—except for the WSUS server itself—are listed as .

So, if you know for sure the exact update that does this, please comment.

On the surface at least, the server looks OK: It synchronizes with upstream Microsoft servers, displays newly-published updates, approves and declines as been told, and downloads approved updates flawlessly.

Since this wasn’t working and the 2016 WSUS server would not download any files from Microsoft, I figured I’d point my TEST 2016 server to my current (working) PRODUCTION WSUS 2012R2 and it had a similar problem.

The Test 2016 server would report in to the 2012R2 Production WSUS server (like normal), I could see what updates were needed, and the WSUS server being a 2012R2 server already had the update files downloaded for approval...

After deploying WSUS on a Server 2012 R2 Essentials machine, I allowed WSUS to update itself with KB3159706.

This upgrades WSUS to supply Windows 10 upgrades (not in use at this location) but the more obvious effect is that it kills WSUS: while connected via Remote Desktop.

An update to WSUS 3.0 SP2 on Windows Server 2008 R2 and Windows Server 2008 (both x64 and x86) seems to break Windows Server Update Services (WSUS) and/or Internet Information Services (IIS) making clients unable to update via WSUS showing error 0x80072EE2.

To me, the subversive update number is not clear yet.

Other Windows servers in your network will then download the updates from the WSUS server rather than the Internet, saving you Internet bandwidth and speeding up the Windows update process.

With WSUS we can configure all of our servers to be automatically updated, ensuring that security updates are installed quickly from a central location.

I also see that the install successfully completed: Step 2 calls for enabling .