Windows 10: Does DISM/Restorehealth fix all issues with SFC/SCannow?

Really weird.
Ran SFC Scannow. Says I have some corrupt files. So I went ahead and did the DISM/Restorehealth and it said it completed successfully.
But when I run SFC again getting same error.

Wouldn't a DISM/Restorehealth fix any issues with SFC/Scannow?

:)

 

windows 10 professional post installation corruption not fixed by sfc scannow or dism restorehealth

Greg,

The troubleshooting for problems with corruption found by sfc /scannow and dism/ online /cleanup-image /restorehealth were related to the upgrade from windows 7 pro to windows 10 pro. The source for the windows 10 pro upgrade was the Microsoft web site.

It impacted some upgrades but not all upgrades. It is unclear why it impacts some and not all.

The source for the windows 10 pro dvd was hp for licensed HP or Compaq PC.

The problems with sfc / scannow and dism restorehealth corruption have been fixed.

sfc /scannow now displays: windows resource protection did not find any integrity violations

dism restorehealth now displays: the restore operation completed successfully. The operation completed successfully.

These were problems with the windows 10 pro operating system downloaded from the Microsoft web site and/or installed from the dvd.

When dism restorehealth finds corruption that it does not fix I don't understand how to guide it and find the source files that it is missing. In case there is corruption in the future please list the steps to use the windows 10 pro dvd to supply the dism
restorehealth command with the sources to fix the corruption.

 

SFC scan and DISM restorehealth scan

Well to be honest I cannot comment about as I haven't heard anything similar to this as a fix.

 

Which Win 10 version do you have ?

In the last Win 10 version 10586.218, we had this problem.
This reply from Microsoft Community forum suggested that it was an incorrect report, and that we could ignore it. Microsoft was working to fix it.

The current 10586.318 appears to have this problem fixed........ at least to my computer.

 

I am using insider preview 14342 Release 160506-1708

 

The "convention wisdom" suggested by many members is to run the sfc at least 3 times AFTER the dism is completed. successfully.

I never buy that, but if the experts say so, who am I to argue ?

 

I will give it a whirl. I am doing a DISM/Restorhealth with a local disk image first then trying SFC /scannow again*Smile

 

Well, I'm not an expert but when it makes fixes, it is on a restart the repairs are actually made. So, run it, restart and run it again. 3 times. I have seen it work that way on windows 7 before. No, it does not always work.