SFC Fail to Repair Files; Don't Understand Log CBS.log

I am new to these forums so I hope this is the right place to post this. I'm pretty good with computers I think...The scan will not complete in windows, says service cannot be started. I am able to complete it offline in recovery environment, but it fails to repair the files it finds. I don't understand the log results. This all started I think when my old hard drive began to crash and I had bad sectors in it. I transferred win7 to a new SSD drive (which is amazing!). Windows runs fine but there are corrupt system files for some reason and I would like to resolve. Only pay attention to 7/14 entrees..there are more on 7/15 don't know why the scan was done on 7/14. Please see attached.

I don't know what is a healthy looking log file but the scan results said system files corrupt and some could not be repaired.

Thanks!

Your log appears to be incomplete. Here are the steps I usually give for SFC:

Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.

Hmm well it won't run in windows says (I forget exactly) service won't start. Trusted installer service is running. I tried the sfcdetail thing and it wrote a blank file lol. This was all offline in recovery environment though! I am running with admin cmd and all. The original cmd.exe was corrupt so I copied one from c:\windows\syswow64. This doesn't affect it does it?

Does sfcdetail.txt have different info or filtered info than CBS.log?

I can try the scan offline couple times but is a restart needed since its offline?

Weird stuff.

If you are unable to run in Windows, can you please post a screenshot of the error? Screenshots and Files - Upload and Post in Seven Forums.


Running offline does not seem to generate the log from my experience. Getting the file from another source other than what the tutorial says will also prevent the information from being given to us properly.

Screenshot attached.

Getting what file from another source? You mean cbs.log vs sfcdetails.txt or cmd.exe?

Thanks!

Ah, I misunderstood. I thought you copied the log from syswow64. I see it was just the cmd.exe. I am actually not sure what problems that might cause...

Anyway, the error you get indicates some pretty bad corruption on the system. I would recommend a repair install.

Repair Install Windows 7.

Steps 1-3 and 5-7 of Clean Reinstall - Factory OEM Windows 7 will help you get installation media, backup any important files (just in case), and obtain your license keys for software (just in case) and the Windows license key (you will need this key).

I assume it was the same cmd.exe. It seems to do the same thing lol.

That's the thing it doesn't do anything weird system boots and acts fine! So I'm not too motivated to do a repair install sounds like a pain. Was hoping I could just overwrite whatever is failing outside of windows (such as trusted installer service) so the scan will run properly. I don't know what to overwrite though.

But if sfc cannot repair it offline then maybe sfc related components itself are damaged? I wish I could fix just them. Repair install sounds like it might make a lot of errors.

Since the scan does work in recovery environment is interesting. I could try copying cmd.exe from a good computer to see if it changes anything. Does 64 or 32 bit matter?

Ha! I figured out the problem; the cmd.exe indeed is 32 bit cmd processor; I overwrote the 64bit one. That's why sfc does not work. I download TCC some third party command processor the 64bit version and the scan is working now :).

Do you know where I can download my proper c:\windows\system32 64 bit cmd.exe? I do not have a windows 7 64 bit iso though I suppose I could download one.

The one in \syswow64 is 32 bit..very misleading lol