Problems with SP4+Rollup

[Guest]

Archived from groups: microsoft.public.win2000.general (More info?)

I have a Windows2000 Professional machine that has been running 24/7 since
early 2001. It has been restarted twice, once after applying SP1 and again
after applying SP3. SP2 was skipped. Except for those two restarts it has
been running continuously. It is a dual processor Pentium-III with 1GB
PC-133 SDRAM and all it does is render video that is fed to it thru the
network.

Violating my "If it ain't broke, don't fix it" rule I decided to apply SP4
and then the End-of-Life Rollup.Big mistake. After restarting twice I
noticed about two hours later that the machine had become unresponsive. No
error, no blue screen, no nada ... just not responding to any external
stimulus. Powered down and restarted. Next morning when I went to check last
nights production ... blue screen. IRQL not Less Than or Equal. Restarted
.... 3 hours later a blue screen. something about Page Fault in a non paged
area.

Restored the machine from a Ghost Image taken before the upgrade. this was
eight days ago and it has been running perfectly for those eight days ...
24/7 flawlessly.

I'm not seeking help.
I'm not looking for solutions.

I know what the problem is.
I've already applied the solution.

Just sharing my experience.

 

[Sparda]

Archived from groups: microsoft.public.win2000.general (More info?)

"" wrote:
> I have a Windows2000 Professional machine that has been
> running 24/7 since
> early 2001. It has been restarted twice, once after applying
> SP1 and again
> after applying SP3. SP2 was skipped. Except for those two
> restarts it has
> been running continuously. It is a dual processor Pentium-III
> with 1GB
> PC-133 SDRAM and all it does is render video that is fed to it
> thru the
> network.
>
> Violating my "If it ain't broke, don't fix it" rule I decided
> to apply SP4
> and then the End-of-Life Rollup.Big mistake. After restarting
> twice I
> noticed about two hours later that the machine had become
> unresponsive. No
> error, no blue screen, no nada ... just not responding to any
> external
> stimulus. Powered down and restarted. Next morning when I went
> to check last
> nights production ... blue screen. IRQL not Less Than or
> Equal. Restarted
> .... 3 hours later a blue screen. something about Page Fault
> in a non paged
> area.
>
> Restored the machine from a Ghost Image taken before the
> upgrade. this was
> eight days ago and it has been running perfectly for those
> eight days ...
> 24/7 flawlessly.
>
> I'm not seeking help.
> I'm not looking for solutions.
>
> I know what the problem is.
> I've already applied the solution.
>
> Just sharing my experience.

Thank you, im glad you share my opinon on software upgrade "If it
works, why upgrade?" upgrading often causes more problems then it
fixes, and you case is a perfect example.

--
Posted using the http://www.windowsforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.windowsforumz.com/General-Discussion-Problems-SP4-Rollup-ftopict401503.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.windowsforumz.com/eform.php?p=1328121

 

[Guest]

Archived from groups: microsoft.public.win2000.general (More info?)

Sparda wrote:
>
> Thank you, im glad you share my opinon on software upgrade "If it
> works, why upgrade?" upgrading often causes more problems then it
> fixes, and you case is a perfect example.
>

Just because YOU think it "works", doesn't mean it actually does.

Even looking at things only from a security standpoint, W2K is
most definitely "broken" and in need of fixing. You can say the
same thing of any other version of Windows, as well as Linux and
other operating systems.

MicroSoft doesn't rush with anything. By the time they get
around to publishing a fix for a security hole, odds are
overwhelming that hackers have long since found ways to exploit
that hole. There is usually only a very narrow window of time
in which to install a security fix before the exploit becomes
well known to hackers and the risk to undefended systems skyrockets.

By and large, when MicroSoft issues a security patch for Windows
(whatever version), it makes it less "broken". There are
occasional exceptions, however, and the post-SP4 rollup is most
definitely one of those exceptions. Competent admins will make
a backup image of their system and boot partitions so that they
can easily undo patches/hotfixes that cause problems.

If you think you can take an "If it ain't broke, don't fix it."
approach to Windows or Linux or Unix or ... security, you are
seriously mistaken. Burying your head in the sand does not make
the bad guys go away.