Old WSUS Issues

Show Menu

This page contains a a list of issues that were found with beta versions of WSUS (divided in to server, client and content issues). This is being kept for now as a separate page to Known WSUS Issues, with the idea that this list should eventually go away.

Here are the known issues with WSUS RC

Server

Synchronization Errors with WSUS Replica/Master in Different Timezones: A replica WSUS server is unable to synchronize from a master server if they are in different time zones.
Error Adding Updates to the Database: Synchronization of the WSUS server fails.
System Out Of Memory Exception: The WSUS installation fails with an out of memory exception.
Flaw in Print Status Report: In some cases, the Print Status Report from the WSUSAdmin interface does not render the entire contents.
Server Error In '/WSUSAdmin' Application: After installing you can't even open the WSUS Admin page.
Content File Download Failed: In some cases, download fails due to access control issues or if the server does not support the necessary HTTP protocol.
Error in WSUS Documentation: Microsoft documentation incorrectly states that the "UseWUServer" REG_DWORD Value is obsolete.
Compiler Error Message CS0016: Could not write to output file. Compiler Error Message while accessing the WSUS admin page.
SqlDateTime overflow: Windows Server Update Services encountered an error taking reports for computers.
Encryptionkey cannot be retrieved: You see error message when when trying to make changes to the synchronization options.
SelfUpdate Tree is not working: Clients may not be able to update to the latest WUS client software and communicate with the WUS Server.
Flaw in Forced Un-Install of WUS Beta: It turns out that the 'Forced Un-Install' of the WUS beta initiated by the WSUS RC is flawed. You need to Uninstall WUS Beta 2 & Install WSUS RC.
Column Widths In Table Grids: In the WSUS Admin web application, column widths in table grids (e.g. on Updates or Computers report pages) cannot be resized. This is a known issue, and has been postponed for future consideration. The work around is to just resize the entire window.
All Languages Are Specified By Default For Download: This is a known issue and has been postponed for future consideration. The work around is to specify the languages you require before synchronising the first time.
WSUS Downloads Some Non English: Despite specifiying English only, it downloads updates for different langauges. This is a known issue with the metadata coding of the updates (as opposed to a bug in WSUS itself).
Backend Installation Fails With Invalid Drive: If the drive specified in the CONTENT_DIR command line installation parameter is not present on the backend machine or does not map to a disk drive, the installation will fail with either "Invalid drive" or "WsusContent is not a valid short file name".

Client

Clientdiag.exe fails - "Class Not Registered" error: In some cases, the client diagnostic (Clientdiag.exe) can fail with a "Class not registered" error.
The Automatic Updates service terminated: The Automatic Updates service terminated with the following error: The class is configured to run as a security id different from the caller.
Agent Failed Detecting with reason 0x8024400d: The problem may be related to your clients being unable to collect all the computer information for registration.
Unknown Status: The client seems to be having trouble accessing the computer information using WMI which is preventing the client from updating its OS information on the server.
SOAP Fault 0x00012c: You see this error in WindowsUpdate.log while the AU client is communicating with WSUS RC.
Flaw in the Client Diagnostic Tool: Client Diag Tool does not check for the "UseWUServer" value. If you have "UseWUServer" value disabled then AU Client might go to windowsupdate.com rather than your local WSUS Server.

Content

PC halts while setup of "Windows Installer 3.1 beta": This is a known issue and it occurs on XP with a very small race condition.

Here are Beta 2 issues that are not yet confirmed as fixed.

If you can confirm it then move the text to the section below and remove the hyperlink from the text and delete the page.

BUG in installing WUS B2 on Windows 2000 Domain Controller with SP4. For more information, see WUS B2 on W2k SP4 Domain Controlers.
WUS B2 UI does not render if IIS lockdown is installed. For more information, see IIS Lockdown And WSUS.
WUS B2 server generates Event ID 30, Event source W3CSVC, and with the description: "The server was unable to read the file c:\Program Files\Update Services\Administration\Errors\AccessDenied.htm.". See Event 30 from W3SCV

Here are Beta 2 issues that were fixed in RC:

WUS B2 fails to download content into D drive.
Computer Status page impropoperly gives the error "Element already exits".
The WUS B2 documentation incorrectly states that MDAC does not need to be installed before WUS is installed - on Windows 2003 Servers the installation is now part of WSUS installation.
Error on installing WUS B2 on Windows 2000 with default SQL instance.
Some systems show up with much of the inventory as 'unknown'. This is a known issue if your client machine's BIOS informaiton is longer than 64 characters. This will be fixed at the next release. To confirm this on your system, run the "sysinfo" utility, and check the length of the BIOS string.
Synchronisation between the WUS B2 server and the MS Server can fail. This is due to a known issue with authentication and a fix is planned for the RC.

Last Modified 7/17/05 5:04 AM