WSUS Product Team Blog

WSUS Product Team thoughts, information, tips and tricks and beyond :-)

WSUS 3.0 SP2 RTM is now available!

WSUS 3.0 SP2 RTM is now available!

  • Comments 59
  • Likes

The WSUS Product Team is proud to announce that WSUS 3.0 SP2 is now available! Get it today!


We recommend installing SP2 on all existing and new installations of WSUS.


WSUS 3.0 SP2 supports the latest operating systems including Windows Server® 2008 R2 and Windows 7 clients. WSUS 3.0 SP2 is more robust and features significant improvements in client performance, reliability, and increased server usability and reliability.

Administrators will see improvements in several areas including:


·       New Update and Computer Status reports provide the ability to report on only the updates you’ve approved for installation. You can run these reports from the WSUS console or use the API to incorporate this functionality into your own reports.

Auto-Approval Rules

·       Auto-approval rules now include the ability to specify the installation deadline date and time for all computers or specific computer groups.

Update Files and Languages

·       Improved handling of language selection for downstream servers includes a new warning dialog that appears when you decide to download updates only for specified languages.

Easy Upgrade

·       WSUS 3.0 SP2 can be installed as an in-place upgrade from earlier versions of WSUS and will preserve all of your settings and approvals. The user interface is compatible between WSUS 3.0 SP1 and SP2 on the client and the server.

Software Updates

·       Stability and reliability fixes for the WSUS server, such as support for IPV6 addresses.

·       The approval dialog now sorts computer groups alphabetically by group name.

·       Computer status report sorting icons are now functional in x64 environments.

·     A new release of Windows Update Agent is included with WSUS 3.0 SP2 that provides improvements in reliability and faster client scan times, the ability to perform ‘scoped’ scans, improved update organization, more clarity on update value and behavior, plus improved display of imaged machines.

Operating Systems Supported by WSUS 3.0 SP2


·       Windows Server 2008 R2

·       Windows Server 2008 SP1 or later

·       Windows Server 2003 SP2 or later


·       Windows 7 client

·       Windows Server 2008 R2

·       Windows Server 2008 SP1 or later

·       Windows Server 2003 SP2 or later

·       Windows Vista

·       Windows XP Professional

·       Windows XP Professional SP1

·       Windows XP Professional SP2

·       Windows XP Professional SP3 or later

·       Windows 2000 SP4


For more information about WSUS 3.0 SP2 including documentation and download instructions, see:


1.       Windows Server Update Services 3.0 SP2 Dynamic Installer for Server Manager (KB972493)

2.       Windows Server Update Services 3.0 SP2 (KB972455)

Additional information

For more information about this release visit us at our Windows Server Update Services page.


The Product Team would like to thank you for your support throughout Beta and RC of this release. Thank you for making WSUS a better product!



Cecilia Cole



  • wsus sp2 dont work via ntlm proxy...wsus sp1 work normal...

  • This broke my WSUS SP1!!!FOOOOOKK!!!

  • Why is it so slow? I run it on Athlon X2 2.5Ghz with 8GB of ram on windows 2008 R2 and the performance is a disaster. Clicking through updates takes forever, clicking through any options takes forever. I'm trying to approve or deny an update and it takes way too long. Do something about that.

  • WSUS 3.0 SP2 is only updating Windows 2kx, Vista and Win7, WinXP is not listed as supported platform for the KB972455 update on the WSUS server.

    The manual update works just fine, without problems.

    Anyway to correct the supported platforms to include WinXP?

    Thanks in advance,


  • WSUS 3 SP1 in W2003 Broken

    2009-09-03 17:14:43  Error     MWUSSetup          InstallWsus: MWUS Installation Failed (Error 0x80070643)

    2009-09-03 17:14:43  Error     MWUSSetup          CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643)

    2009-09-03 17:14:43  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643)

    2009-09-03 17:18:12  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643)

    any idea?

  • Installation on SBS2003R2 failed (unable to create network Share was the message on screen but log reads:

    2009-09-04 11:07:04  Success   CustomActions.Dll  CopyADMFile:The system locale ENA is not supported. Using English...

    2009-09-04 11:13:54  Error     MWUSSetup          InstallWsus: MWUS Installation Failed (Error 0x80070643: Fatal error during installation.)

    2009-09-04 11:13:54  Error     MWUSSetup          CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643: Fatal error during installation.)

    2009-09-04 11:13:54  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)

    2009-09-04 11:14:56  Error     MWUSSetup          CWatsonHelper::Init: Failed to load WER library. (Error 0x8007007E: The specified module could not be found.)

    2009-09-04 11:14:56  Error     MWUSSetup          CSetupDriver::ReportFailure: Failed to initalize the CWatsonHelper.  This is expected on pre-Vista machines. (Error 0x80004005: Unspecified error)

    2009-09-04 11:14:56  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)

  • this maybe helpful:

    cd \windows\system32

    lodctr /R

    it worked with 'WSUS 3 SP1 in W2003 Broken'

  • Thanks,

    The install worked fine.

    As there are no updates pending I'm unable to thest WSUS but all seems good.

    Sorry if I created a double post.

  • The upgrade went fine for me on our main server. I haven't done our downstream servers yet.

    New 'Approved patches only' reports doesn't let you select multiple computer groups like the other reports do. You can only select one group at a time. If the patch isn't approved at that specific group level then it doesn't show up on the report. If you select the All Computers group then only patches specifically approved for All Computers will display. Any thing approved only at sub group levels won't show up. This is uselsess for us.

    Also, the client agent upgrade can't be managed. All clients get it automatically. We haven't had any issues with it but not a smart design.

  • Does it support Vista with SP2 installed?

  • The addition of computer tabular reporting for approved updates was a great idea.  I have noticed a problem, which may be intentional?  We run a "Servers" group with several sub groups, one of which being "Testing".  When I release patches to only the testing group, they do not show up if I run a tabular report for the "Servers" group with "Include child groups" checked.  They only show up if I run the tabular report on the testing group alone.  They will show up however if approved to all server groups, and not just one.  Was this designed on purpose, or possibly a flaw?  Thanks.

  • How come the new version does not support Windows Server 2003 R2 by itself or with a service pack and neither does the client version of the software. If I missed something sorry, but just trying to figure it out.

  • Even a link here or in the console to the report viewer would be nice.  So far as I can tell so far, SP2 is just a breaking update.  What more would one expect from WSUS?  Updates?  Apparently not.  Now I will be looking for the report viewer download.

  • Can you tell me if this phrase:

    "plus improved display of imaged machines"

    means that multiple computers all having the same SUSClientID registry entry due to being imaged after reporting to the WSUS server will now show up as separate PCs in the list in the WSUS console?

    I do hope so, because I could never understand the behaviour in v3.0 and v3.0SP1 where WSUS treats all the PCs as one despite them having different hostnames.

  • WSUS 3.0 has several issues that are shortcomings in design from this user's perspective.

    1) Status reports opened from Search dialog do not produce the same report as the ones opened from the main MMC window.  (Search for a KB number of interest and open one of the hits.  Note that page 2 of the report lacks the list of computers that need the updates.  Compare with the status report opened from the MMC window (if you can find the update in the All Updates list...))

    2) "Wait" indications from Report 2008 software are few and far between.  Sometimes the status line of the MMC window show some progress indication.  In the case of the Search dialog the greyed Find button is the only "indication"

    anything is happening.

    3) Summary pages are not so useful.  Sure the per computer or update summary info is very good, but the MMC list of computers in a group really only contains the names of the systems.  The other columns are nearly useful.  Compare with SUS and WSUS 2.0.

    4) Responsiveness of the total interface really suffers from use of the Report 2008 package.  For example, the change of approval for an update should be reflected in the window with the link used to change the approval.  Having to

    hit the menu item "Run Report" to see the change is worse than using a browser or CLI to do this work.  Why is the interaction of UIs devolving to wooden behaviors?  I'd rather see the return of CURSES terminal interfaces...

    5) Would it be so awful to have ctrl-f search the central scrolling pane info in the MMC window?

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment