Sfc/scannow error repair

Errors are reported which sfc cannot repair. I found some errors in the CBS.log. How do I tell if these are the (only) errors and how do I repair them? This is something of which I have no knowledge or experience.

2018-11-29 13:26:19, Info CSI 000046ef Error: Overlap: Duplicate ownership for directory \??\C:\WINDOWS\SysWOW64\setup\en-US in component Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.17134.1, arch Host= amd64 Guest= x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
2018-11-29 13:26:19, Info CSI 000046f0 Error: Overlap: Duplicate ownership for directory \??\C:\WINDOWS\SysWOW64\en-US in component Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.17134.1, arch Host= amd64 Guest= x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
2018-11-29 13:26:20, Info CSI 000046f1 Error: Overlap: Duplicate ownership for directory \??\C:\WINDOWS\Resources\Themes\aero\en-US in component Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.17134.1, arch Host= amd64 Guest= x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
2018-11-29 13:26:20, Info CSI 000046f2 Error: Overlap: Duplicate ownership for directory \??\C:\Program Files (x86)\Common Files\System\en-US in component Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.17134.1, arch Host= amd64 Guest= x86, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}

As dalchina posted, if needed, the in place upgrade repair should fix the problems.
If it does not fix the problems then you could perform a reset save files or equivalent.

1) Open administrative command prompt and type or copy and paste:
2) dism /online /cleanup-image /restorehealth
3) sfc /scannow
4) chkdsk /scan
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

Some of these steps failed so I will try again

zbook said:

As dalchina posted, if needed, the in place upgrade repair should fix the problems.
If it does not fix the problems then you could perform a reset save files or equivalent.

1) Open administrative command prompt and type or copy and paste:
2) dism /online /cleanup-image /restorehealth
3) sfc /scannow
4) chkdsk /scan
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

C:\Windows\system32> dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.1

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>chkdsk/scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
90624 file records processed.
File verification completed.
3376 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
135 reparse records processed.
126394 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
135 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
17886 data files processed.
CHKDSK is verifying Usn Journal...
36875488 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

81811455 KB total disk space.
13559596 KB in 69231 files.
56360 KB in 17887 indexes.
0 KB in bad sectors.
198179 KB in use by the system.
65536 KB occupied by the log file.
67997320 KB available on disk.

4096 bytes in each allocation unit.
20452863 total allocation units on disk.
16999330 allocation units available on disk.

C:\Windows\system32>


It all looks good but the CBS.log still shows many Duplicate Ownership errors.

This is with a brand-new install, 32bit. I am seeing this on 3 different PCs. I have a customer that thinks this is a problem but I have no answers for this.

At first, the "SFC/Scannow" did report errors it cant repair. and said to check the CBS.log
Now, after the "dism /online /cleanup-image /restorehealth", it says no problems BUT the CBS log still shows the errors.

Open administrative command prompt and copy and paste:


findstr /c:"[SR]" %windir%\Logs\cbs\cbs.log >%userprofile%\desktop\sfcdetails.txt

Find the new file on the desktop > zip > post a share link into the thread

For any concerns about the operating system you can perform an in place upgrade repair with the identical iso or fix registry problems with an iso for 1809.

If there is no corruption or performance problems then there is no need to modify the findings in the logs.

We see many problems in the event logs that we do not fix.
They are reported findings.
Only those that are significant are troubleshooted.

When viewing Panther logs there are lots of entries that do not need to be troubleshooted.

If you post a BETA log collector zip if there are any significant finding they can be troubleshooted:
BSOD - Posting Instructions - Windows 10 Forums