Windows 10: sfc/scannow returns error

Expected: {l:32 ml:33 b:2ee5d65c2b2c70e4ad5b3a5fc497f8714f83ea0ce589e5ef3d7bf777ef3736a3}.
Actual: {l:32 b:05033d64e96050953e94f1dc88a7af154eed541354eb84b4b5c026efb2cbd4a4}.
2020-06-20 14:07:12, Info CSI 0000002b [SR] Cannot repair member file [l:12]'Hydrogen.dll' of Microsoft-Analog-H2-HydrogenRT, version 10.0.19041.330, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-06-20 14:07:13, Info CSI 0000002c Hashes for file member [l:12]'Hydrogen.dll' do not match.
Expected: {l:32 ml:33 b:2ee5d65c2b2c70e4ad5b3a5fc497f8714f83ea0ce589e5ef3d7bf777ef3736a3}.
Actual: {l:32 b:05033d64e96050953e94f1dc88a7af154eed541354eb84b4b5c026efb2cbd4a4}.
2020-06-20 14:07:13, Info CSI 0000002d [SR] Cannot repair member file [l:12]'Hydrogen.dll' of Microsoft-Analog-H2-HydrogenRT, version 10.0.19041.330, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-06-20 14:07:13, Info CSI 0000002e [SR] This component was referenced by [l:124]'Microsoft-Windows-Holographic-Desktop-Analog-Package~31bf3856ad364e35~amd64~~10.0.19041.330.5a35e80213b827824f1c7dbf75396bb7'
2020-06-20 14:07:13, Info CSI 0000002f Hashes for file member [l:12]'Hydrogen.dll' do not match.
Expected: {l:32 ml:33 b:2ee5d65c2b2c70e4ad5b3a5fc497f8714f83ea0ce589e5ef3d7bf777ef3736a3}.
Actual: {l:32 b:05033d64e96050953e94f1dc88a7af154eed541354eb84b4b5c026efb2cbd4a4}.
2020-06-20 14:07:13, Info CSI 00000030 Hashes for file member [l:12]'Hydrogen.dll' do not match.
Expected: {l:32 ml:33 b:2ee5d65c2b2c70e4ad5b3a5fc497f8714f83ea0ce589e5ef3d7bf777ef3736a3}.
Actual: {l:32 b:05033d64e96050953e94f1dc88a7af154eed541354eb84b4b5c026efb2cbd4a4}.
2020-06-20 14:07:13, Info CSI 00000031 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\\Hydrogen.dll; source file in store is also corrupted
2020-06-20 14:07:13, Info CSI 00000032 CSIPERF - FilePI Queue 454ms
2020-06-20 14:07:13, Info CSI 00000033 [SR] Verify complete
2020-06-20 14:07:13, Info CSI 00000034 [SR] Verifying 100 components
2020-06-20 14:07:13, Info CSI 00000035 [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:14, Info CSI 00000036 [SR] Verify complete
2020-06-20 14:07:14, Info CSI 00000037 [SR] Verifying 100 components
2020-06-20 14:07:14, Info CSI 00000038 [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:15, Info CSI 00000039 [SR] Verify complete
2020-06-20 14:07:15, Info CSI 0000003a [SR] Verifying 100 components
2020-06-20 14:07:15, Info CSI 0000003b [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:15, Info CSI 0000003c [SR] Verify complete
2020-06-20 14:07:15, Info CSI 0000003d [SR] Verifying 100 components
2020-06-20 14:07:15, Info CSI 0000003e [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:16, Info CSI 0000003f [SR] Verify complete
2020-06-20 14:07:16, Info CSI 00000040 [SR] Verifying 100 components
2020-06-20 14:07:16, Info CSI 00000041 [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:17, Info CSI 00000042 [SR] Verify complete
2020-06-20 14:07:17, Info CSI 00000043 [SR] Verifying 100 components
2020-06-20 14:07:17, Info CSI 00000044 [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:19, Info CSI 00000045 [SR] Verify complete
2020-06-20 14:07:19, Info CSI 00000046 [SR] Verifying 100 components
2020-06-20 14:07:19, Info CSI 00000047 [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:19, Info CSI 00000048 [SR] Verify complete
2020-06-20 14:07:20, Info CSI 00000049 [SR] Verifying 100 components
2020-06-20 14:07:20, Info CSI 0000004a [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:20, Info CSI 0000004b [SR] Verify complete
2020-06-20 14:07:20, Info CSI 0000004c [SR] Verifying 100 components
2020-06-20 14:07:20, Info CSI 0000004d [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:21, Info CSI 0000004e [SR] Verify complete
2020-06-20 14:07:21, Info CSI 0000004f [SR] Verifying 100 components
2020-06-20 14:07:21, Info CSI 00000050 [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:22, Info CSI 00000051 [SR] Verify complete
2020-06-20 14:07:22, Info CSI 00000052 [SR] Verifying 100 components
2020-06-20 14:07:22, Info CSI 00000053 [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:23, Info CSI 00000054 CSIPERF - FilePI Queue 174ms
2020-06-20 14:07:23, Info CSI 00000055 [SR] Verify complete
2020-06-20 14:07:23, Info CSI 00000056 [SR] Verifying 100 components
2020-06-20 14:07:23, Info CSI 00000057 [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:24, Info CSI 00000058 [SR] Verify complete
2020-06-20 14:07:24, Info CSI 00000059 [SR] Verifying 100 components
2020-06-20 14:07:24, Info CSI 0000005a [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:24, Info CSI 0000005b [SR] Verify complete
2020-06-20 14:07:24, Info CSI 0000005c [SR] Verifying 100 components
2020-06-20 14:07:24, Info CSI 0000005d [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:25, Info CSI 0000005e [SR] Verify complete
2020-06-20 14:07:25, Info CSI 0000005f [SR] Verifying 100 components
2020-06-20 14:07:25, Info CSI 00000060 [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:26, Info CSI 00000061 CSIPERF - FilePI Queue 146ms
2020-06-20 14:07:26, Info CSI 00000062 [SR] Verify complete
2020-06-20 14:07:26, Info CSI 00000063 [SR] Verifying 100 components
2020-06-20 14:07:26, Info CSI 00000064 [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:27, Info CSI 00000065 [SR] Verify complete
2020-06-20 14:07:27, Info CSI 00000066 [SR] Verifying 100 components
2020-06-20 14:07:27, Info CSI 00000067 [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:27, Info CSI 00000068 [SR] Verify complete
2020-06-20 14:07:27, Info CSI 00000069 [SR] Verifying 100 components
2020-06-20 14:07:27, Info CSI 0000006a [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:28, Info CSI 0000006b [SR] Verify complete
2020-06-20 14:07:28, Info CSI 0000006c [SR] Verifying 100 components
2020-06-20 14:07:28, Info CSI 0000006d [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:29, Info CSI 0000006e [SR] Verify complete
2020-06-20 14:07:29, Info CSI 0000006f [SR] Verifying 100 components
2020-06-20 14:07:29, Info CSI 00000070 [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:30, Info CSI 00000071 [SR] Verify complete
2020-06-20 14:07:30, Info CSI 00000072 [SR] Verifying 100 components
2020-06-20 14:07:30, Info CSI 00000073 [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:31, Info CSI 00000074 [SR] Verify complete
2020-06-20 14:07:31, Info CSI 00000075 [SR] Verifying 100 components
2020-06-20 14:07:31, Info CSI 00000076 [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:31, Info CSI 00000077 [SR] Verify complete
2020-06-20 14:07:32, Info CSI 00000078 [SR] Verifying 100 components
2020-06-20 14:07:32, Info CSI 00000079 [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:33, Info CSI 0000007a CSIPERF - FilePI Queue 153ms
2020-06-20 14:07:33, Info CSI 0000007b [SR] Verify complete
2020-06-20 14:07:33, Info CSI 0000007c [SR] Verifying 100 components
2020-06-20 14:07:33, Info CSI 0000007d [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:34, Info CSI 0000007e [SR] Verify complete
2020-06-20 14:07:34, Info CSI 0000007f [SR] Verifying 100 components
2020-06-20 14:07:34, Info CSI 00000080 [SR] Beginning Verify and Repair transaction
2020-06-20 14:07:35, Info CSI 00000081 Warning: Overlap: Directory \??\C:\WINDOWS\System32\drivers\en-US\ is owned twice or has its security set twice
Original owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.19041.1, arch amd64, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
New owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.19041.1, arch amd64, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
2020-06-20 14:07:35, Info CSI 00000082 Warning: Overlap: Directory \??\C:\WINDOWS\System32\wbem\en-US\ is owned twice or has its security set twice
Original owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.19041.1, arch amd64, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
New owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.19041.1, arch amd64, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
2020-06-20 14:07:35, Info CSI 00000083 Warning: Overlap: Directory \??\C:\WINDOWS\help\mui\0409\ is owned twice or has its security set twice
Original owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.19041.1, arch amd64, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}
New owner: Microsoft-Windows-Foundation-Default-Security.Resources, version 10.0.19041.1, arch amd64, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}

:)

 

sfc /scannow errors


Important thing to remember is that the SFC / SCANNOW cannot always fix all errors at once. It is quite often required to run SFC /SCANNOW several times.

I have often had a situation that only a third, fourth or fifth run has finally reported "No more errors".

This is how it should be done:

• SFC / SCANNOW
• If SFC reports not all errors were fixed, reboot and run it again
• SFC / SCANNOW
• If SFC again reports not all errors were fixed, reboot and run it again
• And so on

Screenshot from the TenForums SFC tutorial:

 

SFC /SCANNOW Errors After Update

I've just updated a Windows 8.1 Pro PC to Windows 10 using the Techbench ISO which updated without any problems. However, I've just run sfc /scannow and it found errors it could not repair. I have managed to get sfc /scannow to run without errors - see what I did below:

1. Ran sfc /scannow which showed error "Windows Resource Protection found corrupt files but was unable to fix some of them."
2. Ran Dism /Online /Cleanup-Image /ScanHealth which reported "The component store is repairable."
3. Ran Dism /Online /Cleanup-Image /RestoreHealth which failed with Error: 0x800f081f "The source files could not be found.Use the "Source" option to specify the location of the files that are required to restore the feature."
4. Mounted the W10 Techbench ISO and ran Dism /Online /Cleanup-Image /RestoreHealth /source:wim:G:\sources\install.wim:1 /limitaccess which reported successfully "The restore operation completed successfully."
5. Ran sfc /scannow wich completed successfully with report "Windows Resource Protection found corrupt files and successfully repaired them."

Please advise:

1. Why would sfc /scannow fail on a newly updated installation which ran sfc /scannow error free immediately before the upgrade?
2. Why did I have to use install.wim from the Techbench ISO at step 4 above for Dism /Online /Cleanup-Image /RestoreHealth to work and will I have to use install.wim from the Techbench ISO every time I need to run this Dism command?
3. How can I configure my PC so it has the correct install.wim file for the Dism command to work properly?

 

sfc /scannow error repair

Hi,



Thank you for writing to Microsoft Community Forums.



We appreciate the efforts you have taken in trying to resolve this issue. I have analyzed the error logs that you have shared and I would suggest you follow the steps mentioned below:

1. Type Command Prompt in the
   search bar on the Taskbar.
   
2. Right click on the Command Prompt icon and select
   Run as administrator.
   
3. Now, paste the following command and hit Enter:
   DISM.exe /Online /Cleanup-image /Restorehealth
   
4. Once the DISM command is executed, we would suggest you to run sfc /scannow again.
   

If the integrity violations are not repaired after running sfc scan, the best option will be performing a repair installation. A repair installation will repair all the corrupted files.



Refer the steps mentioned below:



Download the Windows 10 Media Creation Tool (MCT) and use it to perform a repair installation
of Windows 10. We have a video that can show you how if you aren’t sure



Let us know the results.



Regards,

Nikhar Khare

Microsoft Community - Moderator