Re: SVChost.exe 99% CPU Usage with SP3 installed

Dr. Wu wrote:
For brevity I've removed all previous posts text from this response.

Though I don't yet have an answer to this issue I am experiencing
it on one of my two computers. My laptop isn't causing me this
issue. My desktop, however, is.

There were very little differences in the installations at the time
that I saw the issue start. Both have Windows XP Pro and both were
updated to SP 3. While the Laptop has Office 2003 Professional and
all ancilary Office 2003 products (Visio, InfoPath, FrontPage,
Project...) the Desktop has all of that plus Office 2007 Enterprise
and a couple of extras such as Visio, Project and Expression Web.

When I installed the Office 2007 products I opted to keep all
previous versions of Office as well as the Download a file to keep
it running and the automatic updates.

I installed Office 2003 and Office 2007 after installing Windows XP
SP3. I did not notice any hit to performance until after
installing Office 2007.

This leads me to believe that it is Office 2007 or part of the
installation that is causing the CPU issues.

I've installed Windows XP SP3 on many computers to date (I am in an
IT department and take care of over 200 workstations - and sadly
over 200 end-users). SP3 has installed on all of them through
automatic updates and I've yet to receive a complaint.

It might be helpful to find out how many people who have this
problem also have installed Office 2003 with it's automatic updates
turned on.

But I digress...

What has prompted me to post this reply is Sheenan's response to
Freeheeler. Though Freeheeler should not have used the verbage that
he/she did I've
found myself in his/her level of frustration many times in the past
5 years.

There have been many Microsoft Updates that have brought our
computers to their knees. I've spent many mornings in crisis mode
because a Microsoft Update has crashed computers. Usually it
starts with the VPs of the company because they are there early
(yes that isn't a typo).

We had an Automatic Update bring our Exchange Server down and it
took a day and a half for the poor gal who had to fix it to talk
with Microsoft and eventually determine that it was Microsoft's
Update that caused the problem in the first place.

Though I sympathize with Freeheeler's frustration I don't condone
his/her
use of language.

I also strongly oppose Sheenan's retort. Microsoft has conditioned
us to beleive that any and all "Critical Updates" must be installed
as soon as possible. When they do put information about the update
it is usually a very long and complicated document that none of us
in the "real" world have the time to read and fully comprehend.

Microsoft's support is no longer what it used to be as well. I
used to be able to contact a real person by phone and get
immediate, accurate and fully understandable help to resolve a
problem as soon as possible.

Microsoft understood that happy customers are faithful customers.

Now I can't get to anyone on the phone. If I can I'm stuck with
someone who cannot speak without an accent so strong that I cannot
understand them.

Microsoft's documentation used to fully cover the software that it
was written for. I work with Visual Basic 6.0 Pro, Visual Studio
.NET 2003 Pro, and have just received Visual Studio .NET 2008 Pro.

I am here to tell you that Microsoft's documentation is no longer
what it was.

I worked with VBA 6 a while back. The documentation was flawless.
It was truely a place to go to get any questions answered.

It is no longer the case.

I suggest that Shenan get off his/her high horse and start using
compassion towards those who've been hit by anything Microsoft that
has caused their computer to crash or become non-responsive. These
are people who have work to do and cannot do it because of a
possible poorly written update.

I've been there. I know.

Let's become helpful, not condescending!

Whether you like what I say or not, there you have it.

Nothing condescending about my earlier response.

I am in the poster's shoes (or very similar ones) at least once a month if
not more often. I understand and have empathy for most every poster I
choose to give freely of my time to and answer. Everything I stated was
posted in a polite and complete manner and has been repeated by
myself and many others all over the internet and these newsgroups in
particular.

Here's the stuff you snipped...
http://groups.google.com/group/microsoft.public.windowsxp.perform_maintain/browse_frm/thread/39baf73b3a32b50f/2792d5557d27a94d#2792d5557d27a94d

SP3 is not a critical update. One has to choose to install it. No one
forces anyone to install SP3.

As for Microsoft's support not being what it 'used to be' - *shrug* - likely
true. Not like that same song hasn't been sung for every large company I
have ever had to research/deal with. The real world does suck that way.

I responded so that those who might be researching a problem with SP3
would likely find my (or a similar) response at some point in their search.
It contains most of the major issues that have surfaced since SP3's
release and the resolutions found to work for those issues. I cannot think
of a better way to respond to someone's posting such as that put out
there by Freeheeler... I could have *not* responded - but that could have
easily left someone in the cold - thinking that SP3 is, what did Freeheeler
say, a "piece of crap" and that they should wait until Microsoft resolves
the issues with it.

The problem with coming to that conclusion is that it has been over a month
now and the only 'fixes' out there are the ones I (and many others) have
posted (or links from the links I and many others have posted) to the common
issues. I doubt there is some Microsoft knight in shining armor that is
going to help anyone coming over the hill - so I figured it would be better
to let people know - as often as possible - that with a little forethought,
a little planning and a little effort - their installation of Windows XP SP3
could be trouble-free and/or safe.

If you don't consider that helpful... *shrug*

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


.

Relevant Pages

  • Re: Pirated XP, means-test everyone and every product with "income
    ... The last thing on my mind is a guilty concourse about installing ... is your theory on life. ... >> will say it once again I am very pro Microsoft. ... >> Microsoft is computers and computers are Microsoft. ...
    (microsoft.public.windowsxp.general)
  • Re: Problems with Windows Update should not be charged to report.
    ... I could tell you an interesting stories about this concerning Microsoft ... So, tsk, tsk, tsk, on you for thinking that was an ... automatically installed on all 26 computers in our club's classroom. ... have a problem installing themselves, and I have nowhere to report the ...
    (microsoft.public.officeupdate)
  • Re: SVChost.exe 99% CPU Usage with SP3 installed
    ... I've installed Windows XP SP3 on many computers to date (I am in an IT ... SP3 has installed on all of them through automatic updates ... I've spent many mornings in crisis mode because a Microsoft ... If the OP had had a quick scout in the "real world" before installing SP3, ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: SP2
    ... not properly preparing and not properly installing the ... help users prepare their computers. ... The upgrade should not render ... >You really have a few options and Microsoft making SP-2 ...
    (microsoft.public.windowsxp.general)
  • Re: Service Pack 3 Problems: Do I need it?
    ... You buy 'em books and buy 'em books but all they do is eat the covers! ... I did have a problem getting SP3 installed on one, but downloading the SP3 install file and installing it in Safe Mode got me around that one problem. ... blames OEM's and OEM's blame Microsoft, ...
    (microsoft.public.windowsxp.help_and_support)
Loading