My laptop started crawling, apps crashed randomly and a blue screen showed up twice in one week. Everyone told me the same lazy thing: format it. Instead, I opened CMD as administrator and ran a handful of Windows repair commands that fixed everything in under an hour. No USB drive, no paid software, no lost files.
The trick isn’t secret. It’s just that nobody explains how to repair Windows with CMD without making it sound like rocket science. So here’s the real version, tested on Windows 10 and Windows 11 in 2026.
First, open CMD the right way (this matters more than you think)
Hit the Windows key, type cmd, right-click on Command Prompt and pick «Run as administrator». If you skip the admin part, half the commands below will throw an access denied error and you’ll waste time thinking your system is beyond repair.
One detail most tutorials ignore: if you’re on Windows 11, the Terminal app works the same way, but I still prefer classic CMD because sfc /scannow and DISM behave identically and you avoid the extra tabs.
sfc /scannow: the command that repairs corrupted system files
This is the one that saved me. Type:
sfc /scannow
Press Enter and don’t touch anything. It scans every protected Windows file and replaces the corrupted ones with clean copies from a cache stored on your own PC. On my machine it took about 12 minutes.
You’ll get one of three messages. «Windows Resource Protection did not find any integrity violations» means you’re clean. «Found corrupt files and successfully repaired them» is the jackpot. And «could not perform the requested operation» means you need the next step, because the repair cache itself is broken.
DISM /RestoreHealth: repairing the repair tool
When sfc fails, it’s usually because the component store is damaged. That’s what DISM fixes. Run:
DISM /Online /Cleanup-Image /RestoreHealth
This one connects to Microsoft’s servers and downloads healthy replacement files. It needs internet, so plug in an Ethernet cable if your Wi-Fi driver is acting up. Progress can sit at 20% or 60% for several minutes without moving. That’s normal. Do not close the window.
If DISM gets stuck permanently, mount a Windows ISO, point DISM to the install.wim file with /Source, and run it again. That’s the manual workaround when servers fail.
Run sfc /scannow again after DISM
This step is not optional. DISM rebuilds the cache, but it doesn’t repair the damaged files themselves. So type sfc /scannow one more time. In my case, the first run reported unfixable errors and the second run finished with «did not find any integrity violations». That single line was worth more than any registry cleaner.
chkdsk C: /f /r: checking the hard drive itself
If your PC freezes, boots slowly or files vanish, the problem isn’t Windows. It’s the disk. Run:
chkdsk C: /f /r
The /f flag fixes file system errors and /r locates bad sectors and recovers readable data. It’ll ask if you want to schedule the check on the next restart. Say yes. On a 512 GB SSD with 70% full, it took about 40 minutes during boot. On a mechanical drive with terabytes of data, plan for hours.
Don’t pull the plug. Interrupting chkdsk mid-scan is one of the fastest ways to turn a fixable disk into a paperweight.
What these commands actually fixed for me
After running the full sequence, three things changed immediately. The random explorer.exe crashes stopped. Windows Update, which had been failing with error 0x800f081f for months, installed normally. And boot time dropped from almost three minutes to 35 seconds.
That’s the part people don’t believe until they try it. Repairing Windows with CMD commands costs nothing, keeps your files and takes less time than reinstalling drivers one by one.
When CMD is not enough and you should stop insisting
Be honest with yourself here. If sfc and DISM both report clean systems but apps still crash, the issue is probably a dying SSD, faulty RAM or a corrupted user profile. Test the drive with CrystalDiskInfo and the RAM with Windows Memory Diagnostic before wasting more hours.
If SMART data shows reallocated sectors climbing, no command will save that disk. Back up now and replace it. And if Windows won’t even boot, run these same commands from the Recovery Environment: Advanced options, Troubleshoot, Command Prompt. The syntax doesn’t change.
Quick checklist to copy
- Open CMD as administrator.
- Run sfc /scannow and wait for the result.
- If it fails, run DISM /Online /Cleanup-Image /RestoreHealth.
- Run sfc /scannow again to confirm the repair.
- Run chkdsk C: /f /r and let it finish on reboot.
Five commands, zero euros, no formatting. Before you wipe your PC because some forum told you to, spend one afternoon with CMD. Worst case, you learn what’s actually broken. Best case, you save your entire setup and look like the person who fixes everyone else’s laptop.
