SFC /SCANNOW Command - System File Checker

How to Repair Windows 7 System Files with System File Checker​

   Information

The sfc /scannow command (System File Checker) scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible.

   Tip

If you get the Windows Resource Protection Could Not Start the Repair Service error when trying to run SFC, then make sure that the Windows Modules Installer service is enabled, click on Start, and set to Manual.

Services - Start or Disable

OR

Copy and paste the command below in the elevated command prompt, and press Enter. After the Windows Modules Installer service has started, try running the SFC command again

net start trustedinstaller

   Note

The KB3022345, KB3035583, and KB3068708 updates will cause SFC to give you a false mismatch message in SFC for files related to these updates.

You can safely ignore these results in your SFC details since it will not affect SFC from being able to repair other system files.

   Warning

Be aware that if you have modified your system files as in theming explorer/system files, running sfc /scannow will revert the system files such as explorer.exe back to it's default state. Make the appropriate backups of your system files that you have modified for theming if you wish to save them before running sfc /scannow.

:note: For the updated Windows 10 tutorial, please see - SFC Command - Run in Windows 10 - Windows 10 Tutorials

CONTENTS:

• Option One: To Run the SFC /SCANNOW Command at Boot
• Option Two: To Run the SFC /SCANNOW Command in Windows 7
• Option Three: How to See and Read Only the "SFC" Scan Results from the CBS.LOG

OPTION ONE

To Run the SFC /SCANNOW Command at Boot

1. For how, see METHOD TWO at this link: SFC /SCANNOW : Run in Command Prompt at Boot

   Note

Using OPTION TWO below is recommended if able.

If you would like to get help with your SFC issue, then be sure to upload and attach your sfcdetails.txt file from OPTION THREE below in your post.

OPTION TWO

To Run the SFC /SCANNOW Command in Windows 7

1. Open an elevated command prompt or an elevated PowerShell, and do step 2 or 3 below for what type of scan you would like to run.


2. To Scan and Repair System Files
NOTE: Scans the integrity of all protected system files and repairs the system files if needed. Please see red WARNING box at the top of this tutorial.
A) In the elevated command prompt, type sfc /scannow, press Enter, and go to step 4 below. (see screenshot below)
NOTE: This may take a little bit to finish.


3. To Only Verify if the System Files are Corrupted
NOTE: Scans and only verifies the integrity of all proteced system files only. This command will not change your system files as in the red WARNING box at the top of this tutorial.
A) In the elevated command prompt, type sfc /verifyonly, press Enter, and go to step 4 below.
4. When the scan is complete, hopefully you will see all is ok like the screenshot below.

   Note

• If SFC could not fix something, then run the command again to see if it may be able to the next time. Sometimes it may take running the sfc /scannow command 3 or more times to completely fix everything that it's able to.
• If not, then download and run the 32-bit (x86) or 64-bit (x64) System Update Readiness Tool for your same installed 32-bit or 64-bit Windows 7, restart the PC afterwards, and try the sfc /scannow command again.
• If still not, then try using OPTION ONE above to run the sfc /scannow command at boot.
• If still not, then you can attempt to run a System Restore using a restore point dated before the bad file occured to fix it. You may need to repeat doing a System Restore until you find a older restore point that may work.
• If still not, then you can use the steps in the TIP box in the OPTION THREE section below to manually replace the files that SFC could not fix if there are not to many fix.
• If there are to many files to manually fix, or you prefer not to use OPTION THREE below, then you could do a repair install without losing anything.

If you would like to get help with your SFC issue, then be sure to upload and attach your sfcdetails.txt file from OPTION THREE below in your post.

5. When done, close the elevated command prompt.

OPTION THREE

How to See and Read Only the "SFC" Scan Results from the CBS.LOG

   Note

When SFC runs, it logs it's actions into the C:\Windows\Logs\CBS\CBS.log. The steps in this option will show you how to see only the specific SFC entries with the [SR] tags in this CBS.log. This can be helpful to show you what files SFC could not fix automatically if you wanted to try and manually replace them.

1. Open an "elevated command prompt" (right click -> Run as administrator).

2. In the elevated command prompt, copy and paste the command below, and press Enter. (See screenshot below)
NOTE: This will place a sfcdetails.txt file on your desktop with only the SFC scan result details from the CBS.LOG in it.

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

3. Close the elevated command prompt.

4. Open the sfcdetails.txt file on your desktop to see the SFC scan details in the CBS.LOG.

5. You can safely delete the sfcdetails.txt file afterwards if you like.

   Tip

If you need to replace a corrupted system file that SFC cannot fix, then this will show you how to by extracting a new copy directly from your Windows 7 installation DVD.

Extract Files from Windows 7 Installation DVD

That's it,
Shawn

Related Tutorials

---

• How to Run the System File Checker in a Command Prompt at Boot
• How to Do a System Restore in Windows 7
• How to Do a Repair Install to Fix Windows 7
• How to Run Disk Check in Windows 7
• How to See Windows 7 Reliability and Problem History with Reliability Monitor
• How to Extract Files from the Windows 7 Installation DVD
• How to Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista

 

[derekimo]

How could I check up, If I have?

Option1.How to See Which Group Policies are Applied to Your PC and User Account
Option2. https://msdn.microsoft.com/en-us/library/bb742376.aspx

I almost miss your post, but thank for get back to my concern, If there is a way to me to found out this policy, could you be available to pint point to me, please?

Normally, you don't have that feature, it is for Pro and above.

There are ways on the internet to enable that feature in the lower versions.

You would know if you enabled it, it would be a deliberate action.

 

[squirtmph]

Thank you very much! have great dinner time \w/

 

[DocPT]

sfc difficulty

hi,

I'm having some PC issues. Tried running SFC as instructed.
See uploaded pic.

I attempted to export to sfcdetails.txt but came up with an empty text file

Thank you!

 

[Brink]

Hello DocPT,

See if running a SFC /SCANNOW command instead may give you results.

 

[DocPT]

ok got this the next time

that was with sfc /scannow

 

[NoelDP]

You have some issues in the background there which need to be dealt with in another way -
Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your reply.

 

[DocPT]

thanks NoelDP

here is the zip file

 

[NoelDP]

Here's the Summary from the log...

Summary:
Seconds executed: 826
 Found 40 errors
 Fixed 20 errors
  CSI Manifest Missing Total count: 9
  Fixed: CSI Manifest Missing.  Total count: 2
  CSI Catalog Missing Total count: 4
  Fixed: CSI Catalog Missing.  Total count: 4
  CSI Payload File Missing Total count: 17
  Fixed: CSI Payload File Missing.  Total count: 7
  CBS MUM Missing Total count: 2
  CBS Catalog Missing Total count: 1
  CSI Store Directory Missing Total count: 7
  Fixed: CSI Store Directory Missing.  Total count: 7

Unavailable repair files:
	winsxs\manifests\amd64_microsoft-windows-d..fontcache.resources_31bf3856ad364e35_7.1.7601.16492_ko-kr_f255f071e2bad917.manifest
	winsxs\manifests\amd64_netfx-cvtresui_dll_b03f5f7f11d50a3a_6.1.7601.22733_none_477b4e67da3fc938.manifest
	winsxs\manifests\x86_microsoft-windows-p..age-codec.resources_31bf3856ad364e35_7.1.7601.16492_nl-nl_5babb207a1b28455.manifest
	winsxs\manifests\amd64_microsoft-windows-u..oyment-languagepack_31bf3856ad364e35_7.1.7601.16492_sl-si_596761acf46f970c.manifest
	winsxs\manifests\amd64_microsoft-windows-d..fontcache.resources_31bf3856ad364e35_7.1.7601.16492_nb-no_dae871a6bae004d3.manifest
	winsxs\manifests\amd64_win7-microsoft-wind..oyment-languagepack_31bf3856ad364e35_7.1.7601.16492_sl-si_55b44dcdf47b38b7.manifest
	winsxs\manifests\amd64_win7-microsoft-wind..oyment-languagepack_31bf3856ad364e35_7.1.7601.16492_sl-si_1c113d91e8b4627d.manifest
	servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Com-WinIP-Package~31bf3856ad364e35~amd64~uk-UA~7.1.7601.16492.mum
	servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Base-WinIP-Package~31bf3856ad364e35~amd64~uk-UA~7.1.7601.16492.mum
	servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-WinIP-Package~31bf3856ad364e35~amd64~uk-UA~7.1.7601.16492.mum
	servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Com-WinIP-Package~31bf3856ad364e35~amd64~uk-UA~7.1.7601.16492.cat
	servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-Base-WinIP-Package~31bf3856ad364e35~amd64~uk-UA~7.1.7601.16492.cat
	servicing\packages\Win8IP-Microsoft-Windows-DownlevelApisets-WinIP-Package~31bf3856ad364e35~amd64~uk-UA~7.1.7601.16492.cat

I'll post a fix protocol for these errors when I can find the time!

 

[NoelDP]

I've uploaded a file - dptaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder dptaa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

And the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

Then run another SFC /SCANNOW and post the new CBS.log file

 

[DocPT]

NoelDP

Thanks for putting that together!

I attached the new logs.

 

[NoelDP]

Bother - I missed one

Unavailable repair files:
	winsxs\manifests\x86_microsoft-windows-p..age-codec.resources_31bf3856ad364e35_7.1.7601.16492_nl-nl_5babb207a1b28455.manifest

There are also the Missing Payload Files...

	Line 28: (f)	CSI Payload File Missing	0x00000000	wuapp.exe	amd64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.6.7601.18847_none_77615b851ea5a5d3	
	Line 29: (f)	CSI Payload File Missing	0x00000000	wuwebv.dll	amd64_microsoft-windows-w..pdateclient-activex_31bf3856ad364e35_7.6.7601.18847_none_77615b851ea5a5d3	
	Line 30: (f)	CSI Payload File Missing	0x00000000	d3d10warp.dll	x86_microsoft-windows-directx-warp10_31bf3856ad364e35_7.1.7601.16492_none_dd831f034017b66d	
	Line 31: (f)	CSI Payload File Missing	0x00000000	AcGenral.dll	amd64_microsoft-windows-a..ence-mitigations-c3_31bf3856ad364e35_6.1.7601.18128_none_6a43510908eecf0e	
	Line 32: (f)	CSI Payload File Missing	0x00000000	AcGenral.dll	x86_microsoft-windows-a..ence-mitigations-c3_31bf3856ad364e35_6.1.7601.18128_none_0e24b58550915dd8	
	Line 37: (f)	CSI Payload File Missing	0x00000000	credssp.dll	x86_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.18540_none_c59b13a6ffee25f4	
	Line 38: (f)	CSI Payload File Missing	0x00000000	TSpkg.dll	x86_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.18540_none_c59b13a6ffee25f4	
	Line 40: (f)	CSI Payload File Missing	0x00000000	rdpcorekmts.dll	amd64_microsoft-windows-t..instationextensions_31bf3856ad364e35_6.1.7601.18540_none_f812b73581c8d921	
	Line 49: (f)	CSI Payload File Missing	0x00000000	rdpcorekmts.dll	amd64_microsoft-windows-t..instationextensions_31bf3856ad364e35_6.1.7601.22750_none_f89185fa9aee9203	
	Line 50: (f)	CSI Payload File Missing	0x00000000	secproc_ssp.dll	x86_microsoft-windows-s..or-native-serverbox_31bf3856ad364e35_6.1.7601.22530_none_72360c96db85775f

....and from the SFC...

2015-11-03 21:00:22, Info                  CSI    0000034d [SR] Repairing 2 components
2015-11-03 21:00:22, Info                  CSI    0000034e [SR] Beginning Verify and Repair transaction
2015-11-03 21:00:22, Info                  CSI    0000034f [SR] Cannot repair member file [l:30{15}]"rdpcorekmts.dll" of Microsoft-Windows-TerminalServices-RDP-WinStationExtensions, Version = 6.1.7601.18540, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
2015-11-03 21:00:22, Info                  CSI    00000350 [SR] Cannot verify component files for Microsoft-Windows-Photo-Image-Codec.Resources, Version = 7.1.7601.16492, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"nl-NL", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)

I'll post fixes for these errors later.

 

[NoelDP]

I've uploaded a file - gptab.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\gptab
hit the enter key - if you get a 'Not Found' error try
DIR D:\gptab
or
DIR E:\gptab

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\gptab <drive>:\windows\winsxs /y /i /s /v /h

(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

 

[DocPT]

new log

 

[Brink]

new log

Hello Doc,

Your new log doesn't have any issues found by SFC.

 

[DocPT]

Great! Thank you so much for all the help!

 

[cynnpai]

So, i should keep re-doing it?

 

[Brink]

Hello cynnpai, and welcome to Seven Forums.

You could use the troubleshooting steps in the blue note box at the bottom of OPTION TWO to see if it may help.

 

[amadeus39]

Thank you !

Info and post still useful almost 7 years later.

 

[bharath17]

i hav attached sfc details ..pls help me fix ths error. thank you

 

[Brink]

Hello bharath17, and welcome to Seven Forums.

It looks like you used a theme or skinning program to modify Windows theme. If so, then you have nothing to worry about since the files in your SFC details below are for that.

• bootres.dll
• glu32.dll
• imageres.dll
• opengl32.dll
• themeservice.dll
• themeui.dll
• uxtheme.dll