Hotfix for high CPU usage by SVChost during .MSI installs is now publicly available

  • Thread starter Thread starter Bill Sanderson MVP
  • Start date Start date
B

Bill Sanderson MVP

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


I recommend this one to everyone. I've seen this symptom fairly frequently,
including on one client machine just this morning. I find the wording of
the KB article somewhat misleading--it seems to say that is fixes an issue
with the earlier patch, but, in fact, it should address the basic issues
that gave rise to that earlier patch.


--
 
Thanks, Bill. However it is also unclear to me: is the 916089 hotfix
prerequisite for this ? I don't have 916089 installed on my system.
 
Way down near the bottom of the KB article, it states that this hotfix
replaces the earlier one. On XP, SP2 is the only prerequisite.



--
 
Bill,

I also do not appear to have this, so I guess it did not come down as a
critical update on Patch Tuesday.

How do we know if we need it?

Are you saying this is something we all need?

Thanks,
Tim
 
Bill, Tim asked my questions also.


Tim Clark said:
Bill,

I also do not appear to have this, so I guess it did not come down as a
critical update on Patch Tuesday.

How do we know if we need it?

Are you saying this is something we all need?

Thanks,
Tim
Click to expand...
 
Unfortunately this did not fix my problem with MU using IE7 on XP SP2. My
scan eventually goes down with a 0x8DDD0009 error. I applied this patch
yesterday and after 40 minutes I stopped it. The fix says it is a WIP so I
hope MS can get this to work.

Chris
 
I suspect that this fix will eventually be incorporated into some broadly
distributed set of fixes--maybe a service pack. It's possible that this is
more likely to be an issue on machines with slower CPU's--I've mostly seen
the issue on the oldest machines I work with. If you've never seen any
issue of unresponsiveness of the machine surrounding an autoupdate, or
Windows Defender definition updates--you can probably ignore it.

--
 
Maybe I overstated. I've seen the issue of high CPU usage on enough
machines that I think this is a fairly broad problem--but if you are not
seeing it, there's no need to change that file--the patch updates a single
file on 32-bit machines.

--
 
That's an error I can't recall having researched. I see lots of Google hits
on it, but I can't tell which (if any!) have productive help, and I don't
have much time tonight.

I'm tempted to suggest dial-a-fix--but perhaps you've already tried that?
I'm not at all sure it would help, but it shouldn't make anything worse,
either.

--

Chris Wood said:
Unfortunately this did not fix my problem with MU using IE7 on XP SP2. My
scan eventually goes down with a 0x8DDD0009 error. I applied this patch
yesterday and after 40 minutes I stopped it. The fix says it is a WIP so I
hope MS can get this to work.

Chris
Click to expand...
 
Bill,

I would like to try an experiment. I will check for updates at MS.
Does there need to be an update for the test to work?
Can I do a Check today, even if there are no update available?

I not will I need to wait for Patch Tuesday?
Will the next WD update due?

Will AU "Notify Only" work or should I disable AU when I know there is a WD
update and check manually via WU.

I will run the Task Manager and watch CPU usage.
How much/how long is too much/too long?

?:-)
Tim
 
You need to be installing something which comes packaged as a .MSI file.

You could just pick a download from Microsoft--Windows Defender, for
example.

Doing a check when no update is available won't tell you anything.

There are other patches besides the critical ones--you could do a custom
scan and pick something optional to install--but not all patches are .msi
files.

In my experience when this issue arises, the machine becomes essentially
unusable for significant periods of time--it's not just annoying--it really
sucks.

--
 
Back
Top