Some of the damaged files couldn't be repaired:
And, CBS.log says some errors similar to this one:
2015-11-26 16:02:04, Info CSI 00000442 Error - Overlap: Duplicate ownership for directory [l:23]"??C:WINDOWScastdvr" in component Microsoft-Media-Capture-Internal-BroadcastDVR, version 10.0.10586.11, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2015-11-26 16:02:07, Info CSI 00000486 Error - Overlap: Duplicate ownership for directory [l:40]"??C:ProgramDataMicrosoftWindowsCem" in component Microsoft-Foundation-Diagnostics-ErrorDetails, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2015-11-26 16:03:03, Info CSI 000007fd Error - Overlap: Duplicate ownership for directory [l:32]"??C:WINDOWSBrandingShellbrd" in component Microsoft-Windows-Branding-Shell-Professional, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
I just did /scannow twice but it keeps me showing this kind of errors. I don't have a clue about their meaning.
Have you put the error codes into Bing and searching or google.
Both them should find a link for you to read up on them or if anyone else has come up against the same problem.
Yep, I'm on it, but I don't find anything clear. I'm running the Dism /Online /Cleanup-Image /RestoreHealth thing, because one of the entries after my search pointed out and old post with similar issues.
Good sorry could not help you anymore other than to point you in that directionYep, I'm on it, but I don't find anything clear. I'm running the Dism /Online /Cleanup-Image /RestoreHealth thing, because one of the entries after my search pointed out and old post with similar issues.
It's fine, Sir .
What it means is it couldn't replace the corrupt files as local backup copies are also corrupt or missing.
Try running dism as described here DISM - Repair Windows 10 Image - Windows 10 blog rebooting and then running sfc again.
I'll try it, I'll be back with feedback.
Some results so far:
- Dism /Online /Cleanup-Image /CheckHealth: everything is alright.
- Dism /Online /Cleanup-Image /ScanHealth: so far so good.
- Dism /Online /Cleanup-Image /RestoreHealth: so far so good too.
So I'll going to reboot and do a sfc /scannow.
Dism should tell you if it fails... If it finishes OK then if there is still a problem with sfc you could copy the cbs log to desktop, zip it and upload it here...
Well, I think we don¡t need the log, hahaha. The sfc report says everything is good now:
I guess the DISM thing solved it? It's a mistery to me.
Anyway, with this tool I'm a little bit psyched. It's good to run the scf on a kind of routine, or only if we see that something is messed up? I ask this because I wasn't experiencing anything bad, but did it and found those lines.
