none
sfc /scannow found corrupt files, unable to fix; sfcdetails DOESN'T LIST THEM

    Question

  • http://support.microsoft.com/kb/929833

    Followed the above link, including running as admin:

    Ran sfc /scannow, getting corrupt files that could not be repaired as result, and grepped the log as follows:

     findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

    However, the resulting sfcdetails doesn't have any corrupt files listed, just a bunch of these triplets:

    2013-08-02 13:16:06, Info                  CSI    00000006 [SR] Verifying 100 (0x00000064) components
    2013-08-02 13:16:06, Info                  CSI    00000007 [SR] Beginning Verify and Repair transaction
    2013-08-02 13:16:11, Info                  CSI    00000009 [SR] Verify complete

    Nothing listed in the log as "cannot repair" -- So, what's the next step?  Was sfc /scannow lying?  Or is there some other way to figure out what the corrupt files are?


    Friday, August 02, 2013 7:39 PM

All replies

  • Also tried searching the CBS.log directly, and "cannot" wasn't anywhere in the file.  (Tried "Cannot" as well.)

    Is sfc itself broken in this case?

    Friday, August 02, 2013 7:52 PM