DISM Commands Explained: The One Repair Command Worth Running — and When It Means Deeper Trouble
Somewhere in a forum thread about a Windows problem, somebody has told you to "run DISM." Usually with a wall of commands, no explanation, and a confidence level that should make you nervous. DISM is a real repair tool — I use it on the bench weekly — but most of what it does has nothing to do with fixing a broken PC, and a couple of its commands can make a bad situation worse.
Here is what DISM actually is, the one command sequence that genuinely repairs things, and the pattern I watch for that says the corruption is a symptom, not the disease.
What DISM actually does
DISM stands for Deployment Image Servicing and Management. It was built for IT departments to prepare and modify Windows installation images. Buried inside it is the part home users care about: it can check and repair the component store — the master library of system files Windows keeps in the WinSxS folder and uses as the source of truth when it updates or repairs itself.
When that library develops a corrupt OS image — damaged or missing files in the store itself — you get a specific flavor of misery: Windows Updates that fail over and over with cryptic error codes, System File Checker reporting that it "found corrupt files but was unable to fix some of them," features that won't install, and random errors that no amount of rebooting shakes loose.
The three health commands, in the right order
CheckHealth — a ten-second question
Asks Windows whether corruption has already been flagged. It repairs nothing and scans nothing new. Fine to run, tells you little.
ScanHealth — the real inspection
Actually reads through the component store looking for damage. Takes several minutes, changes nothing. Useful if you want a verdict before committing to a repair.
RestoreHealth — the one that fixes things
Scans the store and repairs what it finds, pulling clean copies of damaged files from Windows Update. This is the command the whole exercise is about, and the only one you really need.
The one repair worth running yourself
Right-click the Start button, choose Terminal (Admin) or Windows PowerShell (Admin), and run:
Let it finish — it can sit at certain percentages for a long time, and that is normal, not frozen. Stay connected to the internet so it can fetch clean files. When it completes, run the companion check that repairs the working copies of system files using the store you just fixed:
That pair — RestoreHealth, then SFC — is the entire legitimate home version of this repair. If you have ever wondered how to check your system for untrusted or damaged files, this is the honest answer: SFC verifies every protected system file against its known-good signature and replaces anything that fails. Run together, the two commands fix a genuinely large share of "Windows is acting haunted" complaints: failed updates, odd crashes, features that stopped working after a bad shutdown.
The forum commands to leave alone
DISM has switches that revert pending update actions, strip out components, and reset the image in ways meant for technicians working on deployment images. Run against a live system with a failing drive, some of them can turn a bootable-but-glitchy PC into one that won't start. If a command you found online isn't the RestoreHealth line above, understand exactly what it does before you press Enter — or don't press Enter.
When corruption is a symptom, not the disease
Here is the part the forum threads skip. System files do not corrupt themselves for fun. When RestoreHealth fails with source errors, or SFC finds new corruption every week, or the same machine keeps landing back in the same broken state, the corruption is being caused by something — and the usual suspects are a hard drive or SSD that is quietly dying and mangling data as it writes, RAM that flips bits under load, or malware that has replaced or damaged system files on purpose.
On our bench, a machine with recurring corruption gets the storage health read properly, the memory tested, and the system checked for infection before anyone runs another repair command. Repairing files onto a failing drive is shoveling water out of a boat without patching the hole. Our $75 diagnostic finds the hole, and it's credited toward the repair if you move forward with us. If the corruption traces back to an infection, our flat-rate virus removal deals with the cause instead of the symptom.
Ran the commands and it's still broken?
Then it's time to find out what keeps breaking it. Drop the machine off in Somerville — diagnostic fee credits toward the fix.