The Symptoms of Corrupted System Files
Windows 11 is a massive operating system composed of tens of thousands of individual files. Over time, due to hard drive sector errors, interrupted Windows Updates, or aggressive malware, some of these core files can become corrupted or go missing entirely.
When this happens, you will experience unpredictable instability: the Start Menu might refuse to open, the Settings app might crash immediately upon launching, or you might encounter frequent Blue Screens of Death (BSOD). Before you resort to wiping your hard drive and performing a clean installation of Windows, you should attempt to repair the operating system using two powerful, built-in command-line tools: SFC (System File Checker) and DISM (Deployment Image Servicing and Management).
Step 1: Running the System File Checker (SFC)
The SFC tool is your first line of defense. It scans all protected system files and replaces corrupted versions with a cached, pristine copy stored in a compressed folder within the Windows directory.
- Press the Windows Key, type
cmd, right-click on Command Prompt, and select Run as administrator. - At the prompt, type the following command exactly as written and press Enter:
sfc /scannow
The scan will take between 5 and 15 minutes, depending on the speed of your SSD. Once finished, you will receive one of three messages:
- “Windows Resource Protection did not find any integrity violations.” Your files are fine; your problem lies elsewhere.
- “Windows Resource Protection found corrupt files and successfully repaired them.” The tool worked. Restart your computer and check if the issue is resolved.
- “Windows Resource Protection found corrupt files but was unable to fix some of them.” The local cached copy of the files is also corrupted. This means you must move on to Step 2.
Step 2: Running the DISM Tool
If SFC fails, it’s because the internal Windows component store (the backup repository) is damaged. The DISM tool fixes this by reaching out over the internet to Microsoft’s official Windows Update servers to download fresh, uncorrupted copies of the specific files your system needs.
Because it relies on the internet, ensure your PC is connected to Wi-Fi or Ethernet before proceeding.
- Return to your Administrator Command Prompt window.
- First, we will run the RestoreHealth command. Type the following and press Enter:
DISM /Online /Cleanup-Image /RestoreHealth
Breakdown of the command:
/Online: Tells the tool to target the currently running operating system, rather than an offline Windows image on a USB drive./Cleanup-Image: Tells the tool to perform a deep operation on the system image./RestoreHealth: Instructs the tool to actively download and replace any corrupted files it finds in the component store.
This process often looks like it is stuck at 20% or 40% for several minutes. This is normal. Let it run until it reaches 100% and states “The restore operation completed successfully.”
Step 3: Run SFC One More Time
Now that DISM has successfully repaired the backup repository using Microsoft’s servers, you must run SFC one final time to actually pull those repaired files into your active operating system.
- In the same Command Prompt window, type again:
sfc /scannow
This time, it should successfully repair the files that it failed to fix in Step 1. Once the scan is complete, close the Command Prompt and restart your computer.
Conclusion
The combination of SFC and DISM is the most potent troubleshooting technique available to Windows administrators. By systematically repairing the local cache via the cloud, and then deploying those repaired files to the active system, you can resolve the vast majority of deep-seated Windows 11 instability without losing any personal data or installed applications.