From the KB
If you run the Windows File Checker utility (SFC) with the /SCANNOW
switch (sfc /scannow) after you install Windows 2000 hotfixes or
security updates, updated or patched files that were installed may later
be overwritten by previous versions of those files.
To resolve this issue, install Windows 2000 SP4. Post-SP4 hotfixes and
security patches are registered in such a way that SFC detects them.
This problem does not occur on computers that run Windows 2000 SP4 or
later. For additional information, click the following article number to
view the article in the Microsoft Knowledge Base:
Ok, it appears with SP-4 running sfc /scannow will recognize 'current'
(newer) files than from the (original) install CD.
So, if I run it and it asks me for my original CD? That means it needs
an original file, a file that has not changed since the original? OK so far?
Meaning? After SP4 -- If I run sfc /scannow and it asks me for the
original it is *not* pulling an older file than one which is needed off
the original CD?
So? If a post install (update, hotfix..) file is lost or corrupt ... how
does sfc /scannow get the file needed if it isn't on the original CD?
That is, when I run sfc /scannow (now) & it asks for the original CD --
I assume an 'original' file is needed - but that doesn't seem to
account for files that are missing and didn't come from the original CD.
So,
1. How are the files not on that CD 'sought' (in the scan) and
2. How does the operation 'know' where to find them so the user can
replace them?
In other words? It seems the above KB explains that with SP4 sfc
/scannow will detect the files that are on the system -- what about
detecting and replacing the files after the original install?
Michael
|
Similar Threads
