Windows Update fails with error 8007000E in Windows 2008 R2

I have been doing a lot of work with Windows Update and patching recently and have encountered error 8007000E in Windows 2008 R2 numerous times.  While I consider this a generic error as numerous factors can cause this error to be thrown, there are a few steps that you can take to get past this error and get your Windows 2008 R2 server to update properly.

  1. Reboot the server.  Sometimes your Windows Update service can get in a weird state and rebooting the server will allow Windows Update to successfully download and install the needed patches.
  2. Retry Windows Update.  This is especially true if you are going directly to Windows Update to get your updates.  If there are a large number of updates that your server needs, and/or the Windows Update Servers are very busy at the time, this error can indicate a timeout.  Waiting five to ten minutes between tries may clear the error.
    1. NOTE:  If you have numerous servers/computers in your network, I strongly recommend against using the Windows Update Servers.  You will save bandwidth and resources by implementing Windows Server Update Services (WSUS) on your network.  Additionally you can monitor and manage all of your servers in one place and use the builtin WSUS reporting to easily generate reports on the status of patches across your entire network.
  3. Update your Windows Update Client.  Last October, Microsoft released a new Windows Update Client that addresses some issues that can cause error 8007000E to be thrown.  You can get the updated client from Microsoft KB3083710.
    1. If you are running Windows 2012 R2, there is also an updated client at Microsoft KB3083711.

One of the three steps above is likely to resolve any issues you are encountering with Windows Update error 8007000E.  If not, be sure to review your WindowsUpdate.log file located in the root of your /Windows/ folder.