Windows 10: 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 *Redface

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 reports corrupt files that cannot be repaired

Thanks, Riel Alc.

Yes, I've installed Windows build updates. The CBS.log is at
CBS Log.

(By the way, I realize what I said about DISM never working without an image file might not apply to those new-computer owners who've never used Windows Update to install a new build.)

 

SFC reports corrupt files that cannot be repaired

Thank you and sorry for the late reply.

"Cannot repair member file [l:9]'MSDTC.LOG' of Microsoft-Windows-COM-DTC-Runtime, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch" - This entry indicates that the file content does
not match the operating system definition for the file. In this situation, the SFC.exe program cannot repair the file.

Since DISM cannot also repair the said file, you may perform an in-place upgrade to repair all corrupted system files. For the steps, please check
PaulSey...'s
Forum Article.

Please post back with the result for further assistance.

 

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?

 

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 *Sad

 

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.