WindowsUpdate causing svchost.exe to consume 100% of the CPU Jim 5/15/2007 5:13:01 PM There is a fix for this: KB927891 at http://support.microsoft.com/kb/927891/en-us . However, the fix implies that Microsoft does not understand how bad this problem really is. The "Symptoms" section section lists 2 symptoms, implying that both of them need to be in force. 1 of the 2 symptoms is actually 2 different symptoms. Counting them as 3 symptoms, I have seen nearly every permutation of the 3 symptoms on various systems. Only 1 needs to be in force, and more than one can be. Further, in the same section, there is a statement that "You experience this problem after you install the hotfix that is described in the following Microsoft Knowledge Base article:", and then it points to KB article 916089. Well, unless that fix is inside a service pack, NONE of the systems on which I've seen this problem have had it installed. And, if it is, MS needs to get 927891 into production ASAP, because the old patch no longer exists (having been replaced by 927891). I researched this problem on the Internet, and found that it has been going on, in one form or another, since at least late 2005. However, it has not (to our knowledge) hit my company as a problem until the May 8 patches from WSUS and WindowsUpdate. The patches on that date seem to cause a roughly 50% chance that the system will be rendered unusable. I have found many clues in Internet searches that imply the problem is an order of magnitude greater if one is installing an Office patch than it is if one is only installing Windows (XP) patches or IE patches (etc.) The problem is that Microsoft does not seem to realize how serious this problem is. 927891 is still a "pull" download; it has not been released through the regular update channels. As a result, half of my test systems were rendered unusable until I figured out what the problem was and worked around it (manually). Does anybody know when MS will be pushing this patch to general production? I can't release any updates via WSUS until this patch is installed on peoples' systems. Jim

Re: WindowsUpdate causing svchost.exe to consume 100% of the CPU Gus <vines77[ at ]gmail.com> 5/15/2007 7:05:19 PM See this link to the WSUS Team Blog updated today: http://blogs.technet.com/wsus/default.aspx On May 15, 1:13 pm, Jim <J...[ at ]discussions.microsoft.com> wrote: [Quoted Text] > There is a fix for this: KB927891 athttp://support.microsoft.com/kb/927891/en-us. However, the fix implies that > Microsoft does not understand how bad this problem really is. The "Symptoms" > section section lists 2 symptoms, implying that both of them need to be in > force. 1 of the 2 symptoms is actually 2 different symptoms. Counting them as > 3 symptoms, I have seen nearly every permutation of the 3 symptoms on various > systems. Only 1 needs to be in force, and more than one can be. > > Further, in the same section, there is a statement that "You experience this > problem after you install the hotfix that is described in the following > Microsoft Knowledge Base article:", and then it points to KB article 916089. > Well, unless that fix is inside a service pack, NONE of the systems on which > I've seen this problem have had it installed. And, if it is, MS needs to get > 927891 into production ASAP, because the old patch no longer exists (having > been replaced by 927891). > > I researched this problem on the Internet, and found that it has been going > on, in one form or another, since at least late 2005. However, it has not (to > our knowledge) hit my company as a problem until the May 8 patches from WSUS > and WindowsUpdate. The patches on that date seem to cause a roughly 50% > chance that the system will be rendered unusable. > > I have found many clues in Internet searches that imply the problem is an > order of magnitude greater if one is installing an Office patch than it is if > one is only installing Windows (XP) patches or IE patches (etc.) > > The problem is that Microsoft does not seem to realize how serious this > problem is. 927891 is still a "pull" download; it has not been released > through the regular update channels. As a result, half of my test systems > were rendered unusable until I figured out what the problem was and worked > around it (manually). > > Does anybody know when MS will be pushing this patch to general production? > I can't release any updates via WSUS until this patch is installed on > peoples' systems. > > Jim

Re: WindowsUpdate causing svchost.exe to consume 100% of the CPU Jim 5/15/2007 9:58:00 PM Yes, that helps. Thank you. Do you know if that web site is "official" (i.e. from Microsoft)? "Gus" wrote: [Quoted Text] > See this link to the WSUS Team Blog updated today: > > http://blogs.technet.com/wsus/default.aspx > > > On May 15, 1:13 pm, Jim <J...[ at ]discussions.microsoft.com> wrote: > > There is a fix for this: KB927891 athttp://support.microsoft.com/kb/927891/en-us. However, the fix implies that > > Microsoft does not understand how bad this problem really is. The "Symptoms" > > section section lists 2 symptoms, implying that both of them need to be in > > force. 1 of the 2 symptoms is actually 2 different symptoms. Counting them as > > 3 symptoms, I have seen nearly every permutation of the 3 symptoms on various > > systems. Only 1 needs to be in force, and more than one can be. > > > > Further, in the same section, there is a statement that "You experience this > > problem after you install the hotfix that is described in the following > > Microsoft Knowledge Base article:", and then it points to KB article 916089. > > Well, unless that fix is inside a service pack, NONE of the systems on which > > I've seen this problem have had it installed. And, if it is, MS needs to get > > 927891 into production ASAP, because the old patch no longer exists (having > > been replaced by 927891). > > > > I researched this problem on the Internet, and found that it has been going > > on, in one form or another, since at least late 2005. However, it has not (to > > our knowledge) hit my company as a problem until the May 8 patches from WSUS > > and WindowsUpdate. The patches on that date seem to cause a roughly 50% > > chance that the system will be rendered unusable. > > > > I have found many clues in Internet searches that imply the problem is an > > order of magnitude greater if one is installing an Office patch than it is if > > one is only installing Windows (XP) patches or IE patches (etc.) > > > > The problem is that Microsoft does not seem to realize how serious this > > problem is. 927891 is still a "pull" download; it has not been released > > through the regular update channels. As a result, half of my test systems > > were rendered unusable until I figured out what the problem was and worked > > around it (manually). > > > > Does anybody know when MS will be pushing this patch to general production? > > I can't release any updates via WSUS until this patch is installed on > > peoples' systems. > > > > Jim > > >

Re: WindowsUpdate causing svchost.exe to consume 100% of the CPU eddieb[ at ]online.microsoft.com (Eddie Bowers [MSFT]) 5/15/2007 10:47:38 PM You can consider that official. Eddie Bowers Security Support Microsoft Corporation This posting is provided "AS IS" with no warranties, and confers no rights.

Re: WindowsUpdate causing svchost.exe to consume 100% of the CPU Nigel Jett <jettn[ at ]evergreen.edu> 5/15/2007 11:44:27 PM Eddie Bowers [MSFT] wrote: [Quoted Text] > You can consider that official. > > Eddie Bowers > Security Support > Microsoft Corporation > > This posting is provided "AS IS" with no warranties, and confers no rights. > So does that mean your sig is ironic?