B
BillW50
In glee typed:
I routinely repair other people infected systems all of the time, Glen.
I pull the drives out and scan them with a known clean system. And it
doesn't matter if you believe me or not. As all you have to do is to
scan Microsoft's KB list to know that updates can and does mess up an
OS.
List of fixes that are included in Windows XP Service Pack 3
http://support.microsoft.com/kb/946480
Just look how many of these from the SP2 update had screwed up many
systems. There are dozens of new problems that were caused by SP2
directly. Sure SP3 fixed some of them, but SP3 also caused some of their
own new problems. Although there is not going to be a SP4 to fix all of
the new problems from SP3, now is there?
Don't let XP Service Pack 3 hose your system
http://windowssecrets.com/top-story/dont-let-xp-service-pack-3-hose-your-system/
Windows XP SP3 Issues and Fixes Continued
http://techtalk.pcpitstop.com/2008/...p3-still-not-ready-news-flash-do-not-install/
Doing updates for decades, this is a very common theme. Even if you
change one line of code to a flawless system, the odds start dropping
that it will remain that way the more lines of code you change. That is
why more people have trouble with a SP than with a single small update.
It is just the law of averages. Although anybody who has lots of
experience knows all of this stuff anyway.
Regarding OE compacting, we are talking about the same "issue"...
compacting was not "broken" however. Background compacting was the
problem, but compacting when closing OE or manually compacting while
offline worked fine.
I've never had a critical security update mess up a computer, unless
the computer was infected with a root kit or trojan. I'm not talking
about half a dozen computers, I'm talking about the neighborhood of
50 to 75. I never updated while running other programs, and always
disable the AV during update installation. Most of my clients did
not follow that procedure though, and they still never had update
problems. When people tell these tales of critical updates killing
their system, it has always been due to other issues in every case I
have seen. I'm curious.... when was the last time you checked you
system for root kits and trojans with Windows NOT loaded.... booting
from a Linux-based AV rescue CD?
I routinely repair other people infected systems all of the time, Glen.
I pull the drives out and scan them with a known clean system. And it
doesn't matter if you believe me or not. As all you have to do is to
scan Microsoft's KB list to know that updates can and does mess up an
OS.
List of fixes that are included in Windows XP Service Pack 3
http://support.microsoft.com/kb/946480
Just look how many of these from the SP2 update had screwed up many
systems. There are dozens of new problems that were caused by SP2
directly. Sure SP3 fixed some of them, but SP3 also caused some of their
own new problems. Although there is not going to be a SP4 to fix all of
the new problems from SP3, now is there?
Don't let XP Service Pack 3 hose your system
http://windowssecrets.com/top-story/dont-let-xp-service-pack-3-hose-your-system/
Windows XP SP3 Issues and Fixes Continued
http://techtalk.pcpitstop.com/2008/...p3-still-not-ready-news-flash-do-not-install/
Doing updates for decades, this is a very common theme. Even if you
change one line of code to a flawless system, the odds start dropping
that it will remain that way the more lines of code you change. That is
why more people have trouble with a SP than with a single small update.
It is just the law of averages. Although anybody who has lots of
experience knows all of this stuff anyway.