The sfc scannow choice is one of the few explicit switches accessible in the sfc order, the Command Prompt direction used to run System File Checker.

While there are a lot of various things you can do with the direction, sfc/scannow is the most widely recognized way that the sfc order is utilized.

Sfc/scannow will investigate the majority of the significant Windows files on your PC, including Windows DLL files. On the off chance that System File Checker finds an issue with any of these ensured files, it will supplant it.

Pursue these means for utilizing sfc with the scannow alternative to fix significant Windows files:

1 Open Command Prompt as an executive, frequently alluded to as a “raised” Command Prompt. For the sfc/scannow direction to work appropriately, it must be executed from a raised Command Prompt window in Windows 10, Windows 8, Windows 7 and Windows Vista. This isn’t required in past forms of Windows.

2 Once Command Prompt is open, type the accompanying direction and after that press Enter.

There’s a space among sfc and/scannow. Executing the sfc direction with its choice alongside it (without a space) may result in a mistake. In case you’re attempting to utilize System File Checker from the Command Prompt accessible from Advanced Startup Options or System Recovery Options, see the Executing SFC/SCANNOW From Outside of Windows area beneath for some vital changes by they way you execute the order.

System File Checker will presently confirm the trustworthiness of each ensured working system file on your computer. It may take a long time to wrap up.

When the confirmation achieves 100%, you’ll see something like this in the Command Prompt window, accepting issues were found and revised.

Windows Resource Protection found degenerate files and effectively fixed them. Subtleties are incorporated into the CBS.Log windir\Logs\CBS\CBS.log. For instance C:\Windows\Logs\CBS\CBS.log. Note that logging is as of now not bolstered in disconnected overhauling situations.

Windows Resource Protection did not discover any uprightness infringement.

In certain circumstances, regularly in Windows XP and Windows 2000, you may likewise require access to your unique Windows establishment CD or DVD eventually amid this procedure.

3 Restart your computer if sfc/scannow did really fix any files. System File Checker could possibly incite you to restart however regardless of whether it doesn’t, you ought to restart at any rate.

4 Repeat whatever procedure made your unique issue check whether sfc/scannow redressed the issue.

Each time you run System File Checker, a LOG file is made that contains an ordered rundown of each file that was checked and each fix task that occurred, assuming any.

Expecting Windows is introduced on the C: drive (it typically is) at that point the log file can be found at C:\Windows\Logs\CBS\CBS.log and opened with Notepad or some other content tool. This file could be valuable for cutting edge investigating or as a resource for a technical support individual that may enable you to out.

See Microsoft’s How to Analyze the Log File Entries Created by SFC article in case you’re keen on jumping into this file yourself.

Executing SFC/SCANNOW From Outside of Windows

When running sfc/scannow from outside of Windows, as from the Command Prompt accessible when you boot from your Windows establishment plate or blaze drive, or from your System Repair Disk or Recovery Drive, you’ll need to tell the sfc order precisely where Windows exists.

Here’s a model:


The/offbootdir= choice determines the drive letter, while the/offwindir= choice indicates the Windows way, again including the drive letter.