WSUS Error Codes

Summary

WSUS error codes tell you nothing about the problem; this page lists errors I have encountered, what they mean and how to resolve them.

80072ee2

Problem: The client is unable to connect to the WSUS server to download updates and the connection attempt times out.

Resolution: Find the reason why WSUS is unavailable from the client. Check the name of the WSUS server configured in the registry;  HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

Try pinging the host name to confirm it’s reachable. With mine the WSUS VM had paused due to critical disk space issues.

8024500c

Error: A client (Windows 8.1) cannot connect to the online Windows Updates link in Control Panel.

Problem: The client has been configured to use WSUS, but is blocked when attempting to reach the online Windows Updates

Resolution: 
Open registry editor (Start menu –> Run –> regedit)
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
Chage the value of the UseWUServer from 1 to 0
Restart Windows Update service

C8000710

Error: Windows Update encountered an unknown error

Problem: The OS drive is full.

Resolution: Free disk space

 

C80070643

Error: Installation Failure: Windows failed to install the following update with error 0x80070643

Problem:  SoftwareDistribution folder is corrupt

Resolution: Stop Windows Update service, rename C:\Windows\SoftwareDistribution to  C:\Windows\SoftwareDistributionOLD. Restart Windows Update Service (this creates a new C:\Windows\SoftwareDistribution folder). Rerun the check for updates and install.

 

800B0001 – Fix #1

Error: Windows Update or Microsoft Update cannot determine the cryptographic service provider

Problem: Running both dism /online /cleanup-image /scanhealth followed by dism /online /cleanup-image /checkhealth reports the “CSI Payload Corrupt

Resolution: Run the following in an elevated command prompt:

dism /online /cleanup-image /analyzecomponentstore
net stop wuauserv
net stop cryptsvc
net start wuauserv
net start cryptsvc
dism /online /Cleanup-Image /StartComponentCleanup
dism /online /cleanup-image /startcomponentcleanup /resetbase
sfc /scannow
dism /Online /Cleanup-Image /RestoreHealth
sfc /scannow
wuauclt /resetauthorization /detectnow

The open WSUS client and rescan for updates.

800B0001 – Fix #2

Problem: If the above doesn’t work then the error can also be caused if your Windows 8 clients previously received updates from a Windows Server 2012 WSUS implementation (WSUS version 6.3) but now receive updates from a Windows Server 2008 R2 WSUS instance (WSUS version 3.2). The WSUS client on the 8.1 instance would now be incompatible with WSUS 3.2.

Resolution: On the Windows Server 2008 R2 WSUS server install the following update: http://support.microsoft.com/kb/2734608 . Allow the install to complete then run a new synchronisation, once complete Check for Updates again on the client.

Disclaimer: provided “AS IS” with no warranties and confer no rights