/

How to Add or Remove an SFC /SCANNOW Context Menu Option in Windows 11

by Ann Conte, IT Technical Writer
How to Add or Remove an SFC SCANNOW Context Menu Option in Windows 11
How to Add or Remove an SFC SCANNOW Context Menu Option in Windows 11

Try our #1 rated endpoint management platform on G2

NinjaOne dashboard screenshot

Automate the Hardest Parts of IT

Key Points

  • Adding SFC /SCANNOW to the Windows 11 context menu gives administrators fast, one-click access to System File Checker for repairing corrupted system files.
  • Create the context menu entry by adding registry keys under HKCR, enabling Windows 11 to launch SFC /SCANNOW with proper elevation and an optional log viewer.
  • To remove the SFC context menu entry, delete the associated registry key; it will immediately restore the default Windows context menu behavior.
  • For enhanced diagnostics, MSPs can use a batch script wrapper that runs SFC, pauses for review, and automatically stores scan logs in the CBS.log file.
  • Common problems (SFC entry not appearing, failing to elevate, or scans not running) are typically resolved by restarting Explorer, confirming elevation parameters, or running DISM before SFC.
  • Integrating SFC /SCANNOW into the context menu streamlines system repair operations, improves technician response time, and standardizes Windows maintenance practices across organizations.

The System File Checker (SFC) tool analyzes and repairs corrupted or missing system files. Many administrators prefer to make it more accessible by adding SFC to the context menu in Windows 11. This allows quick initiation of a system integrity scan without navigating through administrative terminals.

A guide for adding and removing SFC /scannow to the Windows 11 context menu

📌 Prerequisites:

  • You need a Windows 11 device and have administrator privileges on that device.
  • You need to have the ability to modify HKCR and HKLM registry paths.
  • You should already have a familiarity with using an elevated Command Prompt window or PowerShell.
  • It’s best to have an RMM or scripting platform for deployment.
  • You need to have Windows Terminal or Command Prompt installed.

Method 1: Add SFC /SCANNOW to the classic context menu

📌Use Case: This is useful for MSPs who want the option available anywhere.

⚠️Warning: Editing the Registry Editor can lead to some unforeseen consequences for your system. Remember to back up your Registry before making any changes.

  1. Open the Start Menu and search for Notepad to open the program.
  2. Copy this into the document:
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\DesktopBackground\Shell\SFC]
“Icon”=”WmiPrvSE.exe”
“MUIVerb”=”SFC /SCANNOW”
“Position”=”Bottom”
“SubCommands”=””

 

[HKEY_CLASSES_ROOT\DesktopBackground\shell\SFC\shell\001menu]
“HasLUAShield”=””
“MUIVerb”=”Run SFC /SCANNOW”

[HKEY_CLASSES_ROOT\DesktopBackground\shell\SFC\shell\001menu\command]
@=”PowerShell -windowstyle hidden -command \”Start-Process cmd -ArgumentList ‘/s,/k, SFC /scannow’ -Verb runAs\””

 

[HKEY_CLASSES_ROOT\DesktopBackground\shell\SFC\shell\002menu]
“MUIVerb”=”View SFC scan log”
“Icon”=”imageres.dll,-102”

[HKEY_CLASSES_ROOT\DesktopBackground\shell\SFC\shell\002menu\command]
@=”PowerShell (sls [SR] $env:windir\\Logs\\CBS\\CBS.log -s).Line >\”$env:userprofile\\Desktop\\SFCdetails.txt\””

  1. Click File > Save as.
  2. Name the file Add_SFCContextMenu.reg.
  3. Click the dropdown menu next to Save as file type > All files.
  4. Save it in your folder of choice. You can now close Notepad.
  5. Go to the .reg file you saved and double-click it to run it.
  6. Restart the computer to apply the changes.

Method 2: Remove the SFC /SCANNOW context menu entry

⚠️Warning: Editing the Registry Editor can lead to some unforeseen consequences for your system. Remember to back up your Registry before making any changes.

  1. Open the Start Menu and search for Notepad to open the program.
  2. Copy this into the document:

Windows Registry Editor Version 5.00

[-HKEY_CLASSES_ROOT\DesktopBackground\Shell\SFC]

  1. Click File > Save as.
  2. Name the file Remove_SFCContextMenu.reg.
  3. Click the dropdown menu next to Save as file type > All files.
  4. Save it in your folder of choice. You can now close Notepad.
  5. Go to the .reg file you saved and double-click it to run it.

Method 3: Use a script wrapper for enhanced logging

📌Use Case: This is useful for MSPs who want auto-logging.

⚠️Warning: Editing the Registry Editor can lead to some unforeseen consequences for your system. Remember to back up your Registry before making any changes.

  1. Open the Start Menu and search for Notepad to open the program.
  2. Copy this into the document:

SFC /scannow

echo Scan complete. Log saved to %windir%\Logs\CBS\CBS.log

pause

  1. Click File > Save as.
  2. Name the file SFC_scan.bat.
  3. Click the dropdown menu next to Save as file type > All files.
  4. Save the file in a permanent folder where it won’t be accidentally deleted.
  5. You can now close Notepad.
  6. Open the Registry Editor.
  7. Navigate to this address: HKEY_CLASSES_ROOT\*\shell\SFC Scan\command
  8. In the right pane, double-click the (Default) value.
  9. Change the Value data to point to your .bat file location.
  10. Click OK. You can now close the Registry Editor.

Troubleshooting tips for adding SFC /scannow to the context menu

Problem Solution
SFC fails to run. Make sure that the menu entry includes start cmd.exe with elevation.
The entry doesn’t appear in the context menu. Use Show more options in Windows 11 to view classic menu entries.
The Registry changes don’t have any effect. Restart explorer.exe or restart the computer to refresh shell settings.
SFC can’t repair your files. Use DISM first, then run SFC again.
You’re getting access denied errors. Confirm that the context menu entry uses an elevated command invocation.

Repair your files by running SFC scannow using the context menu

Adding SFC /SCANNOW to the context menu gives technicians faster access to one of Windows’ most important repair tools. With a few registry keys, you can streamline integrity checks, automate logging, and reduce time spent opening an elevated Command Prompt window.

Quick-Start Guide

NinjaOne can help you add or remove an SFC /SCANNOW context menu option in Windows 11.

You can use a script to add the SFC /SCANNOW option to the context menu by creating a registry key. To remove the option, simply delete the associated registry key, which will restore the default Windows context menu behavior.

Related topics:

FAQs

No. System File Checker (SFC) only scans and repairs Windows system files, not user-installed applications, so it won’t break your programs or compromise personal data.

Yes. Running SFC /scannow requires an elevated Command Prompt. Any context menu shortcut needs to be configured to launch with Administrator rights.

Yes. The same registry-based context menu method for launching SFC works on Windows 10, Windows 11, and all modern Windows versions that support System File Checker.

Yes, you can run offline repairs. Just use the following command:

SFC /scannow /offbootdir=<drive> /offwindir=<path>

However, please note that SFC offline can’t be launched from a context menu. It needs to be run manually from Windows Recovery or Command Prompt.

SFC stores its output in the standard Windows log file located at:

%windir%\Logs\CBS\CBS.log

This log will contain scan results, repairs, and system file operations.

Yes. Windows 11 supports SFC, and SFC /scannow will work there the same way it works in Windows 10. It will scan and repair critical system files to restore OS integrity.

You can add custom items by editing the Windows Registry at keys like HKEY_CLASSES_ROOT\*\shell\ or HKEY_CLASSES_ROOT\Directory\shell\, creating a new command entry, and pointing it to your script or executable. Admin rights are required for these changes.

You might also like

Ready to simplify the hardest parts of IT?

NinjaOne Terms & Conditions

By clicking the “I Accept” button below, you indicate your acceptance of the following legal terms as well as our Terms of Use:

  • Ownership Rights: NinjaOne owns and will continue to own all right, title, and interest in and to the script (including the copyright). NinjaOne is giving you a limited license to use the script in accordance with these legal terms.
  • Use Limitation: You may only use the script for your legitimate personal or internal business purposes, and you may not share the script with another party.
  • Republication Prohibition: Under no circumstances are you permitted to re-publish the script in any script library belonging to or under the control of any other software provider.
  • Warranty Disclaimer: The script is provided “as is” and “as available”, without warranty of any kind. NinjaOne makes no promise or guarantee that the script will be free from defects or that it will meet your specific needs or expectations.
  • Assumption of Risk: Your use of the script is at your own risk. You acknowledge that there are certain inherent risks in using the script, and you understand and assume each of those risks.
  • Waiver and Release: You will not hold NinjaOne responsible for any adverse or unintended consequences resulting from your use of the script, and you waive any legal or equitable rights or remedies you may have against NinjaOne relating to your use of the script.
  • EULA: If you are a NinjaOne customer, your use of the script is subject to the End User License Agreement applicable to you (EULA).