Windows 7: Running sfc /scannow find TONS of errors it can't fix.

My Windows 7 Ultimate install has been very stable. I noticed a Windows popup say " Windows explorer is resetting" which it did in a couple seconds and all was fine. I Googled about that and it said run "sfc /scannow" to fix file system errors, as a possible fix.

I ran SFC /scannow and it said it found corrupt files and was unable to fix all of them. I Googled more and found that the logs are stored in "CBS.log" and to look there for notes on the issue. I did that, but there is hundreds upon hundreds of lines of text most like this:

" 32: Move File: Source = [l:270{135}]"\SystemRoot\WinSxS\Temp\PendingRenames\98ae92744a32ce01ff610000c4038c0b.$$_syswow64_installshield_s etupdir_0021_5cf94704ecb98947.cdf-ms", Destination = [l:182{91}]"\SystemRoot\WinSxS\FileMaps\$$_syswow64_installshield_setupdir_0021_5cf94704ecb98947.cdf-ms"
33: Move File: Source = [l:270{135}]"\SystemRoot\WinSxS\Temp\PendingRenames\3ff098744a32ce0100620000c4038c0b.$$_syswow64_installshield_s etupdir_040c_5cf94f08ecb97c9f.cdf-ms", Destination = [l:182{91}]"\SystemRoot\WinSxS\FileMaps\$$_syswow64_installshield_setupdir_040c_5cf94f08ecb97c9f.cdf-ms"

POQ 222 ends.
2013-04-05 15:11:00, Info CSI 00000545 [SR] Verify complete
2013-04-05 15:11:00, Info CSI 00000546 [SR] Verifying 100 (0x0000000000000064) components
2013-04-05 15:11:00, Info CSI 00000547 [SR] Beginning Verify and Repair transaction
2013-04-05 15:11:00, Info CSI 00000548 Repair results created:
POQ 223 starts:

POQ 223 ends.
2013-04-05 15:11:00, Info CSI 00000549 [SR] Verify complete
2013-04-05 15:11:01, Info CSI 0000054a [SR] Verifying 100 (0x0000000000000064) components
2013-04-05 15:11:01, Info CSI 0000054b [SR] Beginning Verify and Repair transaction
2013-04-05 15:11:02, Info CSI 0000054c Hashes for file member \??\C:\Windows\SysWOW64\en-US\iernonce.dll.mui do not match actual file [l:32{16}]"iernonce.dll.mui" :
Found: {l:32 b:iEV74gMIa1ZAII5tbrto+OHdr7U3aOJe6zbe7tEkkUw=} Expected: {l:32 b:PnnWSLIKpR9gpFwhhHU1X83EBd23plDEr1aYW/ZDBeU=}
2013-04-05 15:11:02, Info CSI 0000054d [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:32{16}]"iernonce.dll.mui" from store
2013-04-05 15:11:02, Info CSI 0000054e Hashes for file member \??\C:\Windows\SysWOW64\en-US\iesetup.dll.mui do not match actual file [l:30{15}]"iesetup.dll.mui" :"

That is a very small slice of the log file and it means nothing to me.

I ran SFC /scannow a 2nd and 3rd time thinking there would be less problems, being as some of the files had been fixed, but if anything the log file was larger.

What do I do now?

Phenom II x4 955BE OCed (but stable for over a year) S.M.A.R.T. shows hard drives in good health and Mem test show no problem with memory.

Thanks,
Brad

Hello Brad,

Please go ahead and upload your sfcdetails.txt file created using OPTION THREE in the tutorial below. This will be only the SFC entries. I'll be happy to take a look at them.

SFC /SCANNOW Command - System File Checker

Who installed Ultimate ? Is it retail ?

OK here it is:

Yes, I build my own PC's and installed it myself.

Brad,

You had a few system files for Internet Explorer that SFC found to be corrupted, but SFC was able to successfully repair them.

Your log didn't have any files listed that it couldn't repair, so you are good to go.

Thank you,

I noticed all the problems being with IE also, but it still says it couldn't fix them all after running Scannow, why would that be? Also, why do I keep getting errors every time I run it?

I found others online that referred to IE9 as a/the problem causing errors with scannow that went away when they uninstalled it. I never use IE, only FF and Chrome, should/can I uninstall IE9 & 10?

Thanks again

No. You would not need to or should uninstall IE.

You may have been looking at the CBS.log file instead. Not all entries in it are for SFC.

In your SFCdetails.txt, it says that all files were successfully repaired.

If it says something different in the command prompt when your run the sfc /scannow command, then please post a screenshot showing the full output of the command prompt.

This is what it has said after every run of scannow:

And here is an updated sfcdetails.txt file showing the last run of scannow: