Should I Be Concerned? SFC/Scannow Errors.

  1. Homer712's Avatar
    Posts : 140
    Windows 10, 1909 (OS Build 18363.1379 )
       #1

    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
      My Computer

  2. Callender's Avatar
    Posts : 4,092
    N/A
       #2

    Why run SFC? Do you have a problem with a system file?

    In any case read the info in the CODE box here:

    Giving up on WIN10 Home

    Note   Note

    The wrapper script causes sfc errors, so if you want to run sfc, uninstall the
    script first or read the logs for errors with EOSNotify.exe,
    WaaSMedic.exe, WaasMedicSvc.dll, WaaSMedicPS.dll, WaaSAssessment.dll,
    UsoClient.exe, SIHClient.exe, MusNotificationUx.exe, MusNotification.exe,
    osrss.dll, %ProgramFiles%\rempl, %systemroot%\UpdateAssistant and
    %systemroot%\UpdateAssistantV2, and %systemdrive%\Windows10Upgrade
    which is normal.
      My Computer

  3. Homer712's Avatar
    Posts : 140
    Windows 10, 1909 (OS Build 18363.1379 )
    Thread Starter
       #3

    Thank you Callender! As for why did I run SFC, possibly just bored to death. Retired Electrical Engineer and playing around with Windows keeps the brain functioning. Saw the Tutorial on SFC (saw a number of posts here advising to run it after any Windows 10 CU) so I thought, "why not."

    Thank you for the response and I'll read through that other thread start to finish. Lots of good information. I posted back and forth with the developer of the wrapper script over on MDL while he was working on this latest version (up to 2.7.0 just a few days ago), and learned a lot there as well.

    In any event, I'll mark this thread "solved" once I post this reply to you.
      My Computer

  4. Try3's Avatar
    Posts : 7,464
    Windows 10 Home x64 Version 20H2 Build 19042.928
       #4

    Use the SFC tutorial guidance to run a Dism restorehealth command whilst online so that it can repair the files it objects to.
    SFC - TenForumsTutorials
    Option 3 - in the blurb after step 4.


    Sorry, I missed the reference to Sledgehammer in your OP. Running SFC-DISM is not an option for you unless you take the steps noted by Callender.

    Denis
      My Computer

  5. Try3's Avatar
    Posts : 7,464
    Windows 10 Home x64 Version 20H2 Build 19042.928
       #5

    Homer712 said:
    ... saw a number of posts here advising to run it after any Windows 10 CU ...
    By the way, SFC rarely needs to be run. Telling you to run it after every CU is about as valid as telling you to run it every time a politician lies.

    If you have fault symptoms that indicate that Windows is faulty then SFC might help to fix the fault. Or it might not but it is so simple to run that you might as well run it in such circumstances rather than spend ages trying to diagnose the fault. On 11th December 2013, I proposed publishing guidance on when SFC was appropriate so perhaps MS are about to respond. I'm waiting with baited breath.

    Denis
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 00:13.
Find Us




Windows 10 Forums