Windows repair sequence: why running DISM before SFC yields better results

Microsoft emphasises the importance of running DISM before SFC for effective Windows recovery. This article explains the correct repair order and troubleshooting tips for system file issues.

Windows repair guides often tell users to run SFC and DISM as if they are interchangeable. They are not. According to Microsoft, SFC checks protected system files and repairs them from the Windows image, while DISM repairs that image itself. That means the order matters: if the image or component store is damaged, SFC may report failures it cannot correct.

The practical sequence is to open an elevated Command Prompt or Terminal, run DISM first, then run SFC. Microsoft’s guidance for Windows 10 and 11 recommends DISM /Online /Cleanup-image /RestoreHealth before sfc /scannow so the repair source is healthy before SFC tries to replace files. DISM /Online /Cleanup-Image /ScanHealth is the read-only check, while /RestoreHealth performs the repair.

If DISM cannot reach Windows Update, the usual failure is 0x800f081f, which indicates that source files could not be found. In that case, Microsoft and other repair guides advise using matching installation media and pointing DISM at the install.wim source with /Source and /LimitAccess so it does not try Windows Update.

When SFC still reports unrepairable files, the useful evidence is in CBS.log under %windir%LogsCBS. The log is large, but filtering for “[SR]” entries makes it easier to identify the specific file that failed. Microsoft also notes that SFC can be run in Safe Mode when normal execution is not possible.

If both tools complete and the problem remains, the fault may not be system-file corruption at all. Repair guides commonly point to drivers, third-party software, or deeper Windows damage in those cases. The next step is often an in-place upgrade repair, which reinstalls Windows over itself while keeping files and apps.