This page looks best with JavaScript enabled

Resolving Windows Server Update Services Connection Errors On Windows Server 2012 R2

 ·  ☕ 2 min read

WSUS Unexpected Error

Update 2018-04-20: I’ve rolled the information in this post, and updated it, into a new post about setting up a WSUS server from scratch on Windows Server 2016 Core. The post is also suitable for a regular Windows Server 2016 server with a GUI. You can read it here.

Update 2017-05-03: If you’re looking to resolve similar problems with WSUS on Windows Server 2016, please see this post.

If you’ve been managing a WSUS server, you may have run into the well known MMC connection error above (appears as Event ID 7053 in the Event Viewer) by now. I started experiencing it more often after installing Windows Server 2012 R2’s WSUS but was able to quickly solve my issue. Later when setting up another 2012 R2 WSUS server I had the same issue but the same fix didn’t work. I eventually solved the problem with that server though.

Here’s a small collection of resolutions and notes on this problem. On one of my WSUS servers, increasing the memory allocated to the WSUS application pool in IIS solved the problem. The server in question was a Hyper-V VM with 8GB of RAM (non dynamic) allocated. I increased the pool to 6000000 KB (6 GB) and thus far it’s solved the issue on this server.

IIS Private Memory Limit

On another WSUS server I setup recently, (which had less RAM) the issue was solved by running the WSUSUtil command line utility. WSUSUtil is located in %systemdrive%\Program Files\Update Services\Tools folder.

"%systemdrive%\Program Files\Update Services\Tools\wsusutil" postinstall /servicing

From what I’ve read online a common cause of the problem seems to be the installation of certain updates and the reported solution is to uninstall these updates - I’ve never had to uninstall any updates to solve this issue, at the time of writing. To give you an idea of how strange this issue seems to be, I’ve had this exact problem when I’ve installed WSUS:

  • After a full Windows Update run from the internet.
  • After a full Windows Update run from the internet.
  • Using a local SQL Express instance to store the WSUS DB.
  • Using Windows Internal Database to store the WSUS DB.
  • Having a small number of clients.
  • Having a large number of clients.

Hopefully this helps you. I’ll make a post in future on how I install WSUS servers currently and some things that I’ve learned to look out for, but until then happy WSUS’ing! I think this is the worst way I’ve ever ended a blog post ever.

If you have any questions or comments please leave them below.


Share on
Support the author with