I am pleased to announce that, as of today, a fix for this issue is available from Microsoft for WSUS 3.x, in addition to the Windows Server 2012 update that we published last week.
WSUS 3.x ships back to Windows Server 2003 R2, and ships in x86 and 64-bit versions. This requires additional testing above and beyond what we did for Windows Server 2012, which applies only to that OS and is for 64-bit only. Additionally, the packaging format for Windows Server 2012 is different from what we must use for downlevel OS versions.
An article describing how to get this update is available at:
- http://support.microsoft.com/kb/2819484 if you are running Windows Server 2012
- http://support.microsoft.com/kb/2828185 if you are running WSUS 3.0 SP2 (WSUS 3.2) on Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2 (Direct link to download: http://www.microsoft.com/en-us/download/details.aspx?id=38429)
Please see my last blog post for more engineering details about why this problem happened in the first place and what decisions we made to try to make this update as bulletproof as possible. This update supersedes and replaces all existing updates for WSUS 3.x and all users of WSUS 3.x should install this hotfix as soon as possible. WSUS 3 SP2 must be installed before you install this update.
Also, I just wanted to take this opportunity to reiterate that all versions of WSUS prior to WSUS 3.0 SP2 are no longer being maintained or supported. WSUS 3.0 SP2 is a free download from the Microsoft Download Center, and any customers using older versions of WSUS should install both WSUS 3.0 SP2 and this hotfix as soon as possible.
Thanks,
The WSUS Team