sfc /scannow issues with XP Hotfixes

[Guest]

Whenever I run the command sfc /scannow on a Windows XP Home or Professional
system, ( yes, just in case it's mentioned, I use the correct retail or OEM
XP/SP2 discs when prompted for them ) it corrupts, damages or replaces some
of the security hotfixes, for example, and especially : KB902400, KB914440 (
and sometimes a few others ) which causes some system wide instabillity, and
a whole host of other problems.

I then delete these previously installed hotfixes and the majority of their
left-overs, then go to Windows Update Site, re-download and re-install these
Hotfixes, and this usually, ( but not always, without some further tweaking
on my part ) solves most of the problems left after running sfc /scannow.

This Windows Article references this problem on Windows 2000 systems, but
does not mention anything about XP :
http://support.microsoft.com/default.aspx/kb/814510

So, how do I prevent this issue from happening whenever ( or everytime ) I
run the command ( sfc /scannow ) ? ... and has anyone else run across this
issue and have a viable solution, without me always having to do what I've
already mentioned above ?

Thanks in advance and my best regards,
Fierce1

 

[Guest]

No, probably not. You are going to have to use another way to repair your
system. Some form of backup would be the best. If you are consistantly
letting some corrupting force into your system, you should prepare for the
worst. Upgrading to Vista would be worth considering.

 

[Guest]

Thanks Mark, but your assumption that I'm letting corrupting forces onto my
OWN system, ( which is backed-up extensively and frequently, and apps,
programs and/or drivers are thoroughly tested by me using virtual Linux or
Windows OS's, before attempting installs on my OWN system) is totally
incorrect.

These repairs, and the simple use of ' sfc/scannow ', are usually done and
were attempted on several of my friends, family, clients and/or colleagues
systems, and every blue moon, on one of my own older test boxes, because it's
a quicky way, or it has been in the past, to solve several simple Windows
issues without complicated trouble-shooting ... also some of these corrupting
forces, that I usually run across during some of these cyber forays of mine,
usually derive from installing faulty or not extensively tested drivers
and/or apps, un-safe surfing and e-mail practices, and sometimes the
incorrect or mistaken deletion of necessary files by nefarious entities
and/or by novice and sometimes experienced operators such as myself.

As mentioned before, 'sfc/scannow' is just a simple step or tool developed
(although out-dated for some, and maybe by me now) for the express purpose to
help replace or repair missing or corrupted files on Windows OS's before
more extensive delving into one's system is attempted.

Soooo, the point of my question was to find out why these ' sfc/ scannow '
issues are occurring now, but I've come to the conclusion and the assumption
that this tool is outdated and no longer useful now ( except for older OS's)
because of the numerous and extensive use of Security Hot fixes and Service
Pack files, etc, etc, now needed and used by the XP OS ... and your
statement, " Upgrading to Vista would be worth considering.", is not a viable
solution for many, and personally I would wait to all the bugs are worked out
of Vista before replacing XP, and that could be a long wait.

Again thanks for your attempt at my query and best regards,
Fierce1