SVChost.exe 99% CPU Usage with SP3 installed

"Shenan Stanley" wrote:

Dr. Wu wrote:
"Olórin" wrote:

Don't confuse terseness with condescension. And Shenan WAS helpful
- he provided *plenty* of material, some of which should have been
researched before applying something as significant as a Service
Pack to an Operating System, some of which provided help fixing
the problems it caused (including a link to free support from
Microsoft). Topped off with a "Good luck!". What more do you want?

If the OP had had a quick scout in the "real world" before
installing SP3, he/she would have found *plenty* of people
advising "wait a while, see what the early adopters find".



Though I agree that updates such as Service Packs need to be
researched prior to installation I must state that I was not
informed of the installation of Service Pack 3. Not on the
computer that I am having problems with or many of the computers
that I take care of at work.

If a Service Pack needs to be researched prior to installation then
tell me why Microsoft has decided to make it an automatic,
unattended update?

If Microsoft has made it an automatic update then how does anyone
think they can tell someone that "they should have researched it
prior to installation"?

Actually - if everything is on schedule - today is the first day Automatic
Updates will offer SP3 to those people with the setting configured to
automatically download and install updates. Other users may have gotten it
if their settings for AU were different than that - but they still had to
choose (in those cases) whether they installed it or not from the list they
were shown - and if they just click on it and don't specify what to/what not
to install - why do they have their settings set to notify them anyway?

The problem here then is not on the end users side but rather on
Microsoft's decision to publish a Service Pack as an automatic and
silent update.

It would have been far more appropriate for Microsoft to post the
availability of the Service Pack as well as the preliminary
preparation procedure towards the installation of the upgrade.

Most people *expect* things just to work and just to stay secure. Sad - but
it seems to be true. They purchase some software and if it doesn't
automatically configure for them - they get frustrated and remove it or
replace it or...

Now there are a lot of computers out there that may be suffering
from this malady. That means that there are a lot of people who
use those computers for critical business use that are down or
having serious problems.

What defines "a lot" and how did you come up with this?

I'm sorry but even though good luck is a nice touch it is far from
adequate.

*shrug*
I volunteer here - that's it. I gave my advice politely even faced with the
obvious obstinance of the poster. If you don't take it as friendly advice -
so be it. Each has to make their own determination of everything in life -
everything is from their perspective.

Information on what to do prior to the installation is a little too
late.

But it may be all someone has if they didn't bother to prepare.

Information about issues not related to this problem such as a 0x7e
stop error also is not appropriate. This isn't the reported issue.

There was no reported issue.

What would be acceptable is a resolution so that we can get back to
work on business matters, not on troubleshooting computers.

Okay - in a business enviroment - involving computers - you should be able
to revert to your latest backup - most likely made moments before you
applied something as critical as a service pack - but likely at least the
night - possibly the weekend before.

Please don't read any emotion into this post, there is no anger
here. There is a lot of frustration however.

Frustration is good - but you are directing your frustration about your
problems onto others - from my perspective.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html



I understand that you volunteer.

Whatever Microsoft's schedule is the cat was let out of the bag early.

The computer I'm typing on now received SP3 without any user intervention or
acceptance, it just happened.

I can't tell you why it just is the case.

Anyways, this has gotten a whole lot more heated than originally intended.

I am just going to back away now. I'm not finding any resolutions to the
reported issue of SVChose.exe 99% CPU Usage with SP3 installed.

Even after uninstalling SP3 there is still a svchost that is wacking out.
And the updating is not working (even though it worked with SP2).

I guess I'm just going to drop back and punt.

It's time to reinstall the OS and all applications.

I hope that I haven't said anything here to continue this argument. If so
then what the heck, a rise in blood pressure is good every now and then.

Ya'll come back now ya hear!

"Dr. Wu" wrote in message
...

I am just going to back away now. I'm not finding any resolutions to
the
reported issue of SVChose.exe 99% CPU Usage with SP3 installed.

Even after uninstalling SP3 there is still a svchost that is wacking
out.
And the updating is not working (even though it worked with SP2).

I guess I'm just going to drop back and punt.

It's time to reinstall the OS and all applications.

Wow, that's a drastic solution! But I guess it will work.

In the event you decide you wish to troubleshoot first (which is usually
easier and quicker than flattening and rebuilding), I recommend using
Process Explorer to determine the offending service which is using
svchost.exe. This should get you started:

http://www.google.com/search?hl=en&q...rer%22+svchost

The first hit seems more than adequate:

http://www.bleepingcomputer.com/tuto...torial129.html

I also suggest from now on to manually update your PC (you have already
been burned by relying on Microsoft's imperfect automatic updates!).
Also, it's a very good idea to periodically make images of your hard
drive, especially before installing anything substantial like a Service
Pack.

freeheeler wrote:
I knew it, I knew it, I knew it.......I was hesitant to apply sp3
and I SHOUD HAVE TRUSTED MY INSTINCTS!
When will MS fix this piece of crap!??????

And he is right. I had this problem a year ago, installed the patch, it
fixed it, all was well. SP3 came out, I installed last week, the problem is
back, my fan runs constantly, my pc is burning up, ridiculous. So I tried to
reinstall the patch and guess what? It won't run on SP3. I called
Microsoft, they know it's a problem, they are working on it. In other words,
don't hold your breath.

So here's the solution:

Start, Run, services.msc, automatic updates, stop it if it's running, then
disable it. You will HAVE TO REMEMBER to start it and check updates once a
week or so. then turn it off again when done, but at least your pc will work
right again.

P.S. You also have to stop BITS.

Hello, all.

I had the same problem as you all, hence my posting on this thread. AUinstaller3.0 did not fix the SVCHost problem so I just turned everything off. I can't even run the ActiveX plugin on the Windows Update website.

On the underlaying topic of proper research and documentation, I just have to say all of you are right, to some extent.

MS (yes, Sheenan, I do mean MICRO$OFT) should've have made the SP3 update require User Permission to install since they KNEW from the beginning it was not complete. (which is kind of an prescription drug paradox "you take an asthma med and the side effects are rashes and shortness of breath"). They should've also provided proper documentation about preparations and precautions (case in point, the missregistration of wuauserv.dll/wuauserv2.dll AND the deletion of previous restore points when SysRes has not been assigned enough memory, since those seem to be the most common problems floating around and they shouldve surfaced on the testing phase IF they did do a proper testing phase.)

BUT the user, myself included should've also done more research. Since this is a new update, way new, one would've encountered almost no material TO research, therefore prompting to wait a bit more on the installation of SP3.

I guess the mayority of end-users (oblivious, non-geek, and computer savvy) are not bare-bone experts, and do not have the knowledge nor the time to do a complete system image or spend several hours rummaging through websites and technical data to find out if they should or should not install a piece of code from a vendor they have been condition to trust blindly (case in point, "silent" automatic updates.)

So take a chill pill, y'all! Cause in computers like in life you only got options: Take the plunge, or don't do crap (oops! LANGUAGE LOL.)

We do not know what "the same problem as you all" is because you started
a new thread. For the same reason, we do not know what problem is "the
SVCHost problem".
---
Leonard Grey
Errare humanum est

Silver D wrote:
Hello, all.

I had the same problem as you all, hence my posting on this thread. AUinstaller3.0 did not fix the SVCHost problem so I just turned everything off. I can't even run the ActiveX plugin on the Windows Update website.

On the underlaying topic of proper research and documentation, I just have to say all of you are right, to some extent.

MS (yes, Sheenan, I do mean MICRO$OFT) should've have made the SP3 update require User Permission to install since they KNEW from the beginning it was not complete. (which is kind of an prescription drug paradox "you take an asthma med and the side effects are rashes and shortness of breath"). They should've also provided proper documentation about preparations and precautions (case in point, the missregistration of wuauserv.dll/wuauserv2.dll AND the deletion of previous restore points when SysRes has not been assigned enough memory, since those seem to be the most common problems floating around and they shouldve surfaced on the testing phase IF they did do a proper testing phase.)

BUT the user, myself included should've also done more research. Since this is a new update, way new, one would've encountered almost no material TO research, therefore prompting to wait a bit more on the installation of SP3.

I guess the mayority of end-users (oblivious, non-geek, and computer savvy) are not bare-bone experts, and do not have the knowledge nor the time to do a complete system image or spend several hours rummaging through websites and technical data to find out if they should or should not install a piece of code from a vendor they have been condition to trust blindly (case in point, "silent" automatic updates.)

So take a chill pill, y'all! Cause in computers like in life you only got options: Take the plunge, or don't do crap (oops! LANGUAGE LOL.)