共用方式為

Svchost /MSI issue follow up:

  • 發行項

Hi Folks –

 

Just want to make sure you know we are actively following up on the comments posted on the svchost/msi issue. We are working on reproducing the reported performance issues on various systems in our labs. We will keep you posted as to the findings.

 

I also want to provide some clarification with install instructions for both the new client and the MSI fix, as well as upcoming available automatic distribution options, and the performance expectations after the MSI fix and new client are installed.

Build 0374 AU client/ WSUS 3.0 client:

While we are engaged in a world-wide deployment of the new AU client (build .0374), this staged deployment is occurring in a wave which we expect to complete by early June. This means that for AU users, the new client bits will just automatically self update when visiting the site before mid –June, and for WSUS users, you will be able to download the bits after 5/22/2007 (or upgrade to WSUS 3.0 now).

 

To make the client available earlier vs. waiting for the duration of the world-wide roll-out, we released the client in a ‘stand-alone’ form which you can download from the Download Center now. The version of the client is 0374 – and can be installed directly from:

 

https://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x86.exe

https://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x64.exe

https://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-ia64.exe

 

Further instructions can be found in https://msdn2.microsoft.com/en-us/library/aa387285.aspx

Please verify on your systems, the client version here is: <windows dir>\system32\wuaueng.dll is 7.0.6000.374

 

KB927891/MSI fix:

To make sure you have the latest MSI fix in KB927891, make sure your MSI.dll binary version for supported platforms are exactly as documented under files in:

https://support.microsoft.com/kb/927891 .

This MSI fix will be available via MU/WU (and there by WSUS) by late May early June.

 

Expected results: It’s important to note that with the MSI fix and the new client installed, the CPU may still go near 100%, but the system should still be responsive and not lock up. If another task requires CPU cycles they will be shared, but if the system is idle, MSI will use the full cycles available. If a task is running at the same time as MSI, the system may be slightly slower, but should still be responsive during this time. Key to remember the MSI fix and the new client address unresponsive or locked systems. CPU spikes during some scans are expected, machine unresponsiveness is not. If your watching the process monitor, you will still see 100% CPU during some scans and this is expected behavior.

 

Next steps for problem systems:

If, after checking these installations, and reviewing expected behavior, iyou are still experiencing this issue and have a system which we can remote into, or obtain logs from, for further investigation, please contact me directly at bobbieh@microsoft.com. The windowsupdate.log from the system experiencing the performance issue would be helpful information as well as full system description of hardware, platform and additional programs installed and running.

 

Thank you,

Bobbie Harder

PM, WSUS CPE

Comments

  • Anonymous
    January 01, 2003
    Its not often that my work PC (running Windows XP service pack 2) starts to misbehave, but recently I&#39;ve

  • Anonymous
    January 01, 2003
    Ok there have been so many questions about these updates that I decided that I should contact my TAM

  • Anonymous
    January 01, 2003
    For those keeping score, there&#39;s a graffiti&#39;d version of the Green Check back on the blog. It

  • Anonymous
    January 01, 2003
    Hi Folks In addition to the next week’s WSUS 3.0 release, we are making the new client portion available

  • Anonymous
    January 01, 2003
    Многие пользователи WSUS помнят, я полагаю, проблему с обновлениями Office через него – процессор загружается...

  • Anonymous
    January 01, 2003
    Многие пользователи WSUS помнят, я полагаю, проблему с обновлениями Office через него – процессор загружается...

  • Anonymous
    January 01, 2003
    So anyone who regularly checks Microsoft Update with Office installed has been living in pain for the

  • Anonymous
    January 01, 2003
    Microsoft released updated versions of Windows Installer 3.1 to fix a problem that could cause Windows

  • Anonymous
    January 01, 2003
    http://www.oyunim.com http://www.oyunulkesi.net http://www.bizimmekan.com Thanks for the its much appreciated harika

  • Anonymous
    January 01, 2003
    http://blogs.technet.com/wsus/archive/2007/05/15/srvhost-msi-issue-follow-up.aspx Once again I&#39;ll

  • Anonymous
    January 01, 2003
    KB927891 is being updated currently. The binary versions are: 3.1.4000.4042 – WS03 x86 and 64  SP1and SP2 3.1.4000.4039 – XPSP2

  • Anonymous
    January 01, 2003
    Some users are having issues with svchost.exe / msi. The Hotfix+WSUS 3.0 works to some users (see here

  • Anonymous
    January 01, 2003
    New version of WUA 3.0 redist on the way? I've just received version 7.0.6000.381 via Windows/Microsoft Update (after applying the new Microsoft Update Catalog control). Bye, Freudi

  • Anonymous
    January 01, 2003
    Ok there have been so many questions about these updates that I decided that I should contact my TAM

  • Anonymous
    May 15, 2007
    Has anyone at Microsoft actually READ kb927891 recently? ALL the information in that kb article is out of date: file date, file time, version number, release date, are all wrong. The kb article refers to version TWO, which is obsolete. The current file on Microsoft's servers is version THREE and is dated Mon, 23 Apr 2007. How can I check the correct version of msi.dll if Microsoft's own kb is incorrect? James

  • Anonymous
    May 15, 2007
    In regards to James_A's post, we have the additional problem that we had already previously downloaded and deployed the -public- KB927891-v2.  Now, with KB927891-v3, how are we supposed to verify installation?  Add/Remove programs shows the old version installed, and HKLMSoftwareMicrosoftUpdatesWindows XPSP3KB927891 does not show the updated filelist information for the v3 update.  It still shows the v2 info even though the actual files do seem to be updated.

  • Anonymous
    May 15, 2007
    Hello, I have a question, whats wrong with WUA, We patch at our company about 2000 clients with SMS. What we found out is following: If we patch a client with only installed XP OS + SP2 (MUI) it takes for about 63 patches 25min If we patch a client that has installed XP OS + SP" (MUI + Office 2003 + SP2 (MUI) than the patch time goes up to 2 hours. Whats wrong with WUA used by ITMUv3 We have WUAv3 + Hotfix  KB927891v3 + SMS (SP3) installed the only thing with the new ITMU fixes is now, that the computer stays responsive, this is good, but what happens to the time?

  • Anonymous
    May 16, 2007
    Hi everybody... I'm an italian Help Desk Technician. I have these problems about svchost issue. I try to fix using wuaueng.dll (7.0.6000.374) and KB927891 (v3) in windows XP client syncronized with a WSUS 2.0 installed in a Windows 2003 Server SP2. The response is the same:

Expected results:  It’s important to note that with the MSI fix and the new client installed,  the CPU may still go near 100%, but the system should still be responsive and not lock up.

But the fix is not working with Windows 2000 Prof. SP4 RollUp Client? Can you help me? Thanks Alfio

  • Anonymous
    May 16, 2007
    Judging by the newsgroups, the problem with long update scan times is related to the presence of Office 2003, rather than any other version of Office, just as Robert reports above. It has also been suggested that the size of the DataStore.edb file might be a factor - can anyone confirm this?  What is a reasonable size for this file on a fully patched XP SP2 plus Office 2003 system?  I have one PC with a DataStore.edb file which is over 49MB in size - is this reasonable, or bloated? It is not clear whether the patches being suggested in this blog entry address either of these particular issues (Office 2003, size of DataStore.edb), or whether they are just general speed-ups.

  • Anonymous
    May 16, 2007
    I ran into this problem yesterday at a client. I found a great resource and wanted to pass it on. http://swigartconsulting.blogs.com/tech_blender/2006/07/windows_update_.html

  • Anonymous
    May 16, 2007
    The comment has been removed

  • Anonymous
    May 16, 2007
    Jeff, Sorry for my previous comment. I meant to call you a DUFUS!!!! hahahahhahaha

  • Anonymous
    May 16, 2007
    Microsoft released Xbox Elite with HDMI. SWEET!

  • Anonymous
    May 16, 2007
    IBM T43 system rebuild, w/ Office 2003, using Microsoft Update caused this.  Installed patch  KB927891 with no improvements. Solution that worked for me:   1- Go to Microsoft Update and under Change Setting, Disable Microsfot Update software. 2- Update Windows through Windows Update 3- Update Office through Office Update (multiple passes) 4- Reboot (not sure if necessary) 5- Activate Microsoft Update upgrade through Windows Update site 6- Works now, less than 3 minutes at mostly 100% CPU for update checks.   Before it would just hang the machine totally.

  • Anonymous
    May 16, 2007
    The comment has been removed

  • Anonymous
    May 17, 2007
    what a constructive comment...

  • Anonymous
    May 17, 2007
    YOU'RE A GEEK!!! ahahahhahahahahahahhaha ahahahahahhahaha hahahah ahah hah!

  • Anonymous
    May 17, 2007
    Once again notice the dancing, this is the "Windows Update" client not Microsoft update client, also note it does not fix the problem it just keeps your machine from locking up. It still causes 99% CPU utilization. It's still not an acceptable fix IMO. Jason

  • Anonymous
    May 18, 2007
    Yeah sounds to me that MS is trying to hose XP to make Vista look better. IMHO.

  • Anonymous
    May 18, 2007
    Aye, this problem hasn't stopped for me, has anyone tested stopping the WSUS from actually looking for Office updates?

  • Anonymous
    May 18, 2007
    How did Microsoft break this in the first place?  I have been dealing with this issue for several months now on 500+ machines.  I have ran every patch known to man, and the only way I was able to find any solution to the problem was by going into services.msc and setting the startup type to manual.  With comments such as "it will still run at 100% capacity" how is this an exceptable answer to the problem?  Upon running the new version of 927891 and a reboot, the machine I was testing completely locked up.  It is difficult to be patience when you have users every day on brand new machines, telling you that it is slow as anything, and the techs actually hope it is spyware.  One basically has to choose between Windows Updates or a functional PC.  

  • Anonymous
    May 18, 2007
    Thanks Gerhard. Your simple solution fixed my svchost 100% issue (stand alone pc). Simple to do. I rebooted after re-activating Microsoft Update just to be sure and I did not encounter a svchost issue. Scott

  • Anonymous
    May 22, 2007
    My WSUS just brought down the KB927891 patch.  Haven't seen the WSUS 3.0 client yet.

  • Anonymous
    May 22, 2007
    The comment has been removed

  • Anonymous
    May 22, 2007
    Also, in response to James_A and Eric Young: I have found that no matter how many times you choose to apply v3 over v2 for KB927891, Add/Remove still says v2.  You must first uninstall v2 via Add/Remove and then install v3 in order to see "v3". I haven't noticed any performance differences with v2 vs v3 but it's always good to know you have the latest and greatest!  BUT... we're not about to to MANUALLY uninstall v2 on nearly 1,000 machines just to see v3 in Add/Remove.  (at this point - unless we notice a performance difference) BUT#2, If we DO see a performance difference AND the latest WSUS critical update deploy of KB927819 doesn't overwrite v2 with v3, I guess we have to re-think.

  • Anonymous
    May 23, 2007
    The comment has been removed

  • Anonymous
    May 23, 2007
    Are the WSUS 3 client downloads eg. at http://download.windowsupdate.com/v7/windowsupdate/redist/standalone/WindowsUpdateAgent30-x86.exe language neutral or are they ENU only?

  • Anonymous
    May 23, 2007
    I have installed all the patches and still have a problem with the svchost.exe file, processor still runs excessivly and if the kernel32.dll is suspended, the processor calms down to normal, however, IE cannot connect to the internet, have to use Firefox.  Also, this has caused problems connecting to my network drives using explorer, cannot see the drives at first boot.  This is getting tiresome.  I have been watching my pc run at 100% for weeks, doing nothing.  The heat being pushed off the cpu is incredible, just wonder what it is doing to the life of my hardware?

  • Anonymous
    May 29, 2007
    Well, we're having this same issue at our office.  We have all the latest patches installed and WSUS 3, but svchost is still pegging the CPU and grinding everything to a halt.  On another related note, MS Outlook 2003 seems to be affected by this as well.  After downloading the latest IE patch, whenever you try to type a message or receive in Outlook in HTML format, it takes a minute or so for the text to show up that you type.  I would say, "Hey, let's just turn off HTML", but it still affects incoming messages and trying to get 300 staff to all do this will be killer.  Are others still having this issue?

  • Anonymous
    May 30, 2007
    Hey Jeff, thanks for this (http://swigartconsulting.blogs.com/tech_blender/2006/07/windows_update_.html) the procedure outlined there seems to have worked in clearing up the issue for me. So...to the MS guys: if the problem is related to something getting hosed in the %WINDIR%SoftwareDistribution folder, which apparently happens from time to time...is there a specific update the seems to be doing it? If its in the DataStore.edb file, as previously mentioned...has anyone attempted (would it even work) to use any of the edb maintenance utilities to check the file (like you would Exchange, ADS, etc)?  Maybe I'll try that on the next machine we have to fix and see what happens... Jordan

  • Anonymous
    May 30, 2007
    The comment has been removed

  • Anonymous
    June 02, 2007
    I am amazed at the nightmare I am going to have to go though to try to work around a Microsoft bug.  I have been using Microsoft Update for years even before Office 2003 and with Office 2003 since it was released.  How come just now is there a problem with this when it has worked correctly for years? There are a lot of flaws in recent Microsoft sofware but I will have to say that this is the worst of it.  Microsoft Update should be something I don't even have to think about.  Please take this seriously, folks or it could spell the end of user confidence in Microsoft Update. Dale

  • Anonymous
    June 02, 2007
    Just another point.  After spending 12 hours today struggling with Microsoft Update on just two PCs before finding this solution, now I am reviewing these procedures and the procedures in the referenced KB articles.   You have got to be kidding.  This is the fix that you expect millions of users to implement in order to fix broken Microsoft Update when Office 2003 is installed?  I am a MCAD, MCSE, MCDBA with many years of IT experience and yet this is a very daunting proposition to undertake fraught with risk of destroying Windows Update even worse than it already is.  Shame on Microsoft and the WUS team for this.

  • Anonymous
    June 05, 2007
    The solution for slow microsoft updates downloads and installation of the updates to Office 2003 While Microsoft Updates are disabled : Download the Update for Windows XP (927891) package now.  Then, restart. For most home xp systems http://go.microsoft.com/fwlink/?LinkID=91237 (which is WSUS version 3.0 client program) Install, then reboot.  May take 2x reboot. This is a very controversial issue for Microsoft, in fact - if you call them and explain it they will immediately ask to remote into your machine and look at logs. Now for the installs of the updates to Office 2003

  1. Make sure the Office Source Engine is set to manual in the service > applet. (start > run > services.msc > scroll through the list and make > sure it > is listed and set to manual.) > > 2) Put your Office 2003 CD in the drive and run setup. Do a detect and > repair because it is possible that the Local Install Source (the hidden > MSOCache folder) or the setup files under program filesMicrosoft office > are  toast. Running detect/repair from the CD might help repair this. > > (  1) The first worked for me as I found the Office Source Engine was disabled and therefore I only had to switch it to manual and then click on Start) you can now switch on the auto updates.....If you dare!!