sfc /scannow Errors, Now What?


  1. Posts : 181
    Windows 10, 20H2 (OS Build 19042.928)
       #1

    sfc /scannow Errors, Now What?


    OK, so sometimes possibly you're better off not knowing. Running Windows 10, 1909 and everything is functioning perfectly, or so I thought. No errors, nothing, not a single hiccup. Then I run sfc /scannow, maybe just because I'm curious, maybe too much time on my hands. In any event results of first run:
    sfc /scannow Errors, Now What?-first-run.png

    Read here that sometimes you need to restart and run DISM and then sfc /scannow again, so I did. Results of second run:
    sfc /scannow Errors, Now What?-second-run.png

    Did another search here and the suggestion was to run "Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:F:\sources\install.wim:1 /limitaccess" after mounting the Windows ISO image. Did that, results here:
    sfc /scannow Errors, Now What?-final-run.png

    The only thing I see that I'm not sure of is that the DISM version is 10.0.18362.1379 and the Image version is 10.0.18363.1379. Could that be an issue?

    Also, I am running Matthew Wai's "preferences", could those be causing the errors. Prior to that I was running Sledgehammer and I know that there would be errors with DISM and sfc /scannow if that was active. It was completely uninstalled prior to using Matthes Wai's solution.

    If not, where do I go from here? Thanks.
    Last edited by Homer712; 17 Apr 2021 at 17:11.
      My Computer


  2. Posts : 34,985
    Win 10 Pro (1903) (2nd PC is 21H2)
       #2

    SFC /VERIFYONLY (check failing) is not the same as failing to repair.

    First check your disk (3rd party tool) and if ok run
    chkdsk X: /scan
    from an admin command or Powershell prompt, where X is the pertinent drive letter.

    If ok, ultimately an in-place upgrade repair install which keeps all progs and data would be appropriate.
    For that you need an iso file of the same major build as you have installed (freely downloadable).

    Kyhi, a member here produced this small tool to help progress through resolving SFC failures using DISM:
    Dropbox - Image-Health v16.zip - Simplify your life
    Last edited by dalchina; 17 Apr 2021 at 13:44.
      My Computers


  3. Posts : 821
    Win 10
       #3

    @Homer712

    The correct order would be first:
    Dism /online /cleanup-image /restorehealth

    and then:
    sfc /scannow

    Source:
    Fix Windows Update errors via DISM or System Update Readiness tool - Windows Server | Microsoft Docs

    The Dism version number does not have to match the installed build number.

    The version numbers of files starts with 18362 because the substructure forms the version number 18362 is Build 1903.

    The same applies to 20h2 or 21h1 because the base is 19041 Build 2004 there.Here is an example picture:

    sfc /scannow Errors, Now What?-screenshot-2021-04-17-202852.jpg

    If Dism cannot provide the defective files or download from the Microsoft servers and thus sfc /scannow cannot repair the files, you should first look in the relevant CBS.log to see which files are defective.

    As it is in the linked Microsoft page.


    Before performing an in-place upgrade, this is always the first thing someone should do who is familiar with the logs.

    Friendly greetings
    Sorry for any mistakes. English is not my native language.
      My Computer


  4. Posts : 181
    Windows 10, 20H2 (OS Build 19042.928)
    Thread Starter
       #4

    dalchina said:
    SFC /VERIFYONLY (check failing) is not the same as failing to repair.

    First check your disk (3rd party tool) and if ok run
    chkdsk X: /scan
    from an admin command or Powershell prompt, where X is the pertinent drive letter.

    If ok, ultimately an in-place upgrade repair install which keeps all progs and data would be appropriate.
    For that you need an iso file of the same major build as you have installed (freely downloadable).

    Kyhi, a member here produced this small tool to help progress through resolving SFC failures using DISM:
    Dropbox - Image-Health v16.zip - Simplify your life
    @dalchina Thanks, I took it in steps.

    1. Ran chkdsk, results:
    sfc /scannow Errors, Now What?-chkdsk.png

    Then I stepped through the "Image Health" steps 1, 2, 3, 4, 6 and 7:

    sfc /scannow Errors, Now What?-read-me.png

    Last step 7 generated this screen:

    sfc /scannow Errors, Now What?-sfc-scannow.png

    Also, three reports were generated on the desktop. Sadly, for those of us to whom a four or five line batch file is a major accomplishment, they may as well be in Greek. So, I'm looking for help from those who can interpret these reports and advise what my next step should be. Guessing that my choices may be to do a repair of 1909, or just upgrade to the next version. A "clean install" either way would take me ages as I have a large number of additional software installed.

    SFC Details.txtScanHealth Details.txtRestoreHealth Details.txt
      My Computer


  5. Posts : 821
    Win 10
       #5

    @Homer712
    Since I didn't know Sledgehammer, I first had to find out what it did.

    It removes the permissions to access these files:
    2021-04-17 16:50:42, Info CSI 000002f9 [SR] Cannot repair member file [l:21]'MusNotificationUx.exe' of Microsoft-Windows-Update-MusNotificationUxExe, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 000002fa [SR] Cannot repair member file [l:19]'MusNotification.exe' of Microsoft-Windows-Update-MusNotificationBroker, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 000002fb [SR] Cannot repair member file [l:13]'UsoClient.exe' of Microsoft-Windows-Update-UsoClient, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 000002fc [SR] Cannot repair member file [l:18]'WaaSAssessment.dll' of Microsoft-Windows-WaaSAssessment, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 000002fd [SR] Cannot repair member file [l:16]'WaaSMedicSvc.dll' of Microsoft-Windows-WaaSMedic, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 000002fe [SR] Cannot repair member file [l:15]'WaaSMedicPS.dll' of Microsoft-Windows-WaaSMedic, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 000002ff [SR] Cannot repair member file [l:13]'SIHClient.exe' of ServiceInitiatedHealing-Client, version 10.0.18362.1316, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 00000300 [SR] Cannot repair member file [l:21]'MusNotificationUx.exe' of Microsoft-Windows-Update-MusNotificationUxExe, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 00000301 [SR] This component was referenced by [l:158]'Microsoft-Windows-Client-Desktop-Required-Package0412~31bf3856ad364e35~amd64~~10.0.18362.1379.08688183F3963F8CEF1B687F5ECB3B8650C97753632768958636365E44EBC2F9'
    2021-04-17 16:50:42, Info CSI 00000302 [SR] Cannot repair member file [l:18]'WaaSAssessment.dll' of Microsoft-Windows-WaaSAssessment, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 00000303 [SR] This component was referenced by [l:128]'Microsoft-Windows-Client-Desktop-Required-Package041021~31bf3856ad364e35~amd64~~10.0.18362.1377.74a75cafce9c10a911ddcf88d9093f78'
    2021-04-17 16:50:42, Info CSI 00000304 [SR] Cannot repair member file [l:13]'SIHClient.exe' of ServiceInitiatedHealing-Client, version 10.0.18362.1316, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 00000305 [SR] This component was referenced by [l:118]'Microsoft-Windows-Client-Features-Package0216~31bf3856ad364e35~amd64~~10.0.18362.1316.4229019198219d148bc586e815ae9454'
    2021-04-17 16:50:42, Info CSI 00000306 [SR] Cannot repair member file [l:19]'MusNotification.exe' of Microsoft-Windows-Update-MusNotificationBroker, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 00000307 [SR] This component was referenced by [l:158]'Microsoft-Windows-Client-Desktop-Required-Package0412~31bf3856ad364e35~amd64~~10.0.18362.1379.08688183F3963F8CEF1B687F5ECB3B8650C97753632768958636365E44EBC2F9'
    2021-04-17 16:50:42, Info CSI 00000308 [SR] Cannot repair member file [l:13]'UsoClient.exe' of Microsoft-Windows-Update-UsoClient, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 00000309 [SR] This component was referenced by [l:158]'Microsoft-Windows-Client-Desktop-Required-Package0412~31bf3856ad364e35~amd64~~10.0.18362.1379.08688183F3963F8CEF1B687F5ECB3B8650C97753632768958636365E44EBC2F9'
    2021-04-17 16:50:42, Info CSI 0000030a [SR] Cannot repair member file [l:16]'WaaSMedicSvc.dll' of Microsoft-Windows-WaaSMedic, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 0000030b [SR] This component was referenced by [l:128]'Microsoft-Windows-Client-Desktop-Required-Package041021~31bf3856ad364e35~amd64~~10.0.18362.1377.74a75cafce9c10a911ddcf88d9093f78'
    2021-04-17 16:50:42, Info CSI 0000030c [SR] Cannot repair member file [l:15]'WaaSMedicPS.dll' of Microsoft-Windows-WaaSMedic, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 0000030d [SR] This component was referenced by [l:128]'Microsoft-Windows-Client-Desktop-Required-Package041021~31bf3856ad364e35~amd64~~10.0.18362.1377.74a75cafce9c10a911ddcf88d9093f78'


    The program's download package contains a recovery.cmd file.

    Did you run this as administrator after removing Sledgehammer?

    recovery.zip


    Friendly greetings
      My Computer


  6. Posts : 181
    Windows 10, 20H2 (OS Build 19042.928)
    Thread Starter
       #6

    Tekkie Boy said:
    @Homer712
    Since I didn't know Sledgehammer, I first had to find out what it did.

    It removes the permissions to access these files:
    2021-04-17 16:50:42, Info CSI 000002f9 [SR] Cannot repair member file [l:21]'MusNotificationUx.exe' of Microsoft-Windows-Update-MusNotificationUxExe, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 000002fa [SR] Cannot repair member file [l:19]'MusNotification.exe' of Microsoft-Windows-Update-MusNotificationBroker, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 000002fb [SR] Cannot repair member file [l:13]'UsoClient.exe' of Microsoft-Windows-Update-UsoClient, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 000002fc [SR] Cannot repair member file [l:18]'WaaSAssessment.dll' of Microsoft-Windows-WaaSAssessment, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 000002fd [SR] Cannot repair member file [l:16]'WaaSMedicSvc.dll' of Microsoft-Windows-WaaSMedic, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 000002fe [SR] Cannot repair member file [l:15]'WaaSMedicPS.dll' of Microsoft-Windows-WaaSMedic, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 000002ff [SR] Cannot repair member file [l:13]'SIHClient.exe' of ServiceInitiatedHealing-Client, version 10.0.18362.1316, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 00000300 [SR] Cannot repair member file [l:21]'MusNotificationUx.exe' of Microsoft-Windows-Update-MusNotificationUxExe, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 00000301 [SR] This component was referenced by [l:158]'Microsoft-Windows-Client-Desktop-Required-Package0412~31bf3856ad364e35~amd64~~10.0.18362.1379.08688183F3963F8CEF1B687F5ECB3B8650C97753632768958636365E44EBC2F9'
    2021-04-17 16:50:42, Info CSI 00000302 [SR] Cannot repair member file [l:18]'WaaSAssessment.dll' of Microsoft-Windows-WaaSAssessment, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 00000303 [SR] This component was referenced by [l:128]'Microsoft-Windows-Client-Desktop-Required-Package041021~31bf3856ad364e35~amd64~~10.0.18362.1377.74a75cafce9c10a911ddcf88d9093f78'
    2021-04-17 16:50:42, Info CSI 00000304 [SR] Cannot repair member file [l:13]'SIHClient.exe' of ServiceInitiatedHealing-Client, version 10.0.18362.1316, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 00000305 [SR] This component was referenced by [l:118]'Microsoft-Windows-Client-Features-Package0216~31bf3856ad364e35~amd64~~10.0.18362.1316.4229019198219d148bc586e815ae9454'
    2021-04-17 16:50:42, Info CSI 00000306 [SR] Cannot repair member file [l:19]'MusNotification.exe' of Microsoft-Windows-Update-MusNotificationBroker, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 00000307 [SR] This component was referenced by [l:158]'Microsoft-Windows-Client-Desktop-Required-Package0412~31bf3856ad364e35~amd64~~10.0.18362.1379.08688183F3963F8CEF1B687F5ECB3B8650C97753632768958636365E44EBC2F9'
    2021-04-17 16:50:42, Info CSI 00000308 [SR] Cannot repair member file [l:13]'UsoClient.exe' of Microsoft-Windows-Update-UsoClient, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 00000309 [SR] This component was referenced by [l:158]'Microsoft-Windows-Client-Desktop-Required-Package0412~31bf3856ad364e35~amd64~~10.0.18362.1379.08688183F3963F8CEF1B687F5ECB3B8650C97753632768958636365E44EBC2F9'
    2021-04-17 16:50:42, Info CSI 0000030a [SR] Cannot repair member file [l:16]'WaaSMedicSvc.dll' of Microsoft-Windows-WaaSMedic, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 0000030b [SR] This component was referenced by [l:128]'Microsoft-Windows-Client-Desktop-Required-Package041021~31bf3856ad364e35~amd64~~10.0.18362.1377.74a75cafce9c10a911ddcf88d9093f78'
    2021-04-17 16:50:42, Info CSI 0000030c [SR] Cannot repair member file [l:15]'WaaSMedicPS.dll' of Microsoft-Windows-WaaSMedic, version 10.0.18362.1350, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file cannot be checked
    2021-04-17 16:50:42, Info CSI 0000030d [SR] This component was referenced by [l:128]'Microsoft-Windows-Client-Desktop-Required-Package041021~31bf3856ad364e35~amd64~~10.0.18362.1377.74a75cafce9c10a911ddcf88d9093f78'


    The program's download package contains a recovery.cmd file.

    Did you run this as administrator after removing Sledgehammer?

    recovery.zip


    Friendly greetings
    @Tekkie Boy

    No I had not. I ran the Sledgehammer "uninstaller" but not the "recovery.cmd." Actually, just tried it a couple of times (install/uninstall Sledgehammer) and the uninstall process completely deletes the entire Sledgehammer folder, so I would not have even seen the "recovery" folder.

    But, I copied the recovery.cmd to another location, uninstalled Sledgehammer, then ran the recovery.cmd. Guess what . . . sfc/scannow runs with NO ERRORS. I then ran the "Image Health" version of sfc/scannow (option 7) and it found NO ERRORS as well. So, I'm good to go!

    Thank you for researching this for me and "friendly greetings" back at you!

    I will go up on the Sledgehammer site and leave a link to this thread for the developer. Possibly the issue was at my end, but it's worth him knowing the process I went through to fix things.

    sfc /scannow Errors, Now What?-latest-sfc-scannow.png

    sfc /scannow Errors, Now What?-image-health-sfc-scannow.png

    SFC Details.txt
      My Computer


  7. Posts : 7,457
    Windows 10 Home 20H2
       #7

    Homer712 said:
    Also, I am running Matthew Wai's "preferences", could those be causing the errors.
    It is absolutely normal to see the following error:
    Code:
    Windows Resource Protection found corrupt files but was unable to fix some of them.
    For online repairs, details are included in the CBS log file located at
    windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
    repairs, details are included in the log file provided by the /OFFLOGFILE flag.
    Run "Undo everything.cmd" before running "sfc /scannow".
    Re-run "Disable hijackers.cmd" after running "sfc /scannow".

    The update hijackers are system files scanned by SFC.exe. When the files have been disabled (locked), SFC.exe will find such errors.
      My Computer


  8. Posts : 181
    Windows 10, 20H2 (OS Build 19042.928)
    Thread Starter
       #8

    Just posted this over on the "My Digital Life" forum in the Sledgehammer thread:

    I don't know how on God's green earth I missed (or just had a complete "senior" moment) the fact that "Matthew's Preferences" disables the same hijackers files that Sledgehammer does. So, when I ran the "Sledgehammer" recovery.cmd, the reason the sfc/scannow errors went away was that the recovery.cmd was undoing the same changes put in place by "Matthew's Preferences" as it would have had I still been using "Sledgehammer."

    Marking thread as solved.

    Edit: For anyone reading this thread in the future, the latest version of Kyhi's "Image Health" (mentioned in Post #2) is located on his profile page: https://www.tenforums.com/members/kyhi.html under the "About" tab.
    Last edited by Homer712; 19 Apr 2021 at 10:05.
      My Computer


  9. Posts : 16,026
    Win 10 Pro 64-bit v1909 - Build 18363 Custom ISO Install
       #9

    Hello @Homer712,

    Homer712 said:
    I will go up on the Sledgehammer site and leave a link to this thread for the developer. Possibly the issue was at my end, but it's worth him knowing the process I went through to fix things.
    Homer712 said:
    I don't know how on God's green earth I missed (or just had a complete "senior" moment) the fact that "Matthew's Preferences" disables the same hijackers files that Sledgehammer does. So, when I ran the "Sledgehammer" recovery.cmd, the reason the sfc/scannow errors went away was that the recovery.cmd was undoing the same changes put in place by "Matthew's Preferences" as it would have had I still been using "Sledgehammer."

    You might also want to point out the section . . .

    sfc /scannow Errors, Now What?-wu.jpg

    . . . in the Tutorial => How to use CMD script and VBScript to control Windows Update in Windows 10

    I hope this helps.
      My Computer


  10. Posts : 7,457
    Windows 10 Home 20H2
       #10

    Thanks for choosing "Matthew's preference".
      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 06:55.
Find Us




Windows 10 Forums