System File Checker: A Guide to Checking and Repairing System Files

What is System File Checker?

System File Checker (SFC) is a built-in Windows utility designed to scan and repair corrupted or missing system files. It checks the integrity of all protected system files and replaces incorrect versions with correct ones from the Windows cache (the WinSxS folders). The utility operates at the system kernel level and is available in all modern versions of Windows, starting with Windows XP.

SFC is particularly useful when the system behaves erratically: random crashes occur, boot errors appear, certain features stop working, or you see messages about corrupted system components. It is the first and often the simplest step in diagnosing problems related to system files.

When to Use SFC?

Run a check if you experience the following symptoms:

• The system periodically displays a Blue Screen of Death (BSOD) with various error codes.
• Some programs or Windows components (e.g., Control Panel, Windows Update) fail to launch or crash with an error.
• System performance has dropped sharply without an obvious cause.
• The system operates incorrectly after removing malware.
• Errors occur during Windows updates.

Important: SFC does not fix issues related to device drivers, registry corruption (except for keys related to system files), or user settings. For more complex scenarios, use other tools like DISM or System Restore.

Preparation Before Running

Before performing the check, it is recommended to:

1. Close all open programs. This reduces the likelihood that SFC will be unable to access files currently in use.
2. Ensure you have administrator privileges. Without them, SFC cannot restore protected files.
3. Check free space on the system drive. The cache and temporary files require free space (at least 1-2 GB).
4. Temporarily disable your antivirus (if active). Some antivirus programs may block SFC's access to system files, causing false positives.

Running the System File Check

The process to launch SFC is straightforward:

1. Open the Start menu and type cmd or PowerShell.
2. In the search results, right-click on "Command Prompt" or "Windows PowerShell" and select "Run as administrator".

   ⚠️ If you are using PowerShell, ensure the execution policy does not block scripts. For SFC this is not critical, but for other commands you may need Set-ExecutionPolicy RemoteSigned.

3. In the opened window, type the command:

   sfc /scannow
   

   and press Enter.
4. The scan will begin. You will see progress in percentages. Do not close the window or interrupt the process.

Interpreting the Results

After completion, SFC will display one of the following messages:

• "Windows Resource Protection did not find any integrity violations."
  System files are fine. No further action is required.
• "Windows Resource Protection found integrity violations and successfully repaired them."
  Corrupted files were replaced with working versions. Restart your computer for changes to take effect.
• "Windows Resource Protection found integrity violations but was unable to fix some of them."
  SFC could not repair all files. This often happens when the system image itself is corrupted or files are locked. You will need an additional step—running DISM.
• "The operation could not be completed. Access to files may be restricted."
  Usually indicates issues with permissions or active file usage. Try running SFC in Safe Mode.

You can check details in the Windows Event Log:

1. Open "Event Viewer" (eventvwr.msc).
2. Navigate to Windows Logs → Application.
3. Find the source "Windows Resource Protection" (SFC) and open events from the time of the scan. It lists specific files that could not be repaired.

What to Do If SFC Did Not Help?

If SFC reports it could not repair files, perform the following actions in the specified order:

1. Run DISM

DISM (Deployment Image Servicing and Management) repairs the Windows image that SFC uses to replace files. Without a healthy image, SFC may not find correct versions.

1. In the same administrator window, type:

   DISM /Online /Cleanup-Image /RestoreHealth
   

   💡 If DISM cannot access repair sources (e.g., without internet), use a Windows installation media:
   DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:X:\Sources\Install.wim:1 /LimitAccess
   where X: is the drive letter of the installation media.

2. The process may take 15-30 minutes. An internet connection is required to download fixes from Microsoft servers.
3. After completion, restart your computer and run sfc /scannow again.

2. Run SFC in Safe Mode

If files are locked by active processes, run SFC in Safe Mode:

1. Press Win + R, type msconfig, and open the Boot tab.
2. Check "Safe boot" and click OK → Restart.
3. After booting into Safe Mode, open an administrator command prompt and run sfc /scannow.

3. Manually Replace Corrupted Files

If a specific corrupted file is known (from the SFC log), you can copy a healthy version from installation media or another computer with the same Windows version. However, this method requires caution and knowledge of system file locations.

Prevention and Recommendations

To minimize the risk of system file corruption:

• Regularly install Windows updates. Many updates contain fixes for system components.
• Avoid manually deleting files from C:\Windows and C:\Program Files. Even if a file seems unnecessary, it may be part of the system.
• Use antivirus with real-time protection. This prevents malware from modifying system files.
• Create System Restore points before installing programs or updates. This allows you to roll back if something goes wrong.
• Do not use "cleaner" utilities (e.g., CCleaner) without understanding what they remove. Some may accidentally delete system files.

Final Steps

After SFC completes successfully (and DISM, if required):

1. Restart your computer once to apply all changes.
2. Check if the original problem (crashes, errors) is resolved.
3. If the problem persists, the issue may not be with system files. Review Event Logs for other errors or consult related guides (e.g., driver or registry diagnostics).

System File Checker is a powerful yet simple tool. Regular use (every 3-6 months) as part of preventive maintenance helps maintain Windows stability without deep system intervention.