System File Checker (SFC) is one of the most useful built-in Windows tools for diagnosing and repairing corrupted system files. If your Windows 11 or Windows 10 PC has started crashing, freezing, displaying unexpected error messages, or behaving unusually after an update, running an SFC scan is often one of the first troubleshooting steps to try.
The System File Checker scans protected Windows system files for corruption, missing files, or unauthorized changes. When it finds a problem, it automatically attempts to replace the damaged file with a healthy copy stored by Windows, help restore system stability without affecting your personal files or installed applications.
In this guide, you’ll learn what System File Checker is, when you should use it, how the sfc /scannow command works, what the scan results mean, and what to do if SFC cannot repair all corrupted files. We’ll also explain when to use the Deployment Image Servicing and Management (DISM) tool before running SFC for the best chance of fixing Windows system file corruption.
Post Contents :-
- 1 What Is System File Checker (SFC)?
- 2 When Should You Run an SFC Scan?
- 3 How Does System File Checker Work?
- 4 How to Run sfc /scannow (Step-by-Step)
- 5 Other Useful SFC Commands Explained
- 6 How to Read the SFC Scan Results
- 6.1 Windows Resource Protection did not find any integrity violations
- 6.2 Windows Resource Protection found corrupt files and successfully repaired them
- 6.3 Windows Resource Protection found corrupt files but was unable to fix some of them
- 6.4 Windows Resource Protection could not perform the requested operation
- 7 Common SFC Errors and How to Fix Them
- 8 When SFC Cannot Repair Corrupted Files
- 9 Run DISM Before Trying SFC Again
- 10 Frequently Asked Questions (FAQ)
What Is System File Checker (SFC)?
System File Checker (SFC) is a built-in Windows command-line utility that scans and repairs protected operating system files. Developed by Microsoft, it helps maintain the integrity of Windows by verifying that essential system files have not been modified, deleted, or corrupted.
Windows relies on thousands of system files to boot correctly, load drivers, run built-in applications, and perform everyday tasks. If one or more of these files becomes damaged, whether due to a failed Windows update, sudden power loss, malware, disk errors, or software conflicts, you may experience problems such as:
- Frequent system crashes or Blue Screen of Death (BSOD) errors
- Random freezing or application crashes
- Missing or corrupted Windows features
- Startup and boot problems
- Unexpected error messages
- Poor system stability after an update
The System File Checker compares the current system files on your PC with the original protected versions stored in the Windows Component Store. If it detects that a protected file has been altered or is missing, it automatically replaces it with a correct copy whenever possible.
Unlike third-party repair tools, SFC is completely free and included with every modern version of Windows, including Windows 11 and Windows 10. Because it only repairs protected Windows system files, it does not delete your personal documents, photos, videos, or installed applications.
For this reason, Microsoft recommends running an SFC scan as one of the first troubleshooting steps whenever Windows begins behaving unexpectedly due to possible system file corruption.
When Should You Run an SFC Scan?
You don’t need to run System File Checker as part of regular PC maintenance. Instead, use it when Windows shows signs that important system files may be corrupted or missing.
Here are some common situations where running an SFC scan can help:
Your PC Keeps Crashing or Freezing
If Windows crashes randomly, freezes during normal use, or frequently displays a Blue Screen of Death (BSOD), corrupted system files may be causing the problem. Running sfc /scannow can repair damaged files that affect system stability.
Windows Features Stop Working
Built-in Windows tools such as Settings, File Explorer, Start menu, Windows Search, or Task Manager may stop responding or fail to open if their required system files are corrupted.
After a Failed Windows Update
Occasionally, a Windows update may not install correctly or may become interrupted due to a power outage or unexpected restart. In such situations, SFC scan can help restore damaged system files left behind by an incomplete update.
You See Missing DLL or System File Errors
Errors mentioning missing or corrupted system files, such as DLL-related messages or Windows Resource Protection errors, often indicate that an SFC scan is worth trying.
Your Computer Is Running Unusually Slow
If you notice your computer is slower, crashes more often than usual, or behaves unpredictably without an obvious cause, corrupted system files could be one of several possible reasons. While SFC isn’t a performance optimization tool, it can resolve slowdowns caused by damaged Windows components.
After Removing Malware
Even after malware has been successfully removed, it may leave behind damaged or modified Windows system files. Running SFC helps restore these files to their original state and improves overall system stability.
Tip: Before making major repairs, restart your computer and install any pending Windows updates. If the problem persists, running
sfc /scannowis a safe first step because it only checks and repairs protected Windows system files without affecting your personal data.
How Does System File Checker Work?
When you run the sfc /scannow Command, Windows starts the System File Checker (SFC) utility and performs a thorough scan of all protected operating system files.
Instead of checking every file on your computer, SFC focuses only on essential Windows system files that are required for the operating system to function correctly. These include files used by Windows components, built-in services, drivers, and core applications.
Here’s what happens during the scan:
- Scans protected Windows system files to detect missing, corrupted, or modified files.
- Verifies each file’s integrity by comparing it with the trusted version stored in the Windows Component Store (WinSxS).
- Automatically replaces damaged files with a healthy copy if one is available.
- Records the results in the Windows Component-Based Servicing (CBS) log, allowing you to review what was repaired or identify files that could not be repaired.
The scan typically takes 5 to 20 minutes, depending on your computer’s performance and the size of your Windows installation. During this time, avoid closing the Command Prompt or restarting your PC.
It’s important to understand that SFC can only repair files if Windows has a healthy backup copy available. If the Windows Component Store itself is damaged, SFC may display a message stating that it found corrupt files but couldn’t repair some of them. In such cases, you’ll usually need to repair the Component Store using the DISM tool before running SFC again.
Good to know: System File Checker only scans protected Windows system files. It does not repair corrupted personal files, Microsoft Office documents, photos, videos, or files belonging to third-party applications.
How to Run sfc /scannow (Step-by-Step)
Running the System File Checker (SFC) scan is straightforward and only takes a few steps. The scan checks all protected Windows system files and automatically repairs any corruption it can fix.
Step 1: Open Command Prompt as Administrator
- Press the Windows key and type Command Prompt.
- Right-click Command Prompt and select Run as administrator.
- Click Yes if prompted by User Account Control (UAC).
Tip: On Windows 11, you can also press Windows + X and select Windows Terminal (Admin). The SFC command works the same way in Windows Terminal.
Step 2: Run the SFC Scan
In the Command Prompt window, type the following command and press Enter:
sfc /scannow
Windows will start scanning all protected system files. Depending on your PC’s performance, the process usually takes 5 to 20 minutes. During this time:
- Keep the Command Prompt window open.
- Don’t close or restart your computer until the scan reaches 100%.
- You can continue using your PC, although performance may be slightly slower during the scan.
Step 3: Wait for the Scan to Finish
Once the scan is complete, Windows will display one of several result messages indicating whether any problems were found and if they were repaired successfully.
We’ll explain what each of these messages means and what to do next in the following sections.
Note: If you’re unable to run the command or receive an error stating that you must be an administrator, close the Command Prompt window and reopen it using Run as administrator before trying again.
Other Useful SFC Commands Explained
While sfc /scannow is the most commonly used command, the System File Checker utility includes several other options that can be helpful in specific situations. These commands allow you to verify system files, scan individual files, or repair an offline Windows installation.
| Command | What It Does |
|---|---|
sfc /scannow | Scans all protected Windows system files and automatically repairs any corrupted files it can fix. This is the command most users should use. |
sfc /verifyonly | Scans protected system files for corruption but does not attempt to repair them. Useful if you only want to check the integrity of system files. |
sfc /scanfile=<file path> | Scans and repairs a specific protected system file instead of checking the entire system. |
sfc /verifyfile=<file path> | Verifies whether a specific protected system file is corrupted without repairing it. |
sfc /offbootdir=<drive> /offwindir=<Windows folder> | Runs an offline scan on a Windows installation that won’t boot. Commonly used from Windows Recovery Environment (WinRE). |
Which Command Should You Use?
For most users, the answer is simple:
sfc /scannow
It performs a complete scan of all protected Windows system files and automatically repairs any corruption it finds. If you’re troubleshooting crashes, Windows errors, or system instability, this is the recommended command to run.
The other SFC switches are primarily intended for advanced troubleshooting or special scenarios, such as checking a single system file or repairing an offline Windows installation that cannot start normally.
Tip: Unless you’re following specific troubleshooting instructions,
sfc /scannowis the only SFC command you’ll need in most situations.
How to Read the SFC Scan Results
After the scan finishes, System File Checker displays a message explaining the outcome. Understanding these results will help you decide whether your system files were successfully repaired or if additional troubleshooting is needed.
Windows Resource Protection did not find any integrity violations
What it means: No corrupted or missing protected Windows system files were found. Your operating system files are intact.
What to do next: If you’re still experiencing crashes, freezes, or other issues, the problem is likely caused by something else, such as faulty drivers, disk errors, failing hardware, or third-party software.
Windows Resource Protection found corrupt files and successfully repaired them
What it means: SFC detected corrupted system files and replaced them with healthy copies.
What to do next: Restart your computer and check whether the issue has been resolved. In many cases, Windows will function normally after the repaired files are loaded.
Windows Resource Protection found corrupt files but was unable to fix some of them
What it means: SFC found damaged system files but couldn’t repair all of them. This usually happens when the Windows Component Store (WinSxS) is also corrupted.
What to do next: Run the DISM tool to repair the Windows image, then run sfc /scannow again. We’ll cover these steps later in this guide.
Windows Resource Protection could not perform the requested operation
What it means: Windows couldn’t complete the scan. Possible causes include disk errors, file system corruption, or interference from another process.
What to do next:
- Restart your computer and try running SFC again.
- Run the CHKDSK utility to check for disk errors.
- If necessary, run SFC from Safe Mode or the Windows Recovery Environment (WinRE).
Tip: If SFC reports that it repaired files successfully, it’s a good idea to restart your PC even if Windows doesn’t specifically prompt you to do so. This ensures the repaired system files are loaded properly.
Common SFC Errors and How to Fix Them
Although System File Checker (SFC) usually runs without problems, you may occasionally encounter an error that prevents the scan from completing. Here are the most common issues and their solutions.
Error: “You must be an administrator running a console session”
Cause: The Command Prompt or Windows Terminal wasn’t opened with administrator privileges.
Fix:
- Close the current Command Prompt window.
- Search for “Command Prompt” or “Windows Terminal”.
- Right-click it and select Run as administrator.
- Run the command again:
sfc /scannow
Error: “Windows Resource Protection could not perform the requested operation”
Cause: This error is often caused by file system corruption, disk errors, or another process preventing SFC from accessing system files.
Fix:
- Restart your computer and try again.
- Run a disk check using:
chkdsk /f
- If the problem persists, boot into Safe Mode and run
sfc /scannowagain.
Error: “Windows Resource Protection found corrupt files but was unable to fix some of them”
Cause: The Windows Component Store used by SFC is damaged, preventing it from replacing corrupted system files.
Fix:
Run the DISM repair command first:
DISM /Online /Cleanup-Image /RestoreHealth
After DISM finishes successfully, restart your PC and run: sfc /scannow again.
The SFC Scan Gets Stuck
Some users notice the scan appears to stop at a certain percentage, such as 20%, 57%, or 73%.
Cause: In many cases, SFC is still scanning large numbers of system files. However, a failing hard drive, SSD issues, or severe system corruption can also cause the scan to hang.
Fix:
- Wait at least 30 minutes before assuming the scan is stuck.
- Restart your PC and try again.
- Check your drive for errors using CHKDSK.
- If the issue continues, run DISM before attempting another SFC scan.
Tip: Most SFC errors are related to corruption in the Windows Component Store. If SFC cannot complete the repair, running DISM first usually resolves the underlying issue and allows SFC to repair the remaining system files successfully.
When SFC Cannot Repair Corrupted Files
While System File Checker is an effective repair tool, it isn’t able to fix every type of system corruption. In some cases, the scan may finish with the message:
“Windows Resource Protection found corrupt files but was unable to fix some of them.”
This doesn’t necessarily mean your Windows installation is beyond repair. It simply indicates that SFC couldn’t replace one or more corrupted system files with a healthy copy.
Common reasons include:
- The Windows Component Store (WinSxS) is corrupted.
- The damaged files are in use by Windows and can’t be replaced while the operating system is running.
- Disk errors are preventing Windows from reading or writing files correctly.
- The corruption is more extensive than SFC can repair on its own.
When this happens, don’t keep running sfc /scannow repeatedly. If the first scan can’t repair the files, running it again usually produces the same result unless the underlying problem has been fixed.
Instead, the next step is to use the Deployment Image Servicing and Management (DISM) tool.
DISM /Online /Cleanup-Image /RestoreHealth
DISM repairs the Windows Component Store that SFC relies on to restore corrupted system files. Once DISM completes successfully, running sfc /scannow again often repairs the remaining corrupted files.
If both DISM and SFC are unable to fix the problem, you may need to consider more advanced recovery options, such as System Restore, an in-place repair upgrade, or Reset this PC, depending on the severity of the corruption.
Run DISM Before Trying SFC Again
If System File Checker reports that it found corrupted files but couldn’t repair them, the next step is to run the Deployment Image Servicing and Management (DISM) tool.
Unlike SFC, which repairs individual protected system files, DISM repairs the Windows Component Store (WinSxS)—the repository that SFC uses to replace damaged files. If this component store is corrupted, SFC won’t have a healthy source from which to restore system files.
Step 1: Open Command Prompt as Administrator
Search for Command Prompt, right-click it, and select Run as administrator.
Step 2: Run the DISM Repair Command
Type the following command and press Enter:
DISM /Online /Cleanup-Image /RestoreHealth
The scan may take 10 to 30 minutes, depending on your system and the extent of the corruption. Keep your PC connected to the internet, as DISM may download healthy files from Windows Update if needed.
Step 3: Restart Your Computer
Once the command completes successfully, restart your PC to ensure the repaired Windows image is loaded.
Step 4: Run SFC Again
After restarting, open Command Prompt as Administrator and run:
sfc /scannow
SFC should now be able to repair any remaining corrupted system files using the repaired Component Store.
Tip: If DISM reports an error or cannot complete successfully, check your internet connection and try the command again. In more severe cases, you may need to run DISM from the Windows Recovery Environment (WinRE) or use a Windows installation media as the repair source.
Frequently Asked Questions (FAQ)
Yes. System File Checker is a built-in Microsoft utility designed to scan and repair protected Windows system files. It does not delete your personal files, installed applications, or documents, making it safe to use whenever you suspect system file corruption.
In most cases, an sfc /scannow scan takes between 5 and 20 minutes. However, it may take longer on older computers or systems with slower hard drives.
No. SFC only scans and repairs protected Windows system files. Your photos, videos, documents, downloads, and installed applications remain unchanged.
For most problems, run SFC first. If SFC reports it found corrupted files but couldn’t repair some, run the DISM command to repair the Windows Component Store. After DISM finishes, run sfc /scannow again.
While you can close the Command Prompt window or restart your PC, it’s not recommended. Interrupting the scan prevents SFC from completing its repair process. For the best results, allow the scan to reach 100% before taking any further action.
There’s no need to run SFC regularly as part of routine maintenance. It’s best used when Windows is experiencing issues such as crashes, freezes, startup problems, or unexpected error messages that may be caused by corrupted system files.
It can help if the BSOD is caused by corrupted Windows system files. However, Blue Screen errors can also result from faulty drivers, failing hardware, memory problems, or disk issues. If SFC doesn’t resolve the problem, additional troubleshooting may be required.
Yes. The System File Checker utility is included with both Windows 11 and Windows 10, and the commands are the same on both operating systems.
