WSUS Product Team Blog

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

Update on svchost/msi performance issue and 3.0 Client distribution plan

Update on svchost/msi performance issue and 3.0 Client distribution plan

  • Comments 269
  • Likes

Hi Folks

In addition to the next week’s  WSUS 3.0 release, we are making the new client portion available via the following plan to our customers who continue to experience performance issues like UI hang and long scan times.

 The new WUA client addresses these issues with deep architectural performance optimizations.  Combining the installation of the new client, with the latest MSI fix available in KB927891 available on Microsoft Download Center, will completely address the what we have fondly called the svchost/msi issue.  It’s important to keep in mind that the new client is only a partial solution and clients must have both KB927891 and the new 3.0 client installed for a full solution.

 On May 1st,  a standalone version of the client will also be made available to those of you who need to address this performance issue now.  Although this will be immediately available, it  will have to be independently distribute.   Instructions on how to get this standalone new 3.0 client version are available at - http://msdn2.microsoft.com/en-us/library/aa387285.aspx

 On  May 22nd. The following WSUS 3.0 full and client only updates will be available to WSUS:

Keep in mind that the new client is only a partial solution for the svchost/msi issue and clients must have both KB927891 and the new 3.0 client installed for a full solution. 

 ·         A critical update for WSUS 2.0 SP1 which contains the WSUS 3.0 client self update tree.  This critical update, applicable to WSUS 2.0 SP1 Server, if approved will install a new client self update versioned tree on the server.  When mapped clients check in with this updated WSUS 2.0 SP1 server, their clients will check their version against that installed on the server, see that they no longer have the latest version, and immediately self update to 3.0 versions.   The server will remain a 2.0 version with the capability to support the 3.0 clients.

  •  For SBS R2 WSUS 2.0 servers, another  critical update will be made available which will when approved, upgrade the R2 servers to WSUS 3.0.  Subsequent  to upgrade, the former 2.0 clients will self update to version 3.0. 
  • For all other servers running WSUS 2.0 (including SBS servers OTHER than R2) we will also be offering a WSUS 3.0 recommended update.   This update, when approved on servers running WSUS 2.0 will upgrade to 3.0, and as with the critical update, cause mapped clients at first check-in with the newly updated server, to self update to 3.0.
  •  For SBS non R2 customers, both of these updates will be available for your approval depending on the update scenario, and or client update path you wish to pursue. 

 We appreciate your patience while we pushed to make these architectural improvements to the client, and find a way to make them available in a variety of ways to suit your upgrade plans as well as your immediate needs.

Thank you the WSUS v3 team

 Update on 5/15: Based on the comments here, a follow-up entry blog entry has been posted @ http://blogs.technet.com/wsus/archive/2007/05/15/srvhost-msi-issue-follow-up.aspx

Please refer to that post for clarifications on expectations after 3.0 client and KB927891 fixes are installed. Please use that post for more feedback.

 

 

Comments
  • WSUS Product Team Blog : Update on svchost/msi performance issue and 3.0 Client distribution plan: http

  • Any new for resolving the issue for MU too ?

  • The new WSUS 3.0 server is due for release next week, which is good news for administrators everywhere

  • Will this also fix the memory leak in the svchost instance hosting automatic updates? One of my SBS R2 boxes needs rebooting every few days due to memory usage growing in this svchost instance, unless I disable the automatic updates service. Thanks.

  • is the mis update KB927891 going to be made available through WSUS 3.0 or WSUS 2.0???

  • is the msi update KB927891 going to be made available through WSUS 3.0 or WSUS 2.0???

  • Anthony: The memory leak is fixed in the MSI update, referenced by KB 927891.

    Andy: The MSI update should go out over WU and MU in late May or early June.

  • "Keep in mind that the new client is only a partial solution for the svchost/msi issue and clients must have both KB927891 and the new 3.0 client installed for a full solution.  "

    I am running WSUS 2.0.

    Can we rollout KB927891 to all clients, regardless of whether they are experiencing issues? (along with the 3.0 client when it gets released). I have a large network and don't know who does/doesn't have the svchost.exe issue.

  • John: Is a more specific release date for KB927891 to WU/MU available?

  • Kurzbeschreibung: Neue Version des Windows Update Clients für Microsoft Update, Windows Update und Auto Update. Aktuell: Ja (Direktdownload der Standalone-Version - wird nach und nach auch über Windows Update angeboten bzw. direkt installiert) Enthä

  • We as many others have same issue and have been forced to turn off AU service due to svchost high cpu utilization for long period of time. But what is the best way to turn AU on clients again on and not being hit again from that svchost? Is any updated version of client available as part of update or do we have to go from computer to computer and use some partial hot fixes?

  • Tuesday, May 01, 2007 1:31 AM by No-one

    "Can we rollout KB927891 to all clients, regardless of whether they are experiencing issues? (along with the 3.0 client when it gets released). I have a large network and don't know who does/doesn't have the svchost.exe issue."

    --

    I would like an answer to this as well as I am in the same situation.

  • Can we get KB927891 posted on the catalog update site so we can import it into WSUS 3.0? I thought hotfixes were supposed to be available on the catalog site?

  • MU catalog has not released. It is still in beta and doesnt contain any hotfixes. Hence KB927891 can not be imported to WSUS at this time.

    You will have to wait for KB927891 to be released as a patch through WU which is expected to happen in late May or early June as per a prev comment.

  • Your blog says that the updated client will be available on May 1/07 through either the xml file on the MSDN page or through the MS Download site.  Has this date changed as I cannot find a link to the new client in either location.

    Is it possible to extract the client from the WSUS 3.0 installation files?  If so, how would one go about this.  I'm temped to install WSUS 3.0 in a test VM just to get the WSUS 3.0 client.

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