- Safe Mode<\/strong><\/a><\/li>
- Recovery Mode<\/a><\/strong><\/li><\/ul><\/li><\/ol>\n\n\n\n
What is SFC?<\/h2>\n\n\n\n
IMPORTANT: <\/strong>The SFC process will take approximately 5-10 minutes, so make sure not to turn off the computer or close out the Command Prompt!<\/p>\n\n\n\n
SFC stands for System File Checker. While the CHKDSK<\/a> command scans sectors of your hard drive, SFC verifies the integrity of specific Windows system files. If you\u2019re receiving an error about missing Windows .dll files, getting Blue Screens of Death, or if particular Windows functions are crashing in general even when booting, it\u2019s a good indicator that you\u2019ll want to run SFC.<\/p>\n\n\n\nHow to run SFC<\/h2>\n\n\n\n
Running the SFC command is straightforward. For basic troubleshooting, you\u2019ll only need to run the scannow command. To display the list and description of all SFC commands that you can run, type sfc \/?. You can also check out Microsoft\u2019s support page<\/a> for a list and description of all SFC parameters.<\/p>\n\n\n\n
- Open an elevated Command Prompt, then type
sfc \/scannow<\/code>.- If you only want to view the issues and don\u2019t want your system to automatically repair them, type
sfc \/verifyonly<\/code>.<\/em><\/li><\/ul><\/li>- Once the scan is complete, you will then receive one of the following messages:
- Windows Resource Protection did not find any integrity violations<\/strong>
- Your system doesn\u2019t have any corrupt files, and nothing needs to be done.<\/li><\/ul><\/li>
- Windows Resource Protection could not perform the requested operation<\/strong>
- Boot into Safe Mode and rerun the
sfc \/scannow<\/code> command.<\/li><\/ul><\/li><\/ul><\/li>- Windows Resource Protection found corrupt files and successfully repaired them.
- Your computer found and was able to fix corrupt files, and nothing needs to be done.<\/li>
- Windows Resource Protection found corrupt files but was unable to fix some of them.<\/strong>
- Your computer found and was not able to fix the corrupt files. At this point, you\u2019ll need to try running SFC in safe mode, recovery mode, run the CHKDSK or DISM command, or perform a repair install.<\/li><\/ul><\/li><\/ul><\/li><\/ol>\n\n\n\n
![\"\"](\"https:\/\/www.sweetwater.com\/sweetcare\/media\/2022\/02\/sfc-in-command-prompt.jpg\")
<\/figure>\n\n\n\nRunning SFC in Command Prompt<\/em><\/p>\n\n\n\n
Return to top<\/a><\/p>\n\n\n\n\n\n
Running SFC in Safe Mode and Recovery Mode<\/h2>\n\n\n\n
Depending on the issue, and if you tried sfc \/scannow in the standard environment<\/a>, there are two other ways you can run the command: Safe Mode and Recovery Mode.<\/p>\n\n\n\n
Safe Mode<\/h3>\n\n\n\n
TIP: <\/strong>If you can\u2019t access the Settings menu, click the Windows <\/strong>icon, select Power, then click Restart<\/strong> while holding the Shift <\/strong>key. This will take you to the Choose an option <\/em>window mentioned in step 3 below.<\/p>\n\n\n\n
When you boot into Safe Mode, specific system files aren\u2019t loaded, and most device drivers are disabled, including audio interfaces and printers. While you can also boot into Safe Mode with Networking (network drivers are also enabled, so you have access to the internet), it\u2019s not completely necessary. Check out Microsoft\u2019s support page<\/a> about booting into Safe Mode and how Safe Mode works.<\/p>\n\n\n\n
- Click the Windows <\/strong>icon on the toolbar, type recovery, then select Recovery options<\/strong>.<\/li>
- Click Advanced setup<\/strong>, then choose Restart now<\/strong>.<\/li>
- When the Choose an option<\/em> window appears, click Troubleshoot<\/strong>, select Advanced options<\/strong>, choose Startup Settings<\/strong>, then click Restart<\/strong>.<\/li>
- When the computer reboots, you will now see the Startup Settings<\/em> menu.<\/li>
- Press F4<\/strong> or the 4<\/strong> key to select Safe Mode. If you want access to the internet while in Safe Mode, press F5<\/strong> or the 5 <\/strong>key to enter Safe Mode with Networking.<\/li>
- Run the SFC command as outlined above.<\/li><\/ol>\n\n\n\n
Recovery Mode<\/h3>\n\n\n\n
IMPORTANT: <\/strong>If you need to enter Recovery Mode, you must create recovery media with the Media Creation tool<\/strong><\/a>. You\u2019ll also need to change the boot load order to make the bootable media drive the first boot option. Since the instructions vary per motherboard, be sure to check out its User Manual.<\/p>\n\n\n\n
If you\u2019re still having issues after running SFC in Safe Mode, the other option is to run it in Windows Recovery Mode. Also referred to as Windows RE or WinRE, Recovery Mode is a barebones version of Windows installed onto a separate partition<\/a> of your primary system drive immediately after the boot partition. Recovery Mode is primarily used when your computer has issues during the boot process. Check out Microsoft\u2019s guide<\/a> to learn more about the Windows Recovery Environment and how to get started.<\/p>\n\n\n\n
- With your computer turned off, insert your bootable media, turn the computer on, then enter the BIOS.<\/li>
- Change the boot order so the bootable media drive is the first option, then exit.
- Refer to your motherboard\u2019s User Manual to learn how to change the boot order.<\/li><\/ul><\/li>
- When the Install Windows screen appears, click Next<\/strong>, then choose Repair your computer<\/strong>.<\/li>
- On the next screen (System Recovery Options), click Next<\/strong>, then select Command Prompt<\/strong>.<\/li>
- Once the Command Prompt window opens, type
BCDEdit<\/code> and take note of the volume letter located next to osdevice<\/strong>.<\/li>- Type the following:
SFC \/scannow \/offbootdir=<volume>:\\ \/offwindir=<volume>:\\windows<\/code><\/li><\/ul><\/li><\/ol>\n\n\n\nIf you can’t enter the Windows Recovery Environment<\/h4>\n\n\n\n
By default, Windows Recovery Environment is enabled, but if by any chance you\u2019re having issues, it might be because it\u2019s disabled. If this is the case, you will need to enable it via the command prompt.<\/p>\n\n\n\n
- Launch an elevated Command Prompt and type
reagentc \/info<\/code> to check if it is disabled.<\/li>- If it\u2019s disabled, type
reagentc \/enable<\/code>.<\/strong><\/li><\/ol>\n\n\n\n - If it\u2019s disabled, type
- Launch an elevated Command Prompt and type
- On the next screen (System Recovery Options), click Next<\/strong>, then select Command Prompt<\/strong>.<\/li>
- Click Advanced setup<\/strong>, then choose Restart now<\/strong>.<\/li>
- Click the Windows <\/strong>icon on the toolbar, type recovery, then select Recovery options<\/strong>.<\/li>
- Your computer found and was not able to fix the corrupt files. At this point, you\u2019ll need to try running SFC in safe mode, recovery mode, run the CHKDSK or DISM command, or perform a repair install.<\/li><\/ul><\/li><\/ul><\/li><\/ol>\n\n\n\n
- Windows Resource Protection found corrupt files and successfully repaired them.
- Boot into Safe Mode and rerun the
- Once the scan is complete, you will then receive one of the following messages:
- If you only want to view the issues and don\u2019t want your system to automatically repair them, type
- Recovery Mode<\/a><\/strong><\/li><\/ul><\/li><\/ol>\n\n\n\n