Windows 10: sfc /scannow error after 1709 update

Thanks for the response.
I have limited wifi download option. Hence I do not want to use non microsoft sites and try.

 

Hi,

The tool from Heidoc.net pulls the ISO's off official MS servers so it's absolutely safe to use. Can you use someone else's bandwith to download it ?

Cheers, *Wink

 

Did you actually look at the 1st option?
Download Official MS Windows & MS Office ISO's From TechBench
TECHBENCH ISO DOWNLOADER





How do you resolve the SFC problem? Probably you don't.
Why? Documented on this forum is a discrepancy between DISM and SFC results, until a further update is applied.

 

If you use Image-health and select option 2 > restorehealth
you will get a detailed log file copied onto your desktop....

thus you (WE) can see what is wrong...

SFC > option 7 > will also create a details log onto your desktop

 

Thanks. I will try at a later time. Now not possible.

 

Sorry. I could not understand your guidance. Can you please put what command I should use to get the results?

 

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?

 

You use the Image Health program as he described in his post...

It's a convenient way of launching DISM e.g.

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.

Anyway, you are now aware of a useful range of tools.
(Kyhi's boot disk, Image Health, in-place repair, ways of getting iso's).

 

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

 

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.

 

I could not download iso using tool and also from windowsiso.net in my laptop. In another laptop 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.