sfc /scannow errors


  1. Posts : 16
    windows 10
       #1

    sfc /scannow errors


    I had a problem with chrome on windows 10, uninstalled it, new installer had malware on it. fixed it all up. system runs fine no problems. Decided to check sfc /scannow and got the corrupt files message
    "Windows Resource Protection found corrupt files but was unable to fix some
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. etc .......

    Here is a sample of the errors in the cbs log.
    2015-09-27 16:02:37, Info CSI 0000504a [SR] Cannot repair member file [l:44{22}]"System Information.lnk" of Microsoft-Windows-MSInfo32-Exe, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-09-27 16:02:37, Info CSI 00005052 [SR] Cannot repair member file [l:28{14}]"XPS Viewer.lnk" of Microsoft-Windows-XPSReachViewer, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-09-27 16:02:37, Info CSI 0000505a [SR] Cannot repair member file [l:48{24}]"Windows Media Player.lnk" of Microsoft-Windows-MediaPlayer-Shortcut, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch

    It is all the lnk files created by windows install. All these lnk files work fine, there doesn't appear to be any issues. however when looking at file explorer these shortcuts all have a different modified date (eg 26/09/15) as compared to creation date (eg 17/07/15). another machine I have has the creation date and modified date the same in relation to these windows shortcuts.
    I think that this is what is causing the hash mismatch.

    Is there a easy way to go to the lnk file and change the modified date to be the same as the creation date? So far I haven't found a way to do it. I am thinking if I can do that the hash mismatch issue will be resolved.
    I have used sfc /scannow and dism but have had no luck. I haven't as yet tried the dism restorehealth /souce method.

    Any help would be greatly appreciated and if my method of repair is incorrect please feel free to advise.
    TIA
      My Computer


  2. Posts : 5,451
    Windows 11 Home
       #2

    angd said:
    system runs fine no problems.
    Not sure, what are you trying to do then?!

    SFC sometimes reports errors, when it can not access files and such.
    If there are no problems, better to not look for any, it might actually create some.
      My Computer


  3. Posts : 17,661
    Windows 10 Pro
       #3

    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-2015_09_27_11_32_031.png

    Kari
      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 10:35.
Find Us




Windows 10 Forums