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:
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 rolls up and includes all updates to WSUS 3.2, including KB2734608. 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
KB 2828185 doesn't mention supporting Windows Server 2003 Service Pack 2 (32-bit x86), only the 64 bit. Will there be a separate update for the 32 bit?
The 32-bit download is here www.microsoft.com/.../details.aspx
I have a only semi related question. Will the WU client get upgraded with improved error messaging so troubleshooting a machine with a non functioning WU client will be easier.
This morning I tried to run the update package from this website www.microsoft.com/.../details.aspx that you all posted on 4/16/2013 on my Windows Server 2003 SP2 64-bit WSUS 3.0 SP2 and I recieved this error message:
"An error occurred during the installation of assembly. Microsoft.UpdateServices.Utils,fileVersion="3.1.7600.262" ,version="3.1.6001.001" ,culture="neutral" ,publicKeyToken="31BF3856AD364E35" ,processorArchitecture="MSIL". Please refer to Help and support for more information. HRESULT: 0x80070020.
Do you have any idea, why I am recieving this error message? Thank you.
Unfortunately, Windows Server 2003 SP2 is no longer supported under mainstream support. This update will only work on Windows Server 2003 R2 and later. If you have an extended support contract with Microsoft for Windows Server 2003, you should contact Support and they will work with us (the product group) to see if we can make an update privately available.
Note: Windows Server 2003 R2 is also no longer supported under mainstream support, but the update happens to work with Windows Server 2003 R2, so you can apply this KB to Windows Server 2003 R2 anyway.
Please see support.microsoft.com/.../lifepolicy for the product lifecycle policy.
Thank you for your reply Ben. I'm sorry for my typo, we do have Windows Server 2003 R2 Standard x64 Edition. I notice that when I tried to run the update package our McAfee HIPS Alert message popped up and then afterwards the download failed. I'm going to run the upgrade package again but first turning HIPS off and hopefully that will fix my problem. I also downloaded the upgrade package on our Windows Server 2008 R2 test box without McAfee installed and it installed just fine. Thank you.
@Typhoon87, I can't speak for the WU client, it's a different team altogether. Sorry!
Ben thank you for answering my first question.
I have another after applying this update does the build number of WSUS in the console change.
Any reason why this fix does not appear in WSUS itself? Or has it just not been pushed to WSUS?
Also, should this be installed on workstations that have the administrative console only installed?
One more question.
When WSUS adds a new product or catagory is there a way to have it be a diffrent color in the Products and Calssifications window for the first couple of weeks so that Admins can tell which are new?
^Yes please! It's very annoying to see "new product added" and not know what was added!
"Note: Windows Server 2003 R2 is also no longer supported under mainstream support, but the update happens to work with Windows Server 2003 R2, so you can apply this KB to Windows Server 2003 R2 anyway."
The update fails to install on Windows Server 2003 R2 - at least it did on my 64 bit server. Same error as mentioned above in Ruffin's post.
Guess it's time for me to upgrade to 2K8 or 2K12.
Thanks for the reply.
If you are not having luck on WS2003 R2, try installing .NET 4.0 before installing the hotfix.
I am receiving the same error: "An error occurred during the installation of assembly. Microsoft.UpdateServices.Utils,fileVersion="3.1.7600.262" ,version="3.1.6001.001" ,culture="neutral" ,publicKeyToken="31BF3856AD364E35" ,processorArchitecture="MSIL". Please refer to Help and support for more information. HRESULT: 0x80070020.
I am running Server 2008 x64, WSUS 3.0 SP2 and DotNet4
What can be causing this error?