Corrupted Windows: How to Check and Repair Without Reinstalling

"Just reinstall it" is the most common advice and the most expensive. Reinstalling takes hours, you lose settings, programs, licences — and in a good share of cases the problem would have been solved in fifteen minutes with two tools already built into Windows.

This guide shows how to check whether the system is genuinely corrupted and how to repair it, in the order that works.

What "corrupted Windows" means

Windows depends on thousands of system files. When one is damaged, deleted by accident or replaced by a wrong version, the system keeps working — just with odd behaviour.

How it happens: shutting down mid-update, a power cut, a bad sector on the disk, a badly installed program, aggressive removal by antivirus.

The signs that point to corruption

Worth checking before running commands, because not every problem is corruption.

• Windows' own programs will not open, or open and close instantly
• Missing file or component-not-found messages
• Windows Update failing consistently, even on retry
• Blue screens naming a system file
• System features disappearing — a menu that will not open, a setting that will not save

If your case is low FPS in games or a slow PC, it probably is not corruption — it is configuration, and the path is different.

Step 1: SFC

The System File Checker compares Windows files against the correct versions and replaces anything wrong.

Open Command Prompt as administrator — right-click the Start menu and choose the terminal or prompt option with administrator privileges. Without administrator, the command will not run.

Type:

sfc /scannow

And wait. The scan takes ten to thirty minutes and the progress bar often looks stuck at certain percentages — that is normal, let it finish. Do not close the window partway.

Reading the result

At the end, one of three messages:

• Found no integrity violations — your system files are fine. The problem is something else
• Found and repaired — sorted. Restart and test
• Found but could not repair — this is where most people give up and reinstall. You do not need to: go to step 2

Step 2: DISM, when SFC fails

This is the point almost no tutorial explains well, and it is what makes the difference.

SFC does not invent the correct files — it takes them from a local store inside Windows. If that store is corrupted too, SFC has nowhere to get a good file from, which is exactly why it reports finding the problem but not fixing it.

DISM repairs that store, downloading what is missing. In short: DISM fixes the source, SFC fixes the system.

In the same administrator Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth

This one takes longer — it can exceed half an hour — and needs internet, because it fetches correct files from Microsoft's servers. It also tends to sit at certain percentages for long stretches. Let it run.

Step 3: SFC again

This part is mandatory and the most skipped.

Once DISM finishes, run sfc /scannow one more time. Now the store is healthy, so SFC finally has somewhere to pull the correct files from.

Running DISM and stopping there solves half the job: you fixed the source and never applied the repair.

Restart the PC afterwards.

If even that did not work

When SFC keeps reporting errors after DISM, consider:

A failing disk. A file that re-corrupts shortly after being repaired usually indicates a bad sector. Worth checking drive health — if it is failing, any repair is temporary.

A repair install. There is a middle option between repairing and wiping: reinstalling Windows over itself, keeping files and programs. It takes time, but it is not the same as losing everything.

Then, a clean install. As a last resort, not a first one.

What these tools do not do

Worth setting expectations, because many people run them hoping for something else.

SFC and DISM do not make your PC faster. They repair damaged files — if your files are intact and your PC is slow, the result will be "no integrity violations found" and nothing will change.

Slowness and low FPS have other causes: power plan, background processes, badly configured drivers, memory in single channel. Those are configuration problems, not integrity problems.

They are different things, and confusing the two means losing time on a command that was never going to help.