Apps crash for no reason. Windows Update keeps failing. The Start menu won't open. Your first instinct might be "let's just reimage it." 😩
Hold on. A lot of these weird problems come from corrupted system files, and Windows ships with two built-in tools that can repair them in about 15 to 30 minutes. Try them first. 🚀
🔑 Step 1: Open an elevated Command Prompt
Both tools need admin rights. Search for Command Prompt (or Terminal), right-click it, and pick Run as administrator.
If you skip this, SFC tells you that you must be an administrator, and DISM fails with an elevation error.
🩺 Step 2: Repair the Windows image with DISM
DISM /Online /Cleanup-Image /RestoreHealth
Why run this first? SFC repairs files by copying good versions from the Windows component store. If that store is damaged too, SFC can't fix anything. DISM checks and repairs the component store itself, using Windows Update as its source by default.
Heads up: it can sit at 20% or 62.3% for a while. That's normal. Let it finish. ⏳
Want a quick check before the full repair?
DISM /Online /Cleanup-Image /ScanHealth
🔍 Step 3: Fix system files with SFC
sfc /scannow
System File Checker scans protected Windows files and replaces corrupted ones. You'll get one of these results:
- ✅ "Windows Resource Protection did not find any integrity violations." System files are fine, so look elsewhere (drivers, apps, user profile).
- 🔧 "...found corrupt files and successfully repaired them." Restart and test again.
- ⚠️ "...found corrupt files but was unable to fix some of them." Run DISM again, restart, then run SFC again.
📄 Step 4: Check the log if you need details
SFC writes its results to the CBS log:
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt"
That pulls just the SFC lines into a text file on your desktop, so you can see which files it couldn't fix.
🔁 Step 5: Restart and retest
Always reboot after repairs, then reproduce the original problem. If it's gone, write down what fixed it in the ticket. 📝
🧭 When to escalate
If DISM and SFC both run clean and the problem stays, the system files probably aren't the cause. Now an in-place repair install or a reimage makes sense, and you can show you ruled out the easy fix first.
Your turn: do you run DISM before SFC, or SFC first? 👇
Top comments (0)