It's an programming oversight - .
SFC (System File Checker) is a function of WFP (Windows File Protection).
It quietly maintains system modules to a correct, expected version. Unless a
user has overridden a replacement, it's unlikely you'll have any version
errors.
Sometimes, I believe this is over used as a diagnostic tool or process.
There is a hierarchy to where XP goes to replace these system components.
Part of the search tree depends on ServicePack levels on how XP was
installed originally (CD, Network/Drive path). Also a few Registry Keys may
affect how SFC works. Actually, when you run SFC /ScanNow it does do
a version check, but mainly repopulates the DllCache folder, which is the
1st
search point for SFC.
- C:\Windows\System32\DllCache
- C:\Windows\ServicePackFiles
-i386 (on Network or local Drive)
-Original CD-ROM
Registry Keys that affect SFC:
Hkey_Local_Machine\Software\Microsoft\Windows\CurrentVersion\Setup
CDInstall (Value 1, original install from CD-ROM, 0 = Drive path)
SourcePath (Usually a Drive Letter designation -likely your CD/DVD drive)
ServicePackSourcePath (Where the ServicePackFiles resides)
The problem comes from the search traversing the different locations and not
finding the version it expects and it ends up at the CD-ROM point which does
not have the latest ServicePack content.