computer always fail sfc check

Page 1 of 2 12 LastLast

  1. Posts : 67
    Win10 Enterprise x64 & Win 7 Home x64
       #1

    computer always fail sfc check


    I notice over the years, my computer often fails sfc /verifyonly and would require me to do /scannow or the DISM options.
    Is this a sign that my hard drive is failing? I did a SMART test and it seems to be normal.


    This happens on any Windows 10 version number.
      My Computer


  2. Posts : 39,972
    windows 10 professional version 1607 build 14393.969 64 bit
       #2

    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) chkdsk /scan
    7) wmic recoveros set autoreboot = false
    8) wmic recoveros set DebugInfoType = 7
    9) wmic recoveros get autoreboot
    10) wmic recoveros get DebugInfoType
    11) bcdedit /enum {badmemory}

    12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
      My Computer


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

    Hi, this has been seen from time to time after a particular update or upgrade. Also, making certain types of modifications such as icon changes or changes to other system file resources will do this.

    To establish greater confidence in your disks you can leave e.g. Crystal Disinfo running, and set thresholds for it to automatically report degradation.

    If you follow the so oft-repeated advice given here to routinely and regularly use disk imaging (e.g. Macrium Reflect - free/paid) the very act of imaging verifies the consistency of the used parts of imaged disks and partitions.

    Meanwhile, try running
    chkdsk c: /scan
    from an admin command or Powershell prompt.

    To check your entire disk surface you can use e.g.
    HD Tune v2.55 (free) Error scan tab.

    Really good: Hard Disk Sentinel (not free) - includes SSDs.
    Last edited by dalchina; 22 Jul 2020 at 01:03.
      My Computers


  4. Posts : 625
    Windows 10 Pro 21H2 x64
       #4

    HDDs probably going under, possibly because of the known WD controller board corrosion issues.
    (If those aren't SSDs)
      My Computers


  5. Posts : 67
    Win10 Enterprise x64 & Win 7 Home x64
    Thread Starter
       #5

    zbook said:
    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) chkdsk /scan
    7) wmic recoveros set autoreboot = false
    8) wmic recoveros set DebugInfoType = 7
    9) wmic recoveros get autoreboot
    10) wmic recoveros get DebugInfoType
    11) bcdedit /enum {badmemory}

    12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
    i restarted my computer and did sfc /verifyonly and now it passes.. odd... Previously my computer was on constant standby and hibernation fo a while... Before the restart when i was having sfc issues, I also couldn't access some admin privileges such as services.msc and group policy, keep saying i need admin rights despite me being on admin account..

    If i follow your steps now while my sfc says my computer is fine, would it give me different information?
      My Computer


  6. Posts : 12,430
    Win10 Version 21H2 Pro and Home, Win11 Pro
       #6

    RJARRRPCGP said:
    HDDs probably going under, possibly because of the known WD controller board corrosion issues.
    (If those aren't SSDs)
    Have you a link to the referenced problem? I'd like to read it in case a client comes up with the problem.
      My Computers


  7. Posts : 39,972
    windows 10 professional version 1607 build 14393.969 64 bit
       #7

    sfc /verifyonly is rarely used in the forums as it does not perform repairs.
    The scannow command is always ran as it allows repairs.
    All of the above commands should check and tune up the computer.

    Scannow > check and repair operating system protected files
    Restorehealth > check and repair the component store
    Chkdsk /scan > quick and superficial check of the drive file system
    Wmic commands > to modify Windows default settings to optimal settings for identifying BSOD and creating dump files
    badmemory > to check whether Windows has predicted RAM failure
      My Computer


  8. Posts : 67
    Win10 Enterprise x64 & Win 7 Home x64
    Thread Starter
       #8

    zbook said:
    sfc /verifyonly is rarely used in the forums as it does not perform repairs.
    The scannow command is always ran as it allows repairs.
    All of the above commands should check and tune up the computer.

    Scannow > check and repair operating system protected files
    Restorehealth > check and repair the component store
    Chkdsk /scan > quick and superficial check of the drive file system
    Wmic commands > to modify Windows default settings to optimal settings for identifying BSOD and creating dump files
    badmemory > to check whether Windows has predicted RAM failure
    i use /verifyonly before /scannow because it is a lot faster. if i run /verifyonly and my computer says it is fine, then there's no point n running /scannow right?.
      My Computer


  9. Posts : 39,972
    windows 10 professional version 1607 build 14393.969 64 bit
       #9

    If there is nothing found that is corrupt then there is nothing to repair.

    The scannow command can be ran before walking away from the computer or ran overnight.

    Chkdsk is different as there are switches to run superficial or deep checks.
      My Computer


  10. Posts : 67
    Win10 Enterprise x64 & Win 7 Home x64
    Thread Starter
       #10

    zbook said:
    If there is nothing found that is corrupt then there is nothing to repair.

    The scannow command can be ran before walking away from the computer or ran overnight.

    Chkdsk is different as there are switches to run superficial or deep checks.
    Yes, that's why i run /verifyonly rather than /scannow now.

    12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


    if i paste the info here when now my pc is not detecting any issues vs. when it was when i originally created the thread. The info you telling me to paste here would be totally different correct?


    - - - Updated - - -

    dalchina said:
    Hi, this has been seen from time to time after a particular update or upgrade. Also, making certain types of modifications such as icon changes or changes to other system file resources will do this.
    .
    yes i notice this also happens after i install updates, does that mean my updates are corrupting my OS?
      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 19:28.
Find Us




Windows 10 Forums