Repair Windows Update Components with DISM + SFC (Win10/11) to Fix Update Errors
Difficulty: Intermediate | Time Required: 20 minutesWindows Update errors often come down to corrupted system files or a damaged component store (the Windows image that updates rely on). The good news: you can repair these core components using built-in Microsoft tools—DISM and SFC—without reinstalling Windows.
This guide walks you through a safe, repeatable process that fixes many common update problems (failed cumulative updates, “something went wrong,” endless retry loops, and errors such as 0x800f081f, 0x80070002, 0x80073712, 0x800f0922, etc. on Windows 10 and Windows 11.
Prerequisites
Before you start, make sure you have:- Administrator access (you’ll run commands in an elevated terminal)
- A stable internet connection (DISM may download repair files from Windows Update)
- ~20 minutes of uninterrupted time
- Optional but recommended: save your work and close apps (some repairs can briefly spike disk/CPU)
Note (Windows 10/11 versions):
The steps apply to all supported Windows 10 and Windows 11 builds (including 22H2 and 23H2/24H2). Commands are the same; only the app you use (Command Prompt vs Windows Terminal) may differ slightly.
Step-by-step: Repair Windows Update components with DISM + SFC
1) Open an elevated terminal (Admin)
Choose the option you prefer:Windows 11
- Right-click Start
- Select Windows Terminal (Admin)
- Right-click Start
- Select Windows PowerShell (Admin) or Command Prompt (Admin)
Tip: Windows Terminal is fine—these commands work in PowerShell and Command Prompt.
2) (Optional) Confirm Windows sees corruption (quick health checks)
These checks are fast and help confirm whether the component store is flagged as repairable.Copy/paste these commands one at a time:
DISM /Online /Cleanup-Image /CheckHealthThen:
DISM /Online /Cleanup-Image /ScanHealthWhat to expect
- CheckHealth: quick result; tells you if corruption is detected and whether a repair is possible.
- ScanHealth: deeper scan; can take a few minutes.
Note: If ScanHealth reports corruption, that’s normal for update issues—and exactly what the next step is designed to fix.
3) Repair the Windows component store (DISM RestoreHealth)
Now run the actual repair:DISM /Online /Cleanup-Image /RestoreHealthWait for it to finish (commonly 5–15 minutes). It may appear “stuck” at certain percentages—this is normal.
Successful results typically include:
- “The restore operation completed successfully”
- “The component store corruption was repaired” (or similar)
Warning: Don’t close the window mid-process. Interrupting DISM can leave the repair incomplete.
4) Repair system files (SFC)
Once DISM finishes, run System File Checker:sfc /scannowSFC uses the now-repaired component store to replace damaged system files.
Possible outcomes:
- “Windows Resource Protection did not find any integrity violations.”
Great—system files look clean. - “Windows Resource Protection found corrupt files and successfully repaired them.”
Also good—issues were fixed. - “…found corrupt files but was unable to fix some of them.”
Don’t panic—see troubleshooting notes below.
Tip: The common best practice is DISM first, SFC second. Doing SFC first can fail if the component store itself is corrupted.
5) Restart Windows (important)
Even if both tools report success, reboot to ensure repaired files and servicing components fully reload.- Save your work
- Restart the PC
6) Try Windows Update again
After restart:Windows 11: Settings → Windows Update → Check for updates
Windows 10: Settings → Update & Security → Windows Update → Check for updates
If the update that failed previously is offered again, let it install.
Tip: If you’re dealing with a cumulative update that repeatedly fails, run the DISM + SFC process first, then attempt the update immediately after the reboot.
Tips, warnings, and troubleshooting
Tip: Run from a local admin account if possible
If you’re on a work PC or joined to a domain, group policies or management tools can interfere. If available, test with a local administrator account.Troubleshooting 1: DISM fails with “source files could not be found” (common)
If DISM returns errors like 0x800f081f (“The source files could not be found”), Windows may not be able to download repair files.Try these quick fixes:
- Ensure you’re online and not behind a restrictive proxy/VPN
- Temporarily disable third-party “system cleaner” tools
- Reboot and rerun:
DISM /Online /Cleanup-Image /RestoreHealthAdvanced option (best for stubborn cases): use an ISO as a repair source
If you have a Windows 10/11 ISO that matches your installed version/build, you can point DISM to it. (This is more advanced, but very effective.
Example (replace
X: with your mounted ISO drive letter):DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:X:\sources\install.wim:1 /LimitAccessNote: Some ISOs useinstall.esdinstead ofinstall.wim. The syntax changes slightly. If you want, reply with your ISO’ssourcesfolder contents and your Windows edition, and we can provide the exact command.
Troubleshooting 2: SFC says it couldn’t fix some files
If you see “unable to fix some of them”:- Reboot
- Run DISM again:
DISM /Online /Cleanup-Image /RestoreHealth - Then rerun:
sfc /scannow
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\SFC_Details.txt"This creates SFC_Details.txt on your Desktop for easier reading/sharing on the forum.
Troubleshooting 3: Windows Update still won’t work after DISM + SFC
DISM/SFC repair core components, but Windows Update can also be blocked by services, cache corruption, or third-party security software.If updates still fail:
- Restart and try again once more
- Ensure your date/time are correct
- Temporarily disable third-party antivirus (if installed)
- Consider resetting Windows Update components (separate procedure)
Note: If you post back on WindowsForum.com, include: the update KB number, exact error code, and the last lines of DISM/SFC output.
Conclusion
Running DISM (/RestoreHealth) followed by SFC (/scannow) is one of the most reliable ways to repair the Windows servicing stack and system files that Windows Update depends on. It’s safe, built-in, and often fixes update failures without drastic steps like reinstalling Windows.If your updates were failing due to corrupted components, this process can get you back to a stable, update-ready system in about 20 minutes.
Key Takeaways:
- DISM repairs the Windows component store that updates rely on.
- SFC repairs system files, using DISM’s repaired source.
- Rebooting after repairs is important before retrying Windows Update.
- For persistent DISM source errors (e.g., 0x800f081f), using a matching ISO as a repair source is a strong next step.
This tutorial was generated to help WindowsForum.com users get the most out of their Windows experience.
