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

Please post a share link for the desktop txt file.

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

It's a small text file.

Should be able to just zip and post as an attachment.

zbook said:

Please post a share link for the desktop txt file.

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

Share link here

I looked at this file and there is nothing out of the ordinary in it.
I suspect that is because i ran sfc /scannow again after the errors were fixed.

- - - Updated - - -

OldNavyGuy said:

It's a small text file.

Should be able to just zip and post as an attachment.

I've posted a Google drive link.

Damun said:

I looked at this file and there is nothing out of the ordinary in it.
I suspect that is because i ran sfc /scannow again after the errors were fixed.

That would be why.

dalchina said:

See Kyhi's useful tool here - post #2 after the rescue disk:
Windows 10 Recovery Tools - Bootable Rescue Disk



and text (Options 1-16) following
The Preferred Method Of Use To Fix file Corruption Would Be To Select

Thanks @dalchina

The CBS and sfcdetails.txt were unremarkable.

For:
What is the correct order of DISM and sfc commands to fix problems?
The order matters for documentation purposes.
If restorehealth is ran first the end user may not see integrity violations.

zbook said:

The CBS and sfcdetails.txt were unremarkable.

Thanks @zbook

For:
What is the correct order of DISM and sfc commands to fix problems?
The order matters for documentation purposes.
If restorehealth is ran first the end user may not see integrity violations.

Please bear with me, I don't know a lot about this and i'd like to learn:
I don't understand why restorehealth would make sfc not see any errors.
If I understood @Brinks post earlier in this thread then dism /online /cleanup-image /restorehealth fixes errors in the component store that sfc then uses to check windows system files.
If that's the case then fixing the component store before running sfc should still report the errors, unless the errors are in the component store.

Brink said:

Correct.

SFC uses the component store to replace any corrupted or modified system files it finds.

If SFC is unable to replace files (usually because of an issue with component store), it will give an error message. In this situation, using dism /online /cleanup-image /restorehealth to repair the component store may then allow SFC to replace the files when ran again afterwards.

SFC will still report if it found any corrupted or modified system files even with an issue to the component store. SFC just wouldn't be able to replace/repair the files if there was an issue with the component store.

Thanks for the explanation @Brink.