sfc /scannow and corrupted files

TUF_0511

Reputable
Oct 5, 2016
12
0
4,510
Hello,

I did a clean installation of Windows 10 yesterday (using official Fall Creators ISO). I did it because the every time I run sfc /scannow, it always finds corrupted files and "successfully repaired them". Next time it finds them again and the command does not really fix them. I have CBS.log file (output of sfc /scannow command) and I I'll be grateful if someone helps me to interpret the log.

CBS.log - http://www77.zippyshare.com/v/AzamPG09/file.html


 
Solution
So i know this isn't a satisfactory answer and doesn't explain why the SFC fails, but if PC is working, I wouldn't worry about it. It might be the version of SFC is out of date and might be updated in a upcoming patch... maybe, it took MS a few months to fix DISM when they broke it after releasing Anniversary edition.

I don't know but i don't run SFC unless I have to.

Colif

Win 11 Master
Moderator
right click start button
choose powershell (admin)
copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter

this command should help fix SFC. If it completes without any errors, re run SFC again and restart PC.

It has been noted before that SFC can find corrupted files on a brand new install, this seems "normal" though bizarre at same time. So this might not show a problem.
 

TUF_0511

Reputable
Oct 5, 2016
12
0
4,510


I already did RestoreHealth, but it did not solve the problem. I tried several times.
 

Colif

Win 11 Master
Moderator
ok, i won't say I am expert on reading cbs log but i see what i can figure out
'
000006fb Error: Overlap: Duplicate ownership for directory \??\C:\Windows\bcastdvr in component Microsoft-OneCore-Multimedia-BroadcastDVR, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
00000731 Error: Overlap: Duplicate ownership for directory \??\C:\Windows\bcastdvr in component Microsoft-Media-Capture-Internal-BroadcastDVR, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

00000756 Error: Overlap: Duplicate ownership for directory \??\C:\Program Files\Common Files\Microsoft Shared\Ink in component Microsoft-Shared-Ink-Directory, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

0000075e Error: Overlap: Duplicate ownership for directory \??\C:\Windows\SystemApps\Microsoft.Windows.AppRep.ChxApp_cw5n1h2txyewy\pris in component Microsoft-Windows-AppRep-ChxApp.appxmain.resources, version 10.0.16299.15, arch amd64, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}

00000767 Error: Overlap: Duplicate ownership for directory \??\C:\Windows\SystemApps\Microsoft.PPIProjection_cw5n1h2txyewy\pris in component Microsoft-PPIProjection.AppxMain.Resources, version 10.0.16299.15, arch amd64, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}

00000778 Error: Overlap: Duplicate ownership for directory \??\C:\Windows\SystemApps\Microsoft.Windows.AssignedAccessLockApp_cw5n1h2txyewy\pris in component Microsoft-Windows-AssignedAccessLockApp.AppxMain.Resources, version 10.0.16299.15, arch amd64, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}

000007ff Error: Overlap: Duplicate ownership for directory \??\C:\Windows\Help\Windows in component Microsoft-Windows-Assistance-CollectionFiles-Help, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2017-11-05 21:18:21, Info CSI 00000800 Error: Overlap: Duplicate ownership for directory \??\C:\Windows\Help\Windows\IndexStore in component Microsoft-Windows-Assistance-CollectionFiles-Help, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2017-11-05 21:18:21, Info CSI 00000801 Error: Overlap: Duplicate ownership for directory \??\C:\Windows\Help\Windows\ContentStore in component Microsoft-Windows-Assistance-CollectionFiles-Help, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2017-11-05 21:18:21, Info CSI 00000802 Error: Overlap: Duplicate ownership for directory \??\C:\Windows\Help\OEM in component Microsoft-Windows-Assistance-CollectionFiles-Help, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2017-11-05 21:18:21, Info CSI 00000803 Error: Overlap: Duplicate ownership for directory \??\C:\Windows\Help\OEM\IndexStore in component Microsoft-Windows-Assistance-CollectionFiles-Help, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2017-11-05 21:18:21, Info CSI 00000804 Error: Overlap: Duplicate ownership for directory \??\C:\Windows\Help\OEM\ContentStore in component Microsoft-Windows-Assistance-CollectionFiles-Help, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2017-11-05 21:18:21, Info CSI 00000805 Error: Overlap: Duplicate ownership for directory \??\C:\Windows\Help\Help in component Microsoft-Windows-Assistance-CollectionFiles-Help, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2017-11-05 21:18:21, Info CSI 00000806 Error: Overlap: Duplicate ownership for directory \??\C:\Windows\Help\Corporate in component Microsoft-Windows-Assistance-CollectionFiles-Help, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
and so on..

now one fix I found for this is running the extended version of DISM. See here:

Download a copy of the win 10 iso from Here - create ISO by telling it you want to make DVD - and then mount that ISO in file explorer (see Here) and then copy paste the below command into command prompt (admin)

DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess
Where "X" is the drive letter where the ISO is located. Simply change the "X" to the correct drive letter

Spacing needs to be exact or it won't work.

Found fix here: https://www.tenforums.com/performance-maintenance/50850-sfc-scannow-error-overlap-duplicate-ownership-directory.html
 

TUF_0511

Reputable
Oct 5, 2016
12
0
4,510


Thank you. I tried that too few days ago but problem still there
 

Colif

Win 11 Master
Moderator
So i know this isn't a satisfactory answer and doesn't explain why the SFC fails, but if PC is working, I wouldn't worry about it. It might be the version of SFC is out of date and might be updated in a upcoming patch... maybe, it took MS a few months to fix DISM when they broke it after releasing Anniversary edition.

I don't know but i don't run SFC unless I have to.
 
Solution