SFC identifies possibley corrupt files

I ran System File Checker today (first time in about 2 months) and it identified approximately 28 .exe and .dll file as "possibly corrupted" and asked if I wanted to verify, replace or ignore. I have chosen ignore for now. These files are in various system directories and program file directories. Examples of the files are:
dxdiag.exe; msoe.dll (OE file); mixer.exe; mfc70.dll; rave.dll (Quicktime file) and on and on. All programs are working OK and Win98SE is running smoothly, well as smooth as it gets.

I am leaning towards the "possibly corrupted" and being a false negative so before I do anything drastic like replace or verify I would like some suggestions/direction. I don't want to replace all these files as probably some of them (or most) are newer versions than the originals.

Never had this many show up before when SFC has been run.

 

Sfc in 98, I believe, and someone will correct me if I'm wrong, I'm sure, verifies files from a database it has created from a previous scan. In other words, if you run sfc, and then install a Windows update, and run sfc again, it will identify the newly installed exe's as "possibly corrupt" since they do not correspond to the characteristics saved from the previous scan.

It should be run immediately after 98 is installed so that a baseline of genuine Windows files will be created.

So, sfc should be run when you are sure that all files are intact, and after any major upgrades or Windows updates, in order to update the database of scanned files, or you will get many false positives such as you have experienced.

In short, the use of sfc in 98 is so time-consuming and flawed a process, it is hardly worth doing unless the stability and security of a system are your responsibility and you are being paid for this menial task.

Easier to upgrade to ME and have Windows File Protection handle it for you.

 

Agreed.
The only way to get true readings from SFC is to run it before and after every install and uninstall, otherwise you will get false readings about missing and/or corrupted files.

Strictly use it as the means to restore (when necessary) files from the Windows CD or CAB files.

 

Thanks Abraxas and Whitphil, that's what I figured was going on. Will follow your advice. Will be away from home for a couple of days so will tackle this when I get home.

 

Most of the filenames mentioned are files that are have been updated since Win98 was introduced. I think you used the additional options to check for Changed files, under the Settings button. This would have produced the results you have.
In default mode, it should have just noted the files as updated.
SFC creates a log file, C:\Windows\Sfclog.Txt. Since SFC appends it's log to the file each time it is run, you end up with a history of what files were updated, deleted or added.
BTW, if the file SetupX.Dll is noted as corrupted, you can replace it.

 

markp62: SFC was run in the normal mode, Change or altered files box was unchecked. I usually run SFC weekly but for some reason haven't run it since before Christmas. Have updated the verify option on the supposedly corrupt files and all seems to be running OK. Had a look at the Sfclog.txt and only shows the last scan. Overwrite box was checked. SetupX.dll was NOT one of the files shown as corrupted.

 

EXCELLENT choice to keep it that way.

Much better choice than my Grandaughter made. ( against my advice ) She was not having any problems either. But she thought a Friend knew better than Grandpa did.

Her next FORCED choice was a re-install of Windows. AND a lot of her software.

BillyBob

PS.
Guess how Grandpa learned.

BB