Use DISM and SFC on Windows 11 without guessing repair commands

DISM and System File Checker are frequently pasted into support threads as a magic pair. They have distinct jobs: DISM examines and can repair the Windows component store, while SFC checks protected system files. Neither repairs a failing SSD, an unrelated application profile or malware by itself. A useful run captures the exact output, checks whether corruption is repairable and only then chooses a repair source or next step.

Before you start​

Back up important files first, particularly if the machine also shows disk errors. Sign in with an administrator account and keep power connected. Record the error code or Windows feature that fails and the current build under Settings > System > About. Use an elevated Windows Terminal. If this is a managed PC, follow IT's servicing rules; policy can change the repair source.

Do it step by step​

1. Open Terminal as administrator. Run `DISM /Online /Cleanup-Image /ScanHealth` and wait for the assessment. Then run `DISM /Online /Cleanup-Image /CheckHealth` to learn whether corruption is reported as healthy, repairable or non-repairable. Copy the exact result before proceeding.
2. If the component store is healthy but a system file seems damaged, run `sfc /scannow` and record whether it repaired files, found none or could not repair some. Do not infer success merely because the progress counter reached 100 percent.
3. If DISM reports repairable corruption, run `DISM /Online /Cleanup-Image /RestoreHealth`. With no explicit source, Windows uses its configured repair source and may use Windows Update. Allow the network and sufficient time; avoid stopping the scan because a percentage appears frozen.
4. After a successful DISM repair, run `sfc /scannow` again so protected files are checked against the repaired store. Restart and test the original failing task. Save the command output, timestamps and any error code.
5. If DISM reports a missing repair source, use Microsoft's documented matching-image source process or your organization administrator. Do not copy a random DLL or run a registry cleaner. An installation image must match the installed Windows version and language closely enough for servicing.
6. If corruption is non-repairable or the symptom persists despite clean checks, stop this branch. Investigate disk health, update history and a supported repair reinstall, rather than repeating the same commands daily.

Check the result​

A successful branch ends with DISM reporting a healthy store, SFC reporting no remaining integrity violation or a completed repair, and the original task working after restart. Record all three observations separately.

If something goes wrong​

Error 0x800f081f often indicates that required source files were not found; a matching source or policy fix is needed, not more identical runs. If the command fails to start, confirm it was elevated and typed exactly. If hardware diagnostics report storage errors, secure data before further writes.

Know the limit​

Microsoft's DISM documentation distinguishes repairable from non-repairable image states and explains /Source and /LimitAccess. These tools cannot guarantee application data or hardware health. An offline Windows image uses different syntax from /Online; do not apply an online recipe blindly in WinRE. Microsoft DISM image repair Recovery options