How to Repair Windows Without Reinstalling

There is a right order to this and it genuinely matters. Each step is more disruptive than the one before, and jumping straight to a reinstall throws away every setting and every application on a machine whose actual problem might have been a single corrupted file. Start at the top even when you are impatient.

Step one: Startup Repair

If Windows will not start at all, begin here. It repairs boot configuration problems on its own and it cannot damage your files, which makes it the safest thing on this page to try first.

Step two: sfc /scannow

System File Checker compares every protected system file against a known-good copy held in a local store and replaces anything that does not match. It is safe, it cannot make matters worse, and it genuinely fixes a real class of problems, so it is worth running even when you are not sure it applies.

Step three: DISM RestoreHealth

From that same elevated prompt, run DISM /Online /Cleanup-Image /RestoreHealth. This repairs the component store itself, pulling replacement files from Windows Update, so the machine needs a working internet connection for it to do anything useful.

Expect it to take ten to thirty minutes, and expect it to sit at 20% for a long while. That is normal and not a hang. When it finishes, run sfc /scannow again: DISM fixes the source, and sfc then uses that source to fix the system files.

Step four: chkdsk

Where sfc and DISM deal with the contents of files, chkdsk deals with the filesystem structure and the disk surface underneath it, which is a different kind of problem entirely. Run chkdsk C: /f /r from an elevated prompt. Because C: is in use it will offer to run at the next restart instead; accept, and reboot.

• `/f` fixes filesystem errors.
• `/r` locates bad sectors and recovers readable information, which is what makes it slow.
• `chkdsk C: /scan` runs online without a restart and reports problems without fixing them. A good first look.

Step five: System Restore

This rolls system files, installed drivers, the registry and installed programs back to a saved point in time, and leaves your documents, photos and email completely alone. If the machine broke right after an update or a driver installation, this is very often the fastest fix available and people skip past it far too readily.

If there are no restore points, System Protection was switched off. Once the machine is healthy, turn it on: Win + R, sysdm.cpl, System Protection tab, Configure. It costs a few percent of the drive and is worth it. Note that a full restore-point history also occupies space, which the guide on deleting temporary files covers.

When Windows still will not boot

If Startup Repair could not sort out the boot configuration, these commands do the same job by hand. Run them from the Command Prompt inside the recovery environment, in the order given.

Run them in that order. If bootrec /fixboot returns *Access is denied*, which is common on UEFI machines, the EFI partition needs assigning a letter with diskpart first, then bcdboot C:\Windows /s X: /f UEFI.

Windows 7 specifically

The tools are the same ones. sfc /scannow and chkdsk behave identically, System Restore is under Control Panel → Recovery, and Startup Repair comes from the installation disc via Repair your computer. The one real difference is that DISM's /RestoreHealth does not exist on Windows 7, which uses the System Update Readiness Tool instead.

The larger point about Windows 7 is that it has received no security updates since January 2020, so a machine you repair today is still an unpatched machine tomorrow. The guide on choosing a Windows version covers the realistic options, including what to do with hardware that cannot take Windows 11.