Have you ever tried to run a Windows update and hit a message like “corrupt system files were found,” or watched the same error return no matter how many times you cleared the cache? That usually means one of the core files Windows depends on has been damaged. The good news: you don’t need to reinstall Windows. Two built-in command-line tools — DISM and sfc /scannow — can repair those files for you. This is the standard Windows system file repair routine built into every modern Windows install, and it’s the fix most people miss before they reach for a fresh install.
DISM vs. sfc /scannow: What each one does
These two commands have clear, separate jobs — and the order you run them in matters.
- DISM (Deployment Image Servicing and Management) downloads clean Windows image files from Microsoft’s servers and rebuilds the local repair store your PC draws healthy copies from. (Think of it as restocking the materials warehouse.)
- SFC (System File Checker) then uses that freshly repaired store to find and replace the actual broken system files on your PC. (That’s the actual building repair.)
Step 1: How to Open Command Prompt as Administrator
Because this check touches protected system files, you must run it with admin rights. A normal CMD window will fail the scan.
- Press the Windows key and type
cmd. - Right-click Command Prompt and choose Run as administrator.
Step 2: Repair the Windows image with DISM (first pass)
This step connects to Microsoft’s servers and rebuilds the local repair store.
- In the admin CMD window, paste the command below and press Enter:
DISM.exe /Online /Cleanup-image /Restorehealth
- You’ll see a progress bar climb toward
[== 20.0% ]and beyond. - This typically takes 5–15 minutes. Wait until you see “The restore operation completed successfully.”
Step 3: Repair system files with sfc /scannow (second pass)
Now SFC uses that healthy store to swap out any broken files on your machine.
- In the same CMD window, type the command below and press Enter:
sfc /scannow
- The scan runs from 0% to 100%.
- When it finishes, read the result message — the table below tells you what to do next.
How to read the sfc /scannow result
After the scan, Windows Resource Protection prints one of three messages. Here’s what each one means and what to do:
| Message you see | What it means | What to do |
|---|---|---|
| “Windows Resource Protection did not find any integrity violations.” | Your system files are fine. | Nothing to repair — the problem lies elsewhere. Look at other update fixes. |
| “Windows Resource Protection found corrupt files and successfully repaired them.” | Damaged files were fixed. | Restart your PC, then retry the Windows update. |
| “Windows Resource Protection found corrupt files but was unable to fix some of them.” | DISM didn’t finish cleanly, or the damage is severe. | Boot into Safe Mode and run sfc /scannow again. If it still fails, re-run DISM, then sfc /scannow once more. |
FAQ
Q: DISM has been stuck near 62.3% for over 10 minutes. Is it broken?
A: No — that’s normal. It’s downloading clean file copies from Microsoft’s servers, and the speed depends on your connection. Don’t close the window; just wait for it to reach 100%.
Q: Will DISM work if I’m offline?
A: The /Restorehealth option needs to reach Microsoft’s servers, so internet access is required. If you’re fully offline, mount a Windows installation ISO and point DISM at that local source path instead.
Wrapping up
When Windows updates fail or your system acts unstable, a corrupt system file is often the hidden cause. Windows system file repair doesn’t have to mean a full reinstall — running DISM first, then sfc /scannow, repairs those files in place, keeping your apps and files intact. After the scan reports success, restart and try your update again.
Photo credits: Pexels contributors.