How to Run SFC Scan in Windows?
It often happens that some Windows system files become corrupted, which can cause missing features, crashes, or other unexpected behavior. Windows includes a built-in tool called System File Checker (SFC) that scans protected system files and replaces corrupted versions with healthy copies.

How to Run a System File Checker (SFC) Scan
- Open Command Prompt, PowerShell, or Windows Terminal with administrator rights:
- Windows 10/11: Right-click the Start menu and choose Windows Terminal (Admin) or Windows PowerShell (Admin). You can also search for cmd, right-click it, and select Run as administrator.
- Older Windows versions: Right-click the Start menu and choose Command Prompt (Admin), or press Win + X and select the elevated Command Prompt option.

Fix: “You Must Be an Administrator Running a Console Session”
If you see the message “You must be an administrator running a console session in order to use the SFC utility”, it means the command window was opened in normal mode instead of elevated mode.
To fix it, close the current window, search for cmd, PowerShell, or Windows Terminal, then right-click it and choose Run as administrator. After that, run the SFC command again.
Tip: After searching for Command Prompt, you can press Ctrl + Shift + Enter to open it directly with administrator privileges.
- In the elevated command window, type the following command and press Enter:
sfc /scannow

- Wait for the scan to finish. The result will appear after the verification reaches 100%.
How This Command Scans Your PC
System File Checker (SFC) scans protected Windows system files and checks whether critical files are corrupted, missing, or modified. This includes:
- .dll libraries
- .exe system executables
- Core Windows configuration files
- Other protected operating system components
If SFC finds a damaged file, it attempts to replace it automatically with a clean copy stored by Windows.
Older Windows versions used cached replacements from:
C:\Windows\System32\dllcache
In newer Windows versions, replacement files are taken from the Windows Component Store located at:
C:\Windows\WinSxS
After the scan completes, you may see one of the following results:

- Windows Resource Protection did not find any integrity violations: No protected system files are corrupted.
- Windows Resource Protection found corrupt files and successfully repaired them: SFC fixed the damaged files automatically.
- Windows Resource Protection found corrupt files but was unable to fix some of them: Some files could not be repaired and require additional troubleshooting.
When SFC cannot repair all files, you can review the CBS log here:
%WinDir%\Logs\CBS\CBS.log
To extract only the SFC-related entries into a readable text file, run:
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt"
If the component store itself is damaged, run the following command first, then run sfc /scannow again:
DISM /Online /Cleanup-Image /RestoreHealth
After DISM finishes, open the sfcdetails.txt file from your desktop to review the entries related to files SFC checked or repaired.
Dism /Online /Cleanup-Image /RestoreHealth
This did not work for me. It hangs for a minute or so at 20.0% and then I get the following…
Error: 1726
The remote procedure call failed