[SOLVED] SCF Scannow Fails With Numerous Duplicate Ownership Errors

IsoQuantic

Member
Joined
Jul 16, 2016
Posts
19
Location
Chandler, AZ
I am getting a SFC scan failure at 24 percent.

Attached is CBS log following powershell mount of Mount-DiskImage -ImagePath "O:\Win10_1607_English_x64.iso" and subsequent successful completion of Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:1 /limitaccess

See attached log: View attachment CBS Log DISM RestoreHealth.log

Below is CBS log after running the above then this: sfc /scannow

View attachment CBS After SFC run.zip

As can be seen from the log above, the majority of errors resemble duplicate ownership errors, for example:

Error - Overlap: Duplicate ownership for directory \??\C:\WINDOWS\SystemApps\ContactSupport_cw5n1h2txyewy\pris in component Microsoft-Windows-ContactSupport.AppxMain.Resources, version 10.0.14393.447, arch amd64, culture [l:14]'ca-ES-valencia', nonSxS, pkt {l:8 b:31bf3856ad364e35}

Error - Overlap: Duplicate ownership for directory \??\C:\WINDOWS\Inf\BITS in component Microsoft-Windows-Bits-Perf, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

Error - Overlap: Duplicate ownership for directory \??\C:\WINDOWS\resources\themes\aero in component Microsoft-Windows-aero, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

Any help in resolving this issue is appreciated.
 
All of the Duplicate ownership for directory errors can be ignored. These are normal and expected. To fix the actual issue in the log I will need you to do the following so I can gather more info.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and run sfc /scannow just like you have in the past.
3. Stop Process Monitor as soon as sfc fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log.
 
All of the Duplicate ownership for directory errors can be ignored. These are normal and expected. To fix the actual issue in the log I will need you to do the following so I can gather more info.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and run sfc /scannow just like you have in the past.
3. Stop Process Monitor as soon as sfc fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log.

Attached is the CBS log:
View attachment CBS-IsoQuantic.zip

For reference, attached is a file extracting errors shown from the CBS log:
View attachment sfcdetails-IsoQuantic.zip

For the larger procmon log file use this link:
Logfile-Isoquantic.zip - Google Drive

Thank you.
 
Please do the following.

Step#1 - SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please
 

Attachments

Please do the following.

Step#1 - SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please
The results are shown below:

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-12-13 12:17:06.149
Microsoft Windows 10 Build 14393 - amd64
Using .txt script file at C:\Users\Patrick\Desktop\SFCScript.txt [0]

RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.14393.0_none_46c76e6076b59fe9.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.14393.0_none_46c76e6076b59fe9.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_10.0.14393.0_none_46c76e6076b59fe9.
RegistryScript:: directive completed successfully.


Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 11 datablocks.
Finish time: 2016-12-13 12:17:06.477
Script hash: mhaqEjQyIw805PL8FTrInyewtrVdUXNGgLIcRCFSIwY=
 
Thanks. Please do the following.

SFC Scan
1. Right-click on the Start
w8start.png
button and select Command Prompt (Admin)
2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
sfc /scannow

3. Once it finishes, copy and paste the following into the command-prompt window and press Enter.
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

4. Once this has completed please go to your Desktop and you will find CBS.txt => Right-click on this file and choose Send To...Compressed (zipped folder). Please upload this zipped file CBS.zip to this thread

Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Thanks. Please do the following.

SFC Scan
1. Right-click on the Start
w8start.png
button and select Command Prompt (Admin)
2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
sfc /scannow

3. Once it finishes, copy and paste the following into the command-prompt window and press Enter.
copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

4. Once this has completed please go to your Desktop and you will find CBS.txt => Right-click on this file and choose Send To...Compressed (zipped folder). Please upload this zipped file CBS.zip to this thread

Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

The CBS log is attached:
View attachment CBS.zip

The sfc /scannow command completed at 100% this time. I still note numerous directory ownership errors. You state these are normal and expected. Can you explain what is going on behind the scenes that causes these errors?
 
I still note numerous directory ownership errors. You state these are normal and expected. Can you explain what is going on behind the scenes that causes these errors?
It's checking the permissions on various directories and reporting an issue when there really isn't. I personally think it's a bug. The only time you need to worry about an Error is if it is reported in the second column of the log file. Everywhere else it shows error can be ignored. Take care.

Capture.JPG
 
I still note numerous directory ownership errors. You state these are normal and expected. Can you explain what is going on behind the scenes that causes these errors?
It's checking the permissions on various directories and reporting an issue when there really isn't. I personally think it's a bug. The only time you need to worry about an Error is if it is reported in the second column of the log file. Everywhere else it shows error can be ignored. Take care.
Thank you for your help, Brian. Much appreciated.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top