Windows 10: sfc /scannow error after 1709 update Solved

Page 1 of 4 123 ... LastLast

  1. Posts : 289
    windows 10 (x64) Home 1709
       18 Nov 2017 #1

    sfc /scannow error after 1709 update


    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.

    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. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.

    What should I do?
      My ComputerSystem Spec

  2.    18 Nov 2017 #2

    You can try to run it again or to an in place upgrade repair.

    Repair Install Windows 10 with an In-place Upgrade Installation Upgrade Tutorials
      My ComputerSystem Spec

  3.    18 Nov 2017 #3

    lvgandhi said: View Post
    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.

    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. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.

    What should I do?
    Dism.exe /Online /Cleanup-image /RestoreHealth then run sfc /scannow again
      My ComputersSystem Spec

  4.    18 Nov 2017 #4

    First make sure you have installed all Windows updates.


    To open an elevated Command Prompt window In Windows 10 type cmd.exe into Start Screen or Start Menu, right-click on Cmd.exe, and open it as an administrator.

    Run below commands from Command Prompt that is open as administrator.

    You would use DISM to fix Windows component store corruption when a sfc /scannow command is unable to repair corrupted or modified system files because the component store (source) is corrupted.

    Code:
    Dism /Online /Cleanup-Image /RestoreHealth


    SFC should be able to repair the files afterwards. Execute below command to make sure corrupted system files repaired.

    Code:
    Sfc  /Scannow

      My ComputerSystem Spec


  5. Posts : 289
    windows 10 (x64) Home 1709
    Thread Starter
       19 Nov 2017 #5

    Josey Wales said: View Post
    You can try to run it again or to an in place upgrade repair.

    Repair Install Windows 10 with an In-place Upgrade Installation Upgrade Tutorials
    This needs an ISO which is impossible to make. I tried MCT which results in an error. I have already posted this in this forum. Further I tried other solution of making edge duplicate as safari. That also failed.
      My ComputerSystem Spec


  6. Posts : 289
    windows 10 (x64) Home 1709
    Thread Starter
       19 Nov 2017 #6

    clam1952 said: View Post
    Dism.exe /Online /Cleanup-image /RestoreHealth then run sfc /scannow again
    FreeBooter said: View Post
    First make sure you have installed all Windows updates.


    To open an elevated Command Prompt window In Windows 10 type cmd.exe into Start Screen or Start Menu, right-click on Cmd.exe, and open it as an administrator.

    Run below commands from Command Prompt that is open as administrator.

    You would use DISM to fix Windows component store corruption when a sfc /scannow command is unable to repair corrupted or modified system files because the component store (source) is corrupted.

    Code:
    Dism /Online /Cleanup-Image /RestoreHealth


    SFC should be able to repair the files afterwards. Execute below command to make sure corrupted system files repaired.

    Code:
    Sfc  /Scannow



    I tried that also as admn. Still I get same error. Pic below
    Click image for larger version. 

Name:	sfcerror.PNG 
Views:	4 
Size:	19.4 KB 
ID:	164611
      My ComputerSystem Spec

  7.    19 Nov 2017 #7

    I recall reading an article recently where exactly this was discussed. Apparently it is a known quirk or oddity experienced by some:
    sfc and dism ..... old issue returns - Windows 10 Forums

    Examine the CBS.LOG file carefully. You can also try running SFC /SCANNOW a couple more times.

    Further report:
    Windows 10 - SFC finds corrupt files and is unable to fix - DISM - Microsoft Community
      My ComputerSystem Spec


  8. Posts : 4,982
    windows 10 Home threshold2
       19 Nov 2017 #8

    lvgandhi said: View Post
    I tried that also as admn. Still I get same error. Pic below
    Click image for larger version. 

Name:	sfcerror.PNG 
Views:	4 
Size:	19.4 KB 
ID:	164611
    It is of no consolation to your case, I am afraid.
    I just want to tell you that I had had this problem on the previous build. But, build 16299.64 has solved the problem for my computer.
    I have posted that in this thread of mine.........
    sfc and dism....restorehealth in 16299.64

    So, apparently the glitch is not "universal".
    I sincerely hope you will solve your issue. Good luck.
      My ComputerSystem Spec

  9.    19 Nov 2017 #9

    Hi,

    This needs an ISO which is impossible to make.
    If you can download the ISO file that corresponds to whatever version of W10 you are running you should point DISM to it when mounted.
    I.e. exact drive letter and Source folder so DISM can repair your damaged backup image. After that Sfc should run just fine.

    When running DISM without a valid source as a reference it will invariably return errors when it has only a corrupted local system source as a reference.
    A mounted official MS ISO of the correct version and correct command line (or PS) parameters should solve the issue.

    Sometimes the error messages are confusing telling you the issue can't be repaired where in essence the source to repair the issue can't be found etc.

    Cheers,
    Last edited by fdegrove; 20 Nov 2017 at 07:52.
      My ComputersSystem Spec


  10. Posts : 289
    windows 10 (x64) Home 1709
    Thread Starter
       19 Nov 2017 #10

    fdegrove said: View Post
    Hi,



    If you can download the ISO file that corresponds to whatever version of W10 you are running you should point DISM to it when mounted.
    I.e. exact drive letter and Source folder o DISM can repair your damaged backup image. After that Sfc should run just fine.

    When running DISM without a valid source as a reference it will invariably return errors when it has only a corrupted local system source as a reference.
    A mounted official MS ISO of the correct version and correct command line (or PS) parameters should solve the issue.

    Sometimes the error messages are confusing telling you the issue can't be repaired where in essence the source to repair the issue can't be found etc.

    Cheers,
    Downloading ISO is main problem.
      My ComputerSystem Spec


 
Page 1 of 4 123 ... LastLast

Related Threads
Solved Windows 10 update 1709 error when waking from sleep in Windows Updates and Activation
Hi guys, since updating to Windows 10 1709 I get a weird video issue - vertical dotted lines, the mouse is still visible as vertical stripes, when waking from sleep mode. It is a desktop machine, I am using an Intel HD graphics 530 and have...
Error in log after sfc /scannow in Performance & Maintenance
Maybe this is the cause of my dde server errors. I don't know how to try and fix. CSI 0000065c Error - Overlap: Duplicate ownership for directory \?? I have a few for different folders. Can some one point me in the correct direction ?
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 18:38.
Find Us