SP2 Installation Warning!!!

[Rich]

I just wanted to give everyone a heads up on what I've ran into with Windows
XP SP2 installations. I've discussed this with a few IT colleagues and they
have had some similar experiences.

I've experimented on 6 workstations and a notebook. The results are anything
from 'working just fine', 'run but slow as cold tar', to 'non-functional'.
And I'm talking about computers with identical software installations. Some
hardware differences.

Now for the good news. I created a slipstreamed Windows XP SP2 installation
CD and have used it 4 times. All four installed fine and they are not only
working perfectly, but are running just as fast an original Windows XP
install. I haven't had time to try to find the possible conflicts with SP1
installs, but there does seem to be a problem with installing it on a
pre-existing SP1 installation. And this may just come down to the exact
hardware configuration.

There's is one idea that came to me during a 3:00 a.m. fix one night.
Because of Windows XP's file protection, it may be there are some files that
the SP2 installation does not properly over-write and therefore lead to
problems depending on what features (hardware setup) is in use.

Because of my experiences, and those of the guys I've talked to, I will only
install SP2 as part of a Windows XP SP2 clean install. It's just been the
only time I haven't ran into problems with it.

 

[GTS]

Odd. I've installed SP2 on about 15 PC's at this point including 3
notebooks without a single serious problem. Before the installation I make
sure that the machine is spyware and Trojan free and in good overall
condition. I clean up temp and tiff files, check that device manager shows
no problems, shut down antivirus software and unnecessary programs, etc.
Something doesn't sound right. Are you doing appropriate preparation? Your
theory that "Because of Windows XP's file protection, it may be there are
some files that the SP2 installation does not properly over-write" sounds
nonsensical.

 

[Rich]

Yes, I did all the prep's you speak of plus I uninstalled any unnecessary
software and unplugged anything that wasn't needed.
Ex:
Workstation #1
Existing XP SP1a installation
I went through it methodically. After the install, it ran fine, but it was
slowed dramatically. I disabled as many items and services as possible, but
no change. The performance change was that of pulling half the ram out of
it.
I wiped it clean.
Installed Windows XP SP2 clean.
Installed all the software (including proprietary database admin software).
It runs like it did with the original XP install.

I care to differ with you, though. I don't think my thoughts are not
"nonsensical". We are talking about Microsoft (home of SP1 followed closely
with SP1a) I don't have time to research all aspects of this because I'm a
one-man IT crew and IT is just one of the jobs I do for my company. I also
don't have time to troubleshoot problems that arise from 'upgrades' or
service packs that should be fixing or improving things (7 servers, 52 PC's,
4 different database servers). (it's an industrial/engineering facility)
Things such as Service Packs and updates should not come with this many
strings attached. Talk a look at all the software titles that have 'issues'
with SP2. Some of them are Microsoft's own software! And they are not old
titles or versions. http://support.microsoft.com/default.aspx?kbid=842242
Who needs this kind of grief just to get pre-existing software to function
again in an enterprise environment.

Remember because of 'files in use', 'startup services and apps', or 'System
Restore', there have been many viruses that have come out in the last year
that require System Restore to be disabled and a boot into Safe Mode to
remove the virus. That's just a virus. We're talking about 'half an OS' redo
by a service pack. It's all part of Windows XP's file protection system.

I wish you could here my phone ring with all the complaints and problems
with SP2. Matter of fact, just look through this very newsgroup.

I agree. I do believe that most of the problems with SP2 are 'install
software' issues or pre-existing junk, but some are obviously hardware
related.

 

[GTS]

Rich,

Sorry about that use of the work 'nonsensical,' which was
unintentionally harsh. I should have said unlikely. I wouldn't draw too
many conclusions about the overall problem rates from reports in the
newgroup since it's very skewed by it's nature. Most of the issues noted in
KB 842242 deal with predictable Firewall port issues.

I'm not sure what to make of our very discrepant experience with SP2. Good
luck in any case. It certainly sounds like you have your hands full.

 

[BP]

"I wouldn't draw too many conclusions about the overall problem rates from
reports in the newsgroup since it's very skewed by it's nature."

Whistling in the dark.

 

[Enkidu]

"I wouldn't draw too many conclusions about the overall problem rates from
reports in the newsgroup since it's very skewed by it's nature."

Whistling in the dark.

This ALWAYS happens when an SP comes out, or even a substantial fix
package. It seems no better or worse than usual.

Cheers,

Cliff

 

[GTS]

I'm not sure what you're trying to say with that remark, but there was a
similar flood of questions with SP1, which, as it turned out had no endemic
flaws. It's too early to judge the overall success of SP2 installations,
but newsgroup questions will not provide a realistic basis for same.

 

[BP]

What I'm saying is that I *am* drawing conclusions from the reports in this
and other newsgroups because this is where people report problems. I am not
interested in evaluating the success rate of installations. I am interested
in making sure that I will not have any problems loading this sucker on *my*
machine. I have compiled quite a little list of issues to look out for and
the info I have gained here is valuable. Granted, it seems that the majority
of installation problems are due to the fact that many people simply can't
follow instructions, but there are some issues that are compatibility bugs
that have to be squashed. In defense of software engineers, there are just
too many configuration variations for any mere mortal to anticipate in
advance. At some point you've got to launch and let the bugs show
themselves. But to dismiss the problems that people are reporting in this
group, real or self inflicted, as "nothing to worry about" is not helpful to
anybody.