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

There are lots of computer with normal checkhealth that may or may not have problems with later commands.
Similar with scanhealth.
The advantage of running scanhealth is for helpers to see whether there is or is not a different error message or code.

The advantage of running scannow before restorehealth is to see if it reports integrity violations that could explain other computer problems.

The quickest method to fix problems for the end user is restorehealth followed by scannow.
For those interested in cause and effect then run scannow first followed by restorehealth followed by scannow.
Then view findstr and cbs results.

I just want to point out, most corruptions in windows system files comes from hard drive corruption, and it is important that running check disk is important to first, fix any corruption in the drive, which may restore damaged missing files, Second to prevent sfc attempt to repair a segment of data that is corrupt and unrepairable.
I actually feel better that everyone can't agree upon the sfc DISM issue. My opinion is sfc can NOT repair the system if the repair files are missing or corrupt. It also goes back to my original argument that if the drive is damaged, bot the system files and repair files could be damaged causing additional delays.

Depending how corrupt system file or system files is it