sfc /scannow says this.

Page 2 of 2 FirstFirst 12

  1. Posts : 5,478
    2004
       #11

    Ghost82 said:
    I guess the DISM thing solved it? It's a mistery to me.

    Anyway, with this tool I'm a little bit psyched. It's good to run the scf on a kind of routine, or only if we see that something is messed up? I ask this because I wasn't experiencing anything bad, but did it and found those lines.
    Yes DISM fixed it - good news :)

    SFC replaces corrupt things from the component store. This was also corrupt so sfc could not work. Dism fixed the component store and this meant sfc could then work and replace whatever was wrong.

    As for how often to run probably only if something is not working is it required. It would not do any harm to run every week (or every day) though. Perhaps after installing upgrades would be a good time.
      My Computer


  2. Posts : 2,834
    Windows 11 Home (x64) Version 21H1 (build 19043.1202)
       #12

    Hi glad you got it sorted and hopefully now all will be good
      My Computer


  3. Posts : 197
    Windows 10 Pro x64
    Thread Starter
       #13

    Thank you both, guys :). I really love this boards. Well, the people in here, of course.
      My Computer


  4. Posts : 4
    Windows 10
       #14

    I'd just like to add my thanks too - I got my new Microsoft Surface Pro 4 sorted out by the combination of sfc /scannow and the Dism commands explained so clearly here. Looks like Microsoft are supplying devices with corrupt files already installed...
      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 08:49.
Find Us




Windows 10 Forums