SFC found corrupt files that cannot be repaired but log file is clean


  1. Posts : 5
    Windows 10 64-Bit
       #1

    SFC found corrupt files that cannot be repaired but log file is clean


    Hi,
    iam running sfc /scannow on a fresh windows 10 Pro 1607 installation and get every time the same output: found corrupt files...cannot be repaired... but when i analyze the cbs logfile there is no match when searching for "cannot repair".

    dism /online /cleanup-image /checkhealth -> OK
    dism /online /cleanup-image /scanhealth -> OK
    dism /online /cleanup-image /restorehealth -> OK

    when i run sfc /scannow /offbootdir=c:\ /offwindir=c:\windows in boot environment, it didn't find any corruptions

    i ran sfc /scannow in safe mode serveral times and created a sfcdetails.txt file of the whole cbs.log file, but there same output: found corrupt files...cannot be repaired...
    And still no matches when searching for "cannot repair" string, see attach.

    Did someone observe the same behaviour? Should i ignore this?
      My Computer

  2. dalchina's Avatar
    Posts : 29,882
    Win 10 Pro (1903)
       #2

    There are plenty of error reports about duplicate ownership.. search for 'error'.

    Forgive the obvious question - is your PC misbehaving in some manner, or are you running sfc out of curiosity?
      My Computers


  3. Posts : 5
    Windows 10 64-Bit
    Thread Starter
       #3

    Yeah thats right, but its normal and a known issue with sfc itself, you can read here: http://answers.microsoft.com/en-us/w...0-49ac71e27706

    Try it yourself: Do a clean install with Windows 10 Pro in a virtual machine (8 minutes) and run sfc /scannow...you sould get the same warnings/errors.

    These errors are not the problem, cause they are signed as "Info" and not as "Error". PC is running good, no problems yet. But its curious that sfc fails -.-

    Edit: I think it will be difficult to found a solution, cause i forget to say that i customized the installation of my Windows Pro 1607 image (.wim file). I removed a lot of packages with an unofficial hack. Although it's curious that sfc doesn't log specific informations to locate the real problem
      My Computer

  4. dalchina's Avatar
    Posts : 29,882
    Win 10 Pro (1903)
       #4

    Well, my sfc scan fails- but I have modified system icons so some 77 look like Win 7, and I've added support for old hlp file format. So it fails on those of course.

    So long as you know what you've modified and can make an appropriate decision on the log file, that's the best one can do.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:28.
Find Us




Windows 10 Forums