sfc /scannow error after 1709 update

dalchina said:

Hi, Kyhi's referring to the useful tool in post#2 here:
Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums

I have his tool. How to use it to solve this problem?

dalchina said:

I actually think you're trying to solve a non-problem - if your system is functioning normally, others have observed SFC not succeeding even if DISM does. @Bree reported that discrepancy was resolved after a Windows update.

I just signed up here, after seeing this and other threads which address my problem. I also have been getting the "

Windows Resource Protection found corrupt files but was unable to fix some of them"

message after running sfc /scannow ever since the 1709 update. I've tried resetting the computer in various ways (using "Reset this PC" keeping files and apps, using "Reset this PC" keeping nothing, using MediaCreationTool, using Windows10Upgrade9252.exe) and running the DISM with its various options (/CheckHealth, /ScanHealth, /RestoreHealth, /RestoreHealth /Source:repairSource\install.wim), but no matter what I do, the message is the same. I have seen a few people say that they have had this problem but that it seems to go away after subsequent builds. I can only hope that the same thing will happen for me.

I should also mention that I started having other problems after the 1709 update installed. At times the mouse and keyboard would be completely unresponsive (I discovered that closing the lid to put it to sleep and opening it again to wake it up... made it work again) and I even got a blue screen once. I had never had these problems before the 1709 update (I got this laptop new less than eight months ago). I've also never had any errors come up when running sfc /scannow before the 1709 update, but after the unresponsiveness problem started happening, I ran sfc /scannow and got the aforementioned "Windows Resource Protection found corrupt files but was unable to fix some of them" message. That is why I am concerned about this. I have not had the unresponsiveness problem or any blue screens since resetting, but I've only had limited usage since the resets, so I don't know if it might still happen at some point.

EdmondDantes ,
If you want us to troubleshoot the bsod please run the dm log collector and make a new post in the BSOD forum:
BSOD Crashes and Debugging - Windows 10 Forums
BSOD - Posting Instructions - Windows 10 Forums

zbook said:

EdmondDantes ,
If you want us to troubleshoot the bsod please run the dm log collector and make a new post in the BSOD forum:
BSOD Crashes and Debugging - Windows 10 Forums
BSOD - Posting Instructions - Windows 10 Forums

Thanks, zbook, but I have reset the computer since the blue screen occurred, so I don't think any information will be able to collected on it.

lvgandhi said:

I could not download iso using tool and also from windowsiso.net in my laptop. From another using MCT, I could download ISO using MCT.
Did repair install as per
Repair Install of Windows 10 with an In-place Upgrade.
Now sfc /scannow shows all ok and no error.

I tried it, it didn't work for me - still same error message...

As already posted, Only thing that worked for me is an inplace upgrade, now SFC and DISM are fine.

Two questions, what is an "inplace upgrade" and after downloading the iso, how do I point to it via dism?

To perform an in place upgrade repair you will need to open file explorer and click on the windows iso flash drive. Then launch setup or setup.exe. Make sure that you do not click install. Instead look in the left lower corner and click on repair your computer. Then follow the text and images in this link:
Repair Install Windows 10 with an In-place Upgrade Installation Upgrade Tutorials

In many cases that will fix operating system problems.
If you need to go deeper and fix registry problems you may need to create a Macrium backup image. Then clean install followed by restoring the image.

If scannow and restorehealth fail to fix the OS you may be able to fix the OS without an in place upgrade repair. This would be by running a dism command with the iso as the source file. And if this fails then you would perform the in place upgrade repair.