1. Joined : Dec 2015
    Posts : 4
    Windows 10 64-Bit
       17 Aug 2016 #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?
    SFC found corrupt files that cannot be repaired but log file is clean Attached Files
      My System SpecsSystem Spec


  2. Joined : Jan 2015
    UK, Midlands
    Posts : 6,526
    Win 10 Pro (1607)
       18 Aug 2016 #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 System SpecsSystem Spec


  3. Joined : Dec 2015
    Posts : 4
    Windows 10 64-Bit
       18 Aug 2016 #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 System SpecsSystem Spec


  4. Joined : Jan 2015
    UK, Midlands
    Posts : 6,526
    Win 10 Pro (1607)
       19 Aug 2016 #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 System SpecsSystem Spec


 


Similar Threads
Thread Forum
BSOD & corrupt files found
Hi guys, new here. Recently I've gotten 3 BSOD's within the past week, with the message "Your PC ran into a problem and needs to restart. We're just collecting some error info, and then we'll restart for you." I also ran the command SFC...
BSOD Crashes and Debugging
Found corrupt files but not fixed
Hi there, I was having a problem with my start button on windows 10, so i decided to go ahead and do sfc /scannow. It said it found corrupt files, but could not repair them, so i went ahead and done DISM /Online /Cleanup-Image /RestoreHealth....
Installation and Setup
Solved WIndows resource protection has found some corrupt files... No Fix
Hello, I have tried to run sfc/ scannow and it gives me the notification that: WIndows resource protection has found some corrupt files but is unable to fix some of them. Details are included in the CBS.log. Is it ok to post the log here so...
Performance & Maintenance
Found corrupt files (SFC scan)
Was on Win 8.1 and found nothing of the sort "windows did not find any integrity violations". Upgraded to windows 10 and boom "Windows Resource Protection found corrupt files but was unable to fix some of them." Full DISM log:...
Performance & Maintenance
Windows Resource Protection found corrupt files.
Hi, just wanted to know what should one do if one gets the error and how does one troubleshoot it properly? I looked up the log on my system but it's just a really big lump of text.
Performance & Maintenance
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 10:26.
Find Us
Twitter Facebook Google+



Windows 10 Forums