Windows 10: What is the correct order of DISM and sfc commands to fix problems?

Today i updated my system to build 2004.
Everything went fine and so far i haven't had any problems.

For good meassure i ran sfc /verifyonly and it found some problems.

From reading here in the forum and from this Microsoft support document, it is recommended first to run

DISM.exe /Online /Cleanup-image /Restorehealth
and then
sfc /scannow

Here in the forum i found this thread where it is recommended to run DISM and sfc in this order:

1) Dism.exe /online /Cleanup-Image /checkhealth
2) Dism.exe /online /Cleanup-Image /scanhealth
3) Dism.exe /online /Cleanup-Image /Restorehealth
4) sfc /scannow
5) Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
6) Dism.exe /Online /Cleanup-Image /StartComponentCleanup

I seem to remember that i have seen other recommendations elsewhere (can't remember where).

So i was wondering: Is there a consensus on the correct order of DISM and sfc commands to to repair missing or corrupted system files?

:)

 

In troubleshooting Windows Update, how do the recommended DISM and SFC commands actually work?

I am trying to understand what the DISM and SFC commands listed in the

Fix Window Update errors guide actually do. I have searched posts online about these two commands but I still have questions about how they work in this situation.

One of the later steps in the guide is "Fix Windows File Corruption". The two commands in that step are:

1. DISM.exe /Online /Cleanup-image /Restorehealth

(explanation:

/online applies to a running operating system

/Cleanup-Image Performs cleanup or recovery operations on the image

/RestoreHealth Scans the image for component store corruption, and then performs repair operations automatically)

Followed by:

2. sfc /scannow

(explanation:

/scannow Scans the integrity of all protected system files and repairs files with problems when possible.)

Is the “image” that DISM is cleaning up a copy/image of the operating system, or is it the actual components/files of the operating system running on the computer?

Is this DISM command actually altering the operations of the computer, or just modifying an image?

Is the image checked/cleaned up by DISM used by the sfc command?

What is the difference between DISM and sfc commands?

Another article about using DISM says: ImportantWhen you run this command, DISM uses Windows Update to provide the files that are required to fix corruptions.
However, if your Windows Update client is already broken, use a running Windows installation as the repair source, or use a Windows side-by-side folder from a network share or from a removable media, such as the Windows DVD, as the source of the files.

If the reason you run DISM is to troubleshoot windows update on your computer and DISM uses Windows Update to fix corruptions, what is the point of using this DISM command in the Fix Windows Update Errors guideline?

A docs.microsoft.com article about DISM best practices says: We do not recommend that you use the Sfc.exe scan options to automatically fix Windows system files.

Is there a risk that having DISM /restorehealth and/or sfc /scannow make changes will further corrupt the system?

Thanks for any replies that help me clear this up.

 

Can't get SFC and DISM to work anymore on Win10

Ok, can someone help me out because this crap is starting to piss me off. There was once a time when you could simply run SFC and DISM to check Windows files integrity and if there were any problems found with the local files, Windows repaired it automatically. The reason why I want to run this is because I'm getting stupendously huge amount of errors and warnings in Event Viewer, but I don't want to run refresh because it'll mess up tons of apps.

Commands I used:
sfc /scannow
Dism /Online /Cleanup-Image /RestoreHealth

Fast forward few years and we now have glorious Windows 10. Trying to run the same tools, they find errors but stubbornly refuse to fix ANYTHING. What's the god damn point of it then?

Sfc finds issues but can't repair them and DISM constantly bitches how it can't find the source. All this used to work directly in Windows 7, but in Win 10, nothing. This was one of the best features to get OS back in good state and they go and ruin it. Because Microsoft!

I've checked this thread:
https://social.technet.microsoft.co...sfc-failed-to-repair?forum=win10itprohardware

Nothing worked. And they keep mentioning install.wim where my Windows image downloaded from Microsoft itself! only carries install.esd which I can't seem to use with anything.

I've also tried this tool:
CodePlex Archive

Which again wants .wim file and refuses to work with esd.

 

How to get damn DISM to work?

Thx guys, I'll compress this data into a blog post. For all the so called guides I've read, not a single one mentioned it has to be WIM file (some listed even ESD which clearly doesn't work) or that certain ISO images don't work with DISM.

After I've done DISM thingie, SFC also managed to repair stuff. Which is what I've needed here.