Just the next step →

How to Repair Windows 11 Without Reinstalling It

By Iikka Isosaari · Windows 11 · Updated

Windows 11 problems do not always mean you need to reset or reinstall your PC. Windows includes several built-in repair tools that can fix damaged system files and components while leaving your applications, files, and settings intact.

Before repair commands: save your work, keep a backup of important files, and use Terminal or Command Prompt as Administrator. These commands change Windows files; they are not read-only diagnostics. /Online targets the Windows installation currently running, not an offline installation in recovery.

Repair the Component Store First

Open Terminal or Command Prompt as Administrator. Run DISM to repair the component store used by Windows servicing:

DISM /Online /Cleanup-Image /RestoreHealth

Wait for it to finish successfully. DISM may obtain replacement components from Windows Update. If it fails, record the error instead of repeatedly rerunning the command.

Check Protected System Files

In the same administrator terminal, run:

sfc /scannow

Wait for the scan to complete and read the result. SFC attempts to replace damaged protected files; a successful repair does not prove that an unrelated driver or hardware problem has been fixed.

Restart Windows

Restart after completing the repairs, even if Windows does not explicitly ask you to.

Many system components cannot be fully replaced while Windows is running.

When These Repairs Can Help

SFC and DISM can be useful when you experience:

They will not usually fix hardware failures, third-party driver problems, or malware.

References

Questions about How to Repair Windows 11 Without Reinstalling It

Can Windows system files be repaired without reinstalling the OS?

DISM can repair the component store and SFC can check protected system files. These tools do not guarantee a fix for hardware, driver or application-specific problems.

What should I save before attempting Windows repairs?

Back up important files and record the error messages. If a command fails, note its exact output before trying a different repair path.