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?

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