Common WSUS Errors Codes

Show Menu

Common WSUS Error Codes

These errors will be displayed in the client computer's log. The log is located at %windir%\windowsupdate.log

0x8007f02b - This error means there is not enough disk space for WSUS to create the Uninstall files. You need to clean up your system drive.
0x8007f003 - This error means there is not enough disk space for WSUS to create the Uninstall files. You need to clean up your system drive.
0x80072F8F- This error relates to WSUS configured with SSL. Ensure that the server is connecting to a certificate subject name. You can also type the https address into Internet Explorer and look for error messages relating to the certificate- if a certificate error is displayed, clients will not sync.
0x8007F004-This is a user rights issue. If a user has administrative rights, but is not listed, or a member of a group listed under the “Manage Auditing and Security Log” right in the security policy- then any patch that writes to the event log will fail with this error code.
0x80072EFD-This error relates to WSUS configured with SSL. Validate the certificate chains on the server and ensure the WSUS server’s certificate is trusted. Also, ensure FIPS-140 compliant algorithms are disabled on the WSUS server, as they do not appear to be supported by the WU clients.
0x8024400D- There are several known fixes for this problem.
- Run this command in a command prompt: wuauclt /detectnow /resetauthorizations
- This may indicate some stored files are out of date. Stop the Automatic Updates Service. Delete all files in "C:\Windows\SoftwareDistribution\DataStore" and "C:\Windows\SoftwareDistribution\Download" directories. Start the Automatic updates service. Force a Detection Cycle.
- This may indicate a problem with WMI. Stop the Windows Management Instrumentation service. Delete the Repository folder from: C:\WINNT\SYSTEM32\WBEM. Restart the WMI service. Force a detection cycle.
0x80244018- This usually means a problem with a proxy server passing credentials. Check the proxy settings.

0x8024402c- This is usually associated with a Firewall, Anti-Virus Product, or a client based Intrusion Prevention product blocking portions of the AU client

0x80072AFC- This appears to be a DnldMgr error. Check the log and ensure that the DNS name used by the WU client is the location DnldMgr is attempting to download from. Clients will not download updates, though they will report correctly to the WSUS server. You may have to clear the software distribution folder to remove any cached information or downloads.

Note for Highly Advanced Administrators: When securing IIS on the WSUS server, do NOT set the “UseHostName” property unless the FQDN (ex servername.domain.com) matches the DNS name (ex. Wsusserver.domain.com) used by the clients to access the server. The DnldMgr does not use the WU Client registry information on the machine, instead it pulls the location of the “Content” directory from IIS, if the UseHostName property exists- it may use any IP visible to IIS (if set to false), or the FQDN instead of the DNS. (If set to true)

#Launching old AU client- If you get this in the log, with no other errors check the registry for the SusServerVersion key. If it exists, delete it and force a detection cycle. The existence of this key forces a client to use the SUS client rather than the WSUS client.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update

"SusServerVersion" = REG_DWORD: 0x00000001 (1)

You should also checkout the following page as it has a list of error codes and what they mean.
http://inetexplorer.mvps.org/archive/windows_update_codes.htm

Last Modified 11/19/08 8:51 AM