I think the point that was being made was that running the DISM command before the SFC one will mean that SFC will not find faults because they've already been fixed and therefore diagnostic data will have been hidden.
In contrast, running SFC first will allow the discovered faults to be readily identified for future reference even though they might be fixed pretty swiftly by DISM.
Denis
Last edited by Try3; 30 Nov 2020 at 05:47.
Either sfc /scannow or sfc /verifyonly methods produce the same unhidden diagnostic information.
Running restorehealt though will hide both verifyonly and scannow diagnostics.
Maybe I'm missing something, but I guess I don't see that as an issue.
If I ran DISM first, I can look at dism.log in %windir%\logs\dism, and see what it found, or fixed (depending on the run option used).
I personally run SFC first, but I don't automatically move to DISM, unless SFC can't fix something, or the issue still exists after it did fix something.
One thing at a time.
Most end users are not trained to read CBS or DISM logs.
They see the results displayed when the command completes the run and displays the results.
So the command order is important for diagnostics.
I don't follow your logic.
If DISM was run, post the DISM log.
If SFC was run, use the parse CBS.log command, and post that log.
If I get an error code in my car, I don't need training on Chrysler error codes. I take it to a mechanic who can make sense out of it.
Users don't need to be trained in logs, just given a simple way to provide the needed information.
It's on the tech forum helpers (like car mechanics) to read and interpret.
I always run it this way.
Dism /Online /Cleanup-Image /StartComponentCleanup
Dism /Online /Cleanup-Image /RestoreHealth
SFC /scannow
It's always worked for me, time spent running the commands does not matter to me. If SFC fixes any problems or cannot fix a problem I run the same set of commands again, up to 3 times. Been doing it this way for quite a few years now. It works for me and I'm happy with it.
Quote