computer always fail sfc check

Page 2 of 2 FirstFirst 12

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

    yes i notice this also happens after i install updates
    Shouldn't always be the case, but has been sometimes so historically. And no, it's not that updates are corrupting something. Just that a mismatch is created between the current O/S and the WinSxS store somehow.
      My Computers


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

    For convenience you can copy and paste all at one time into administrative command prompt while doing other things on the computer.

    For example while task manager was displaying:
    CPU: 25%
    Mem: 54%
    Disk; 6%

    these were ran:

    Code:
    sfc /scannow
    dism /online /cleanup-image /scanhealth
    dism /online /cleanup-image /restorehealth
    sfc /scannow
    chkdsk /scan
    wmic recoveros set autoreboot = false
    wmic recoveros set DebugInfoType = 7
    wmic recoveros get autoreboot
    wmic recoveros get DebugInfoType
    bcdedit /enum {badmemory}

    Code:
    Microsoft Windows [Version 10.0.17763.1282]
    (c) 2018 Microsoft Corporation. All rights reserved.
    
    C:\WINDOWS\system32>sfc /scannow
    
    Beginning system scan.  This process will take some time.
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    Windows Resource Protection did not find any integrity violations.
    
    C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth
    
    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1282
    
    Image Version: 10.0.17763.1282
    
    [==========================100.0%==========================] No component store corruption detected.
    The operation completed successfully.
    
    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
    
    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1282
    
    Image Version: 10.0.17763.1282
    
    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.
    
    C:\WINDOWS\system32>sfc /scannow
    
    Beginning system scan.  This process will take some time.
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    Windows Resource Protection did not find any integrity violations.
    
    C:\WINDOWS\system32>chkdsk /scan
    The type of the file system is NTFS.
    
    Stage 1: Examining basic file system structure ...
      881920 file records processed.
    File verification completed.
      22540 large file records processed.
      0 bad file records processed.
    
    Stage 2: Examining file name linkage ...
      1220 reparse records processed.
      1108116 index entries processed.
    Index verification completed.
      0 unindexed files scanned.
      0 unindexed files recovered to lost and found.
      1220 reparse records processed.
    
    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
      113099 data files processed.
    CHKDSK is verifying Usn Journal...
      38382832 USN bytes processed.
    Usn Journal verification completed.
    
    Windows has scanned the file system and found no problems.
    No further action is required.
    
     248570090 KB total disk space.
     162249980 KB in 559074 files.
        363512 KB in 113100 indexes.
             0 KB in bad sectors.
       1004434 KB in use by the system.
         65536 KB occupied by the log file.
      84952164 KB available on disk.
    
          4096 bytes in each allocation unit.
      62142522 total allocation units on disk.
      21238041 allocation units available on disk.
    
    C:\WINDOWS\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\DESKTOP-9HEBUKS\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
    Property(s) update successful.
    
    C:\WINDOWS\system32>mic recoveros set DebugInfoType = 7
    'mic' is not recognized as an internal or external command,
    operable program or batch file.
    
    C:\WINDOWS\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE
    
    
    C:\WINDOWS\system32>mic recoveros get DebugInfoType
    'mic' is not recognized as an internal or external command,
    operable program or batch file.
    
    C:\WINDOWS\system32>bcdedit /enum {badmemory}
    
    RAM Defects
    -----------
    identifier              {badmemory}
    
    C:\WINDOWS\system32>

    The last command required a click on enter.

    The duration with the many open browsers / applications was 19 minutes.
    Again, it was completed while working on other applications.
      My Computer


  3. Posts : 625
    Windows 10 Pro 21H2 x64
       #13

    Berton said:
    Have you a link to the referenced problem? I'd like to read it in case a client comes up with the problem.
    Well, of course, I just found this one:

    WD HDD PCB Oxidization / corrosion / discolorations you name it - Desktop & Mobile Drives - WD Community

    Heads up, I saw this kind of stuff going on, even with a later-2010s Black HDD! Yes, I did also see that on a very-early-2010s' WD HDD. (or circa-2010) But, that possibly exists on WD HDDs from 2007 and 2006!
    (Based on bizarre symptoms when trying to clean-install Windows Vista at the time.)
      My Computers


  4. Posts : 13
    Windows 10
       #14

    Subbed.
      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:27.
Find Us




Windows 10 Forums