Fix Corrupted Windows System Files with DISM

Your Windows installation is likely acting up because critical system files have become corrupted or damaged. You can resolve these stability issues, blue screens, and update failures by using the built-in Deployment Image Servicing and Management tool to replace the broken files with healthy versions.

Why this happens

System file corruption usually occurs due to interrupted Windows updates, improper shutdowns, or failing storage drives. This process forces Windows to verify its core files against a known healthy source.

What you'll need

You will need administrative access to your computer and a stable internet connection, as the tool may need to download fresh files from Windows Update.

Steps

1. 01
   Click the Start button, type CMD, right-click on 'Command Prompt', and select 'Run as administrator' to open the console with full permissions.
2. 02
   Type DISM /Online /Cleanup-Image /RestoreHealth exactly as shown and press Enter.
3. 03
   Wait for the progress bar to reach 100 percent, which can take anywhere from 5 to 20 minutes depending on your hardware performance.
4. 04
   Look for the message 'The restore operation completed successfully' to confirm the repair is finished.
5. 05
   Restart your computer to apply the changes and verify that the system is stable.

Still not working?

If the DISM command finishes but errors persist, the next logical step is to run the System File Checker. Open an elevated Command Prompt again and run sfc /scannow to verify and repair protected system files that DISM might have missed. If you still encounter crashes, check your Event Viewer for specific error codes or investigate your hard drive health, as physical drive failure can cause recurring corruption.

Frequently asked questions

Will this delete any of my personal files or programs?

No, this command only repairs Windows system files. Your documents, photos, and installed applications will remain untouched.

How often should I run this command?

You do not need to run this regularly. It is best used as a troubleshooting step when you experience system instability or after a major Windows update fails.