How to Use System File Checker (SFC) to Repair Corrupted Windows 11 Files

First, you need elevated privileges to run SFC. Press Windows + X to open the Power User menu, then click Windows Terminal (Admin) or Command Prompt (Admin). Alternatively, click the Start button, type cmd or terminal, right-click the result, and select Run as administrator.

When the User Account Control (UAC) prompt appears, click Yes to grant administrator privileges.

Execute the standard System File Checker scan by typing the following command and pressing Enter:

sfc /scannow

This command scans all protected system files and replaces corrupted files with cached copies from %WinDir%\System32\dllcache. The scan typically takes 5-60 minutes depending on your system speed and the number of files to check.

You'll see a progress percentage that updates as the scan proceeds. Don't interrupt this process or close the window.

After the scan completes, SFC will display one of these messages:

For detailed information about what was repaired, check the SFC log file:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.txt

If SFC reports it found corrupt files but couldn't fix them, run the Deployment Image Servicing and Management (DISM) tool first. DISM can download fresh system files from Windows Update to repair the local component store that SFC relies on.

Execute this command in your admin command prompt:

DISM /Online /Cleanup-Image /RestoreHealth

This process requires an internet connection and may take 10-30 minutes. DISM will download replacement files from Microsoft's servers to fix the Windows component store.

After DISM completes successfully, run SFC again:

sfc /scannow

If Windows won't boot normally or SFC fails repeatedly, you can run it from the Windows Recovery Environment (WinRE). There are two ways to access WinRE:

Method 1 - From Windows Settings:

Go to Settings > System > Recovery, then under Advanced startup, click Restart now.

Method 2 - Using Installation Media:

Boot from a Windows 11 installation USB or DVD. When the Windows Setup screen appears, click Next, then click Repair your computer in the bottom-left corner.

From either method, navigate to Troubleshoot > Advanced options > Command Prompt.

Before running SFC in the recovery environment, you must identify which drive contains your Windows installation. Drive letters often change in WinRE.

Use these commands to locate your Windows drive:

diskpart
list volume
exit

Look for a volume with enough space to contain Windows (typically 20GB+). Then test each likely drive by checking for the Windows folder:

dir C:\Windows
dir D:\Windows
dir E:\Windows

The correct drive will show the Windows directory with subdirectories like System32, SysWOW64, and others.

Common scenarios:

• If C: shows Windows folder: Your Windows drive is C:
• If D: shows Windows folder: Your Windows drive is D:
• If no drive shows Windows: Try other letters or check if drives are encrypted

Once you've identified your Windows drive (let's assume it's D: for this example), run SFC with the offline parameters:

sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows

Replace D: with your actual Windows drive letter. The parameters mean:

• /offbootdir=D:\ - Specifies the location of the offline boot directory
• /offwindir=D:\Windows - Specifies the location of the offline Windows directory

The scan will proceed similarly to the online version but may take longer since it's running from the recovery environment.

SFC offers several other switches for specific situations:

Scan on next boot only:

sfc /scanonce

Scan on every boot until cancelled:

sfc /scanboot

Cancel scheduled boot scans:

sfc /cancel

Enable Windows File Protection (if disabled):

sfc /enable

You can also run SFC from PowerShell with the same syntax. Open Windows PowerShell (Admin) and use the same commands.

If SFC continues to fail or you need detailed information about what was repaired, examine the SFC log files. The main log is stored in the CBS (Component-Based Servicing) log:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.txt

Open the sfcdetails.txt file on your desktop to see exactly which files were scanned, repaired, or couldn't be fixed.

Common troubleshooting steps:

• Access denied errors: Ensure you're running as administrator and temporarily disable antivirus software
• Scan hangs or freezes: Boot into Safe Mode and retry, or use the WinRE method
• Persistent corruption: Run chkdsk /f /r to check for disk errors first
• SFC finds no issues but problems persist: Consider running Windows Memory Diagnostic or performing a clean Windows installation