# How to Repair Windows Without Reinstalling > Repair a damaged Windows installation in escalation order: Startup Repair, sfc, DISM, chkdsk, System Restore and bootrec, least destructive first. - Source: https://zepe.online/guides/repair-windows-7 - Author: Robert Moca (https://zepe.online/author/robert-moca) - Topic: Updates and recovery - Published: 2026-06-21T09:00:00+00:00 - Updated: 2026-07-24T09:00:00+00:00 - Author: Zepe editorial team (https://zepe.online/editorial-standards) - Image: https://zepe.online/img/repair-windows-7-featured-3caf0468db.webp ## The short answer Work in escalation order: **Startup Repair**, then `sfc /scannow`, then `DISM /Online /Cleanup-Image /RestoreHealth`, then `chkdsk C: /f /r`, then System Restore. Consider a reset only after all of those, because each step costs more. ## Key takeaways - sfc repairs system files from a local store; if that store is itself damaged, DISM must repair it first, which is why sfc sometimes reports it cannot fix things. - chkdsk /r takes hours on a large drive and cannot be safely interrupted, so start it when you can leave the machine alone. - System Restore reverts system files, drivers and the registry, but does not touch your documents. - If the drive is physically failing, every repair step makes it worse. Image the drive first and diagnose second. 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. > **Careful — Before anything else, consider the drive** > > If the machine has been slow, freezing, or producing read errors, the drive may be failing. Repair tools write to the disk, and writing to a failing disk accelerates the loss. Check SMART status first, and if it is questionable, image the drive before running anything else. Data recovery is a specialist job and the guides here will not help with it. **Figure: Repair escalation order** Work down the list. Each step costs more than the one above it, and most machines are fixed in the first three. - **Startup Repair** — Automated. Fixes boot configuration. Costs nothing. - **sfc /scannow** — Repairs protected system files from the local component store - **DISM RestoreHealth** — Repairs the store that sfc draws from. Run when sfc cannot fix things - **chkdsk C: /f /r** — Filesystem and bad-sector repair. Hours, and cannot be interrupted - **System Restore** — Reverts system files and registry to an earlier point. Keeps documents - **Reset or clean install** — Last resort. Removes applications and settings ## 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. ### Run Startup Repair 1. Get into the recovery environment. From Windows: **Settings → System → Recovery → Advanced startup → Restart now**. If Windows will not boot, it usually appears by itself after two failed starts. You can force that by powering off with the button during boot, twice. 2. Choose **Troubleshoot → Advanced options → Startup Repair**. 3. Pick your account and let it run. It can take fifteen minutes and may restart on its own. A report saying it could not repair the PC is common and does not mean the machine is unrecoverable. 4. On Windows 7, boot from the installation disc and choose **Repair your computer**. Windows 7 machines often also have a recovery partition reachable with F8 during boot. ## 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. ### Run System File Checker 1. Open an elevated Command Prompt: **Win + X**, then **A**. It must be elevated. Without administrator rights the command refuses to run. 2. Run `sfc /scannow` and let it reach 100%. 3. Read the result carefully. *Found corrupt files and successfully repaired them* means done. *Found corrupt files but was unable to fix some of them* means go to DISM next. > **Key point — Why sfc sometimes cannot repair** > > It repairs files by copying from a local store. If that store is itself damaged, there is nothing intact to copy from, and sfc reports failure through no fault of its own. DISM repairs the store, which is exactly why the two commands are run in that order. ## 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. > **Careful — Do not interrupt chkdsk /r** > > On a multi-terabyte drive it can run for several hours. Interrupting it partway through a repair can leave the filesystem in a worse state than it started. Begin it when you can leave the machine alone, and on a laptop, leave it plugged in. ## 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. ### Roll back to a restore point 1. Press **Win + R**, type `rstrui` and press Enter. From the recovery environment: Troubleshoot → Advanced options → System Restore. 2. Choose a restore point from before the problem started. 3. Click **Scan for affected programs** before confirming. This lists exactly what will be removed or restored, which is worth reading rather than skipping. 4. Confirm and let the machine restart. 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](https://zepe.online/guides/delete-temp-files-windows) 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. **Boot repair commands** | Command | What it does | | --- | --- | | `bootrec /fixmbr` | Writes a new master boot record | | `bootrec /fixboot` | Writes a new boot sector | | `bootrec /scanos` | Scans all disks for Windows installations | | `bootrec /rebuildbcd` | Rebuilds the boot configuration data store | | `sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows` | Runs sfc against an offline installation | | `chkdsk C: /f /r` | Runs offline, where C: is not in use | 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](https://zepe.online/guides/best-windows-version) covers the realistic options, including what to do with hardware that cannot take Windows 11. > **Editor's note — When to stop repairing** > > If sfc, DISM and chkdsk all come back clean and the machine is still misbehaving, stop repairing. The fault is probably not file corruption at all, and running the same commands a fourth time achieves nothing. Look at hardware instead: run the built-in Memory Diagnostic, check the drive's SMART data, and pull out anything you added recently. At that point [a reset](https://zepe.online/guides/factory-reset-windows-7-8) is a reasonable next step rather than an admission of defeat. ## Common questions ### What is the difference between sfc and DISM? sfc repairs Windows system files by copying from a local component store. DISM repairs that store itself, pulling replacement files from Windows Update. If the store is damaged, sfc has nothing intact to copy from and reports that it could not repair. Run DISM first in that case, then sfc again. ### Will System Restore delete my files? No. It reverts system files, drivers, the registry and installed programs to an earlier point, and leaves documents, photos and email alone. Programs installed after the restore point will be removed; click **Scan for affected programs** before confirming to see exactly which. ### How long does chkdsk take? With `/r` it can run for several hours on a large drive, because it checks the disk surface sector by sector. Do not interrupt it partway through a repair. If you just want to know whether there is a problem, `chkdsk C: /scan` runs online in minutes and reports without fixing. ### How do I repair Windows 7 without the installation disc? Most Windows 7 machines have a recovery partition reachable by pressing F8 during boot and choosing **Repair your computer**. From there you get Startup Repair, System Restore and a Command Prompt. If the manufacturer's recovery partition has been removed, a disc or USB is the only route into the recovery environment. ## Sources - [sfc — Windows commands reference](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/sfc) — Microsoft Learn. Supports: That sfc verifies protected system files against a cached copy, the /scannow switch, and the offline switches used from recovery. - [chkdsk — Windows commands reference](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/chkdsk) — Microsoft Learn. Supports: The behaviour of the /f, /r and /scan switches and the requirement to schedule a restart for a volume in use. - [Recovery options in Windows](https://support.microsoft.com/en-us/windows/recovery-options-in-windows-31ce2444-7de3-818c-d626-e3b5a3024da5) — Microsoft Support. Supports: Reaching the recovery environment, Startup Repair, and System Restore, including what System Restore does and does not affect. ## Related guides - https://zepe.online/guides/factory-reset-windows-7-8 - https://zepe.online/guides/best-windows-version - https://zepe.online/guides/delete-temp-files-windows --- © 2026 Zepe. Windows is a trademark of Microsoft Corporation; this site is not affiliated with Microsoft.