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?

lvgandhi said:

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

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

Josey Wales said:

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.

clam1952 said:

Dism.exe /Online /Cleanup-image /RestoreHealth then run sfc /scannow again

FreeBooter said:

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

lvgandhi said:

I tried that also as admn. Still I get same error. Pic below

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.

fdegrove said:

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.