sfc /scannow error

Page 2 of 3 FirstFirst 123 LastLast
  1. Farvatten's Avatar
    Posts : 129
    Windows 10 Pro 64bit 1903 18362.295
       #11

    Kyhi said: View Post
    Wait til next update before considering corrupt
    That's the part I found discouraging. I had gotten this corruption in the morning before .239 and specifically waited for the update hoping it would clear it up, but it didn't.

    So I guess when in doubt, wait another cycle?
      My ComputersSystem Spec

  2.    #12

    Ivghandi wrote in an earlier post:

    I did all in first part.
    Results are as below
    PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /AnalyzeComponentStore

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18362.239

    [==========================100.0%==========================]

    Component Store (WinSxS) information:

    Windows Explorer Reported Size of Component Store : 3.69 GB

    Actual Size of Component Store : 3.62 GB

    Shared with Windows : 2.95 GB
    Backups and Disabled Features : 673.41 MB
    Cache and Temporary Data : 0 bytes

    Date of Last Cleanup : 2019-07-10 11:40:09

    Number of Reclaimable Packages : 0
    Component Store Cleanup Recommended : No

    The operation completed successfully.
    PS C:\WINDOWS\system32>

    ===========
    PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /StartComponentCleanup

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18362.239

    [=========== 20.0% ]
    The operation completed successfully.
    PS C:\WINDOWS\system32>

    ==========================
    PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /CheckHealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18362.239

    No component store corruption detected.
    The operation completed successfully.
    PS C:\WINDOWS\system32>
    ==============
    PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /ScanHealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18362.239

    [==========================100.0%==========================] The component store is repairable.
    The operation completed successfully.
    PS C:\WINDOWS\system32>
    ==========
    PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /RestoreHealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18362.239

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.
    PS C:\WINDOWS\system32>

    But still I am in problem as follows.
    PS 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 found corrupt files and successfully repaired 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.
    Bastet said: View Post
    Then the next step (unless another member has a different solution) would be the repair install.
    Isnt that exactly what you would expect to see after a successful restorehealth DISM repair? The next time you run sfc /scannow it just repairs the corrupted files?
    Isn't the last SFC /scannow where it says "Windows Resource Protection found corrupt files and successfully repaired them" just informing you that the SFC has repaired the corrupted files after the successful DISM repair? I don't think its saying that there is still a problem
      My ComputerSystem Spec

  3.    #13

    I got it fixed by running:

    sfc /scannow
    dism /online /cleanup-image /restorehealth
    sfc /scannow
    sfc /scannow -> This one should come up clean.
      My ComputerSystem Spec

  4.    #14

    sportsfan148 said: View Post
    Ivghandi wrote in an earlier post:

    I did all in first part.
    Results are as below
    PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /AnalyzeComponentStore

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18362.239

    [==========================100.0%==========================]

    Component Store (WinSxS) information:

    Windows Explorer Reported Size of Component Store : 3.69 GB

    Actual Size of Component Store : 3.62 GB

    Shared with Windows : 2.95 GB
    Backups and Disabled Features : 673.41 MB
    Cache and Temporary Data : 0 bytes

    Date of Last Cleanup : 2019-07-10 11:40:09

    Number of Reclaimable Packages : 0
    Component Store Cleanup Recommended : No

    The operation completed successfully.
    PS C:\WINDOWS\system32>

    ===========
    PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /StartComponentCleanup

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18362.239

    [=========== 20.0% ]
    The operation completed successfully.
    PS C:\WINDOWS\system32>

    ==========================
    PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /CheckHealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18362.239

    No component store corruption detected.
    The operation completed successfully.
    PS C:\WINDOWS\system32>
    ==============
    PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /ScanHealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18362.239

    [==========================100.0%==========================] The component store is repairable.
    The operation completed successfully.
    PS C:\WINDOWS\system32>
    ==========
    PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /RestoreHealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18362.239

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.
    PS C:\WINDOWS\system32>

    But still I am in problem as follows.
    PS 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 found corrupt files and successfully repaired 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.

    Isnt that exactly what you would expect to see after a successful restorehealth DISM repair? The next time you run sfc /scannow it just repairs the corrupted files?
    Isn't the last SFC /scannow where it says "Windows Resource Protection found corrupt files and successfully repaired them" just informing you that the SFC has repaired the corrupted files after the successful DISM repair? I don't think its saying that there is still a problem
    If you read the last part of the post the it does say there was still a problem with sfc even though it says it completed successfully.
    You usually do not see the instructions on running an online repair if the cmd worked so I assumed the successful was a mis-type 😀
      My ComputerSystem Spec

  5.    #15

    eLPuSHeR said: View Post
    I got it fixed by running:

    sfc /scannow
    dism /online /cleanup-image /restorehealth
    sfc /scannow
    sfc /scannow -> This one should come up clean.
    That's why Im asking the question. Am I correct in thinking that its perfectly normal that after the second running of sfc /scannow in your list you would get :-

    Beginning system scan. This process will take some time.
    Beginning verification phase of system scan.
    Verification 100% complete.
    Windows Resource Protection found corrupt files and successfully repaired 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.

    Then after that..its the third sfc /scannow that you list that comes up clean .
    Ivghandi was saying that he presumed that the second sfc /scannow you list showing "Windows Resource Protection found corrupt files and successfully repaired them" meant that he still had a problem.

    The way I understand that DISM works is that it repairs the Component Store. Then when you run SFC /scannow again it can then repair the file corruptions it detected originally. Have I got that correct?
      My ComputerSystem Spec

  6.    #16

    Should everyone do this because of a bad Defender update of the past days? Did Defender corrupt system files? If so why is thisnt a pinned important post. Will MS push an update which does an auto scan maybe with next reboot?
      My ComputerSystem Spec


  7.    #17

    I am pretty sure you can live with it. MS might fix it in some incoming update though. I prefer to leave things in a tidy manner before making a Macrium Reflect backup copy. I make one every cummulative update.
      My ComputerSystem Spec

  8.    #18

    I did

    sfc /scannow
    dism /online /cleanup-image /restorehealth
    sfc /scannow
    sfc /scannow (why the 2nd times in a row?)

    and the 2nd time it didnt find anything anymore, weird, the first one though did.
      My ComputerSystem Spec

  9.    #19

    gorgor said: View Post
    I did
    sfc /scannow
    dism /online /cleanup-image /restorehealth
    sfc /scannow
    sfc /scannow (why the 2nd times in a row?)
    and the 2nd time it didnt find anything anymore, weird, the first one though did.
    thanks for this, just did same and yes, odd that second (third) sfc is clean. but thanks!
      My ComputerSystem Spec

  10.    #20

    gorgor said: View Post
    I did

    sfc /scannow
    dism /online /cleanup-image /restorehealth
    sfc /scannow
    sfc /scannow (why the 2nd times in a row?)

    and the 2nd time it didnt find anything anymore, weird, the first one though did.
    That's just for confirming everything is okay.
      My ComputerSystem Spec


 
Page 2 of 3 FirstFirst 123 LastLast

Related Threads
Sfc/scannow error repair in Performance & Maintenance
Errors are reported which sfc cannot repair. I found some errors in the CBS.log. How do I tell if these are the (only) errors and how do I repair them? This is something of which I have no knowledge or experience. 2018-11-29 13:26:19, Info ...
Solved sfc /scannow error after 1709 update in Performance & Maintenance
After 1709 update yesterday, I did %SystemRoot%\System32\Cmd.exe /c Cleanmgr /sageset:65535 & Cleanmgr /sagerun:65535 Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase Then I did sfc /scannow. I got the following error. ...
Win 10 Pro (64 bit) on Intel DP-43TF motherboard on an Q9650 core2 quad at 3GHz with 8GB memory. sfc /scannow fails at 66% completion with multiple "Error - Overlap: Duplicate ownership for directory" errors with different directories being listed....
Solved SFC /SCANNOW Error in Performance & Maintenance
When trying to run SFC /SCANNOW the following error is generated: C:\Windows\system32>sfc /scannow Windows Resource Protection could not start the repair service. Is this a knpown problem with solution?
Hi friends, By the way after the recent update, I am having issues with Network Properties, and I see the reason mentioned here, but for your kind attention my sfc /scannow results found corrupted files that cant be fixed. How to fix that. Any help...
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:15.
Find Us