Main Forum > General Computer Support

CBS log file

<< < (4/6) > >>

Boggin:
While I've only had one occasion where an offboot sfc /scannow reported it was unable to repair all files, wouldn't that replace the missing files, or has your curiosity gotten the better off you  :smiley:

Shane:

--- Quote ---or has your curiosity gotten the better off you
--- End quote ---

Always :-)

But in this case, the other person I helped had corrupt files in there and yet sfc reported all files where fine. sfc doesnt scan all the files. A lot of those files in that folder also get added by windows updates. So I dont think sfc covers everything because he ran sfc 4 times on the system and each time it came back saying no corrupt files found.

But sure enough I found the corrupt files, replaced them and it fixed him. Not to mention sfc doesnt check anything in the registry and that folder contents should match a registry section.

So a tool for this can be a big big help. So, I am making one :-)

Shane

Boggin:
I always thought that sfc in checking the System did check the registry as that is the "engine" of Windows.

It's obviously finding something wrong in this case whereas the chkdsk doesn't and I've been led to believe that chkdsk looks at more than just the system files ?

Shane:
chkdsk scans all files, but not their data, thats what the /r does and why it takes longer. chkdsk checks the files system and the files reported in the mft table. So it makes sure security is in check and pointers to the file locations and such are correct. Very different than sfc. chkdsk is checking the file system not the files and what is corrupt or not.

Shane

Boggin:
I was just using chkdsk in its general term without specifying any switches.

Navigation

[0] Message Index

[#] Next page

[*] Previous page