Match the symptom before changing settings
| What you observe | Where to focus |
|---|---|
| Error 0x800f081f source files not found | Use a matching Windows repair source |
| DISM stalls at one percentage | Allow time and check activity before interrupting |
| Network or proxy error appears | Check Windows Update connectivity and policy |
| DISM completes but issue remains | Run SFC and verify the original symptom |
Diagnose DISM component-store repair with evidence first
Run DISM once and write down the exact error code, percentage, and message. A missing repair source, network failure, access error, and damaged component store each require a different next step.
Confirm whether DISM is using Windows Update or a local image as its repair source. If a local source is used, verify edition, language, architecture, and image index before assuming the command itself is broken.
Complete these focused checks: record the exact DISM command and error code; confirm Windows edition, language, version and build; check network, proxy and Windows Update status; create a backup before advanced source repair. Take screenshots or notes before changing firmware, encryption, recovery, driver or power settings. Those records provide a return path if the first repair does not help.
Use Microsoft installation media and Windows Update as repair sources. Avoid modified ISOs or third-party component-store repair packages because a mismatched source can create new servicing errors.
Save important data and recovery information before servicing or repair-install work. DISM is normally non-destructive, but repeated servicing failures can be a sign that broader recovery may be needed.
Run the supported online repair
Use DISM /Online /Cleanup-Image /RestoreHealth from an elevated Terminal and let it complete without closing the window.
Record the exact DISM error code and message before trying another command. Source-not-found, access, servicing, and network errors require different fixes.
1Verification checkpoint
- Run DISM again with the corrected source or condition.
- Confirm the exact previous error no longer appears.
- If a new code appears, treat it as a new diagnostic clue.
Provide a matching source when required
Mount official Windows media matching edition, language and build, identify the correct image index and use the documented Source and LimitAccess options.
Confirm that Windows Update services and network access are available if DISM is using the online repair source. If you intentionally use local installation media, verify that the source path and image index match the installed edition.
2Verification checkpoint
- Run SFC after DISM succeeds.
- Confirm protected files can now be checked or repaired.
- If SFC still fails, preserve both logs before escalating.
Complete the repair chain
Run SFC after DISM succeeds, restart and test the original failure. Use repair reinstall when servicing remains damaged.
Run DISM from an elevated terminal and wait for the process to finish. A percentage that appears paused for several minutes is not automatically a failure.
3Verification checkpoint
- Restart and retest the original Windows problem.
- Confirm the repair changed the real symptom, not just the command output.
- Persistent servicing errors may justify a repair install.
Interpret the result before escalating
A source-files error usually points to repair-source availability or mismatch rather than proof that Windows itself cannot be repaired.
If DISM completes with a local source but not with the online source, investigate Windows Update connectivity, policy, proxy, or servicing access separately.
If DISM fails consistently with servicing-stack or component-store errors, move toward repair-install or recovery options instead of repeatedly changing source switches.
Verify the fix and choose the safe escalation
After DISM reports success, run SFC and check whether previously damaged protected files can now be repaired.
Restart Windows and retest the original feature, update, or system behavior that prompted the DISM repair.
If the same DISM error returns with a verified matching source, preserve the error code and logs before escalating to a repair install or deeper storage/component-store diagnosis.
Technical order checked against current Microsoft guidance. Exact controls vary by Windows build, hardware, edition and organization policy.
Frequently asked questions
Why does DISM pause at one percentage?
Some phases take a long time. Check disk and CPU activity before assuming it is frozen.
What causes error 0x800f081f?
DISM cannot find repair files compatible with the installed Windows image.
Do I still need SFC after DISM?
Yes. DISM repairs the component source; SFC uses it to repair protected system files.