Windows 10: Should I Be Concerned? SFC/Scannow Errors.

Sometimes ignorance is bliss, especially with Windows 10. Saw the Tutorial when you could add SFC/SCANNOW to the drop down menu, so I did. Ran SFC/SCANNOW and of course the report that was generated stated that there were errors that could not be repaired (posted below, I took out all the the normal stuff and just copied the four sets of error messages).

Windows 10, 1909, last CU installed was back in February, I give it a month or so before updating.

I am running Sledgehammer, so updates are off. Would this have anything to do with the errors listed? Thanks!

First Set:

Microsoft-Windows-Update-MusNotificationBroker, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:04:17, Info CSI 00000160 [SR] Cannot repair member file [l:19]'MusNotification.exe' of Microsoft-Windows-Update-MusNotificationBroker, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:04:17, Info CSI 00000161 [SR] This component was referenced by [l:157]'Microsoft-Windows-Client-Desktop-Required-Package0412~31bf3856ad364e35~amd64~~10.0.18362.693.5071480F81552952A71B27ACC9D01D21CCA109E9D412E4664 5A3B6BA8B5ADD28'
2020-03-29 10:04:18, Info CSI 00000162 [SR] Verify complete
2020-03-29 10:04:18, Info CSI 00000163 [SR] Verifying 100 components
2020-03-29 10:04:18, Info CSI 00000164 [SR] Beginning Verify and Repair transaction
2020-03-29 10:04:18, Info CSI 00000165 [SR] Cannot repair member file [l:21]'MusNotificationUx.exe' of Microsoft-Windows-Update-MusNotificationUxExe, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:04:20, Info CSI 00000166 [SR] Cannot repair member file [l:13]'UsoClient.exe' of Microsoft-Windows-Update-UsoClient, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:04:21, Info CSI 00000169 [SR] Cannot repair member file [l:13]'UsoClient.exe' of Microsoft-Windows-Update-UsoClient, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:04:21, Info CSI 0000016a [SR] This component was referenced by [l:157]'Microsoft-Windows-Client-Desktop-Required-Package0412~31bf3856ad364e35~amd64~~10.0.18362.693.5071480F81552952A71B27ACC9D01D21CCA109E9D412E4664 5A3B6BA8B5ADD28'
2020-03-29 10:04:22, Info CSI 0000016c [SR] Cannot repair member file [l:21]'MusNotificationUx.exe' of Microsoft-Windows-Update-MusNotificationUxExe, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:04:22, Info CSI 0000016d [SR] This component was referenced by [l:157]'Microsoft-Windows-Client-Desktop-Required-Package0412~31bf3856ad364e35~amd64~~10.0.18362.693.5071480F81552952A71B27ACC9D01D21CCA109E9D412E4664 5A3B6BA8B5ADD28'

Second Set:

Microsoft-Windows-WaaSAssessment, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:04:28, Info CSI 00000178 [SR] Cannot repair member file [l:16]'WaaSMedicSvc.dll' of Microsoft-Windows-WaaSMedic, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:04:28, Info CSI 00000179 [SR] Cannot repair member file [l:15]'WaaSMedicPS.dll' of Microsoft-Windows-WaaSMedic, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:04:28, Info CSI 0000017a [SR] Cannot repair member file [l:16]'WaaSMedicSvc.dll' of Microsoft-Windows-WaaSMedic, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:04:28, Info CSI 0000017b [SR] This component was referenced by [l:127]'Microsoft-Windows-Client-Desktop-Required-Package041021~31bf3856ad364e35~amd64~~10.0.18362.693.74a75cafce9c10a911ddcf88d9093f78'
2020-03-29 10:04:28, Info CSI 0000017c [SR] Cannot repair member file [l:15]'WaaSMedicPS.dll' of Microsoft-Windows-WaaSMedic, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:04:28, Info CSI 0000017d [SR] This component was referenced by [l:127]'Microsoft-Windows-Client-Desktop-Required-Package041021~31bf3856ad364e35~amd64~~10.0.18362.693.74a75cafce9c10a911ddcf88d9093f78'
2020-03-29 10:04:29, Info CSI 0000017f [SR] Cannot repair member file [l:18]'WaaSAssessment.dll' of Microsoft-Windows-WaaSAssessment, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:04:29, Info CSI 00000180 [SR] This component was referenced by [l:127]'Microsoft-Windows-Client-Desktop-Required-Package041021~31bf3856ad364e35~amd64~~10.0.18362.693.74a75cafce9c10a911ddcf88d9093f78'

Third Set:

2020-03-29 10:05:14, Info CSI 000001d1 [SR] Cannot repair member file [l:13]'SIHClient.exe' of ServiceInitiatedHealing-Client, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:05:15, Info CSI 000001d2 [SR] Cannot repair member file [l:13]'SIHClient.exe' of ServiceInitiatedHealing-Client, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:05:15, Info CSI 000001d3 [SR] This component was referenced by [l:117]'Microsoft-Windows-Client-Features-Package0216~31bf3856ad364e35~amd64~~10.0.18362.329.4229019198219d148bc586e815ae9454'

Forth Set:

2020-03-29 10:07:31, Info CSI 000002b9 [SR] Cannot repair member file [l:19]'MusNotification.exe' of Microsoft-Windows-Update-MusNotificationBroker, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:07:31, Info CSI 000002ba [SR] Cannot repair member file [l:13]'UsoClient.exe' of Microsoft-Windows-Update-UsoClient, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:07:31, Info CSI 000002bb [SR] Cannot repair member file [l:21]'MusNotificationUx.exe' of Microsoft-Windows-Update-MusNotificationUxExe, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:07:31, Info CSI 000002bc [SR] Cannot repair member file [l:16]'WaaSMedicSvc.dll' of Microsoft-Windows-WaaSMedic, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:07:31, Info CSI 000002bd [SR] Cannot repair member file [l:15]'WaaSMedicPS.dll' of Microsoft-Windows-WaaSMedic, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:07:31, Info CSI 000002be [SR] Cannot repair member file [l:18]'WaaSAssessment.dll' of Microsoft-Windows-WaaSAssessment, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:07:31, Info CSI 000002bf [SR] Cannot repair member file [l:13]'SIHClient.exe' of ServiceInitiatedHealing-Client, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:07:31, Info CSI 000002c0 [SR] Cannot repair member file [l:19]'MusNotification.exe' of Microsoft-Windows-Update-MusNotificationBroker, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:07:31, Info CSI 000002c1 [SR] This component was referenced by [l:157]'Microsoft-Windows-Client-Desktop-Required-Package0412~31bf3856ad364e35~amd64~~10.0.18362.693.5071480F81552952A71B27ACC9D01D21CCA109E9D412E4664 5A3B6BA8B5ADD28'
2020-03-29 10:07:31, Info CSI 000002c2 [SR] Cannot repair member file [l:13]'UsoClient.exe' of Microsoft-Windows-Update-UsoClient, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:07:31, Info CSI 000002c3 [SR] This component was referenced by [l:157]'Microsoft-Windows-Client-Desktop-Required-Package0412~31bf3856ad364e35~amd64~~10.0.18362.693.5071480F81552952A71B27ACC9D01D21CCA109E9D412E4664 5A3B6BA8B5ADD28'
2020-03-29 10:07:31, Info CSI 000002c4 [SR] Cannot repair member file [l:16]'WaaSMedicSvc.dll' of Microsoft-Windows-WaaSMedic, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:07:31, Info CSI 000002c5 [SR] This component was referenced by [l:127]'Microsoft-Windows-Client-Desktop-Required-Package041021~31bf3856ad364e35~amd64~~10.0.18362.693.74a75cafce9c10a911ddcf88d9093f78'
2020-03-29 10:07:31, Info CSI 000002c6 [SR] Cannot repair member file [l:15]'WaaSMedicPS.dll' of Microsoft-Windows-WaaSMedic, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:07:31, Info CSI 000002c7 [SR] This component was referenced by [l:127]'Microsoft-Windows-Client-Desktop-Required-Package041021~31bf3856ad364e35~amd64~~10.0.18362.693.74a75cafce9c10a911ddcf88d9093f78'
2020-03-29 10:07:31, Info CSI 000002c8 [SR] Cannot repair member file [l:18]'WaaSAssessment.dll' of Microsoft-Windows-WaaSAssessment, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:07:31, Info CSI 000002c9 [SR] This component was referenced by [l:127]'Microsoft-Windows-Client-Desktop-Required-Package041021~31bf3856ad364e35~amd64~~10.0.18362.693.74a75cafce9c10a911ddcf88d9093f78'
2020-03-29 10:07:31, Info CSI 000002ca [SR] Cannot repair member file [l:21]'MusNotificationUx.exe' of Microsoft-Windows-Update-MusNotificationUxExe, version 10.0.18362.628, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:07:31, Info CSI 000002cb [SR] This component was referenced by [l:157]'Microsoft-Windows-Client-Desktop-Required-Package0412~31bf3856ad364e35~amd64~~10.0.18362.693.5071480F81552952A71B27ACC9D01D21CCA109E9D412E4664 5A3B6BA8B5ADD28'
2020-03-29 10:07:31, Info CSI 000002cc [SR] Cannot repair member file [l:13]'SIHClient.exe' of ServiceInitiatedHealing-Client, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
2020-03-29 10:07:31, Info CSI 000002cd [SR] This component was referenced by [l:117]'Microsoft-Windows-Client-Features-Package0216~31bf3856ad364e35~amd64~~10.0.18362.329.4229019198219d148bc586e815ae9454'
2020-03-29 10:07:31, Info CSI 000002ce [SR] Repair complete
2020-03-29 10:07:31, Info CSI 000002cf [SR] Committing transaction
2020-03-29 10:07:31, Info CSI 000002d4 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

:)

 

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