SFC /SCANNOW Command - System File Checker

enrell · 09 Jun 2011

niemiro said:

enrell said:

marsmimar said:

Hello enrell and welcome to Seven Forums.

As the information section at the beginning of the tutorial says, "The sfc /scannow command (System File Checker) scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed, or damaged versions with the correct versions if possible." I might be mistaken but I don't believe SFC will check the hardware that might be installed on a given computer. You might have to go to Device Manager. Device Manager can be used for changing hardware configuration options, managing drivers, disabling and enabling hardware, identifying conflicts between hardware devices, etc.

Open Device Manager

hi there

what i meant the errors are graphic drivers..ati and nvidia drivers..but funny thing is i dont have any error when using my gpu..

Hello!

Have you ever used Driver Sweeper? There was a bug in Driver Sweeper which caused this problem. Do you still have it installed? Are these files in the backup directory?

Thanks a lot!

yeah..there were an issue when previous version of the DS accidentally removed ati files which are needed for the SP1. I have since upgraded to the latest version.

mmmm...so if i can find those files, i just copy and paste to the specific directory?

Brink · 09 Jun 2011

Hello Enroll, and welcome to Seven Forums.

Reinstalling or installing the latest ATI/AMD drivers should have replaced and fixed the damaged/missing files. :)

karlsnooks · 28 Jun 2011

Shawn,
Here's a link to a new kb on sfc. Don't know whether you think some of the info should/needs to be integrated into the tutorial.

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

Brink · 28 Jun 2011

Thank you Karl, but the tutorial already covered everything in it and more.

karlsnooks · 28 Jun 2011

Shawn,
I didn't remember seeing the part in the tutorial regarding taking ownership, setting access rights and then replacing the bad file.
karl

Brink · 28 Jun 2011

The yellow TIP box is for that with more details on how at the link in it.

karlsnooks · 28 Jun 2011

Brink said:

The yellow TIP box is for that with more details on how at the link in it.

My error. I overlooked the TIP box. Thanks for point it out.
karl

Brink · 28 Jun 2011

It's no problem Karl. Thank you again. :)

karlsnooks · 29 Jun 2011

Shawn,

What do you think of using DISM to determine the index into the Wim file?

Code:

 USE DISM TO DETERMINE INDEX INTO WIM FILE

   
   
  32 BIT WIN 7

  C:\Windows\system32>dism /get-wiminfo /wimfile:e:\sources\install.wim
   
  Deployment Image Servicing and Management tool
  Version: 6.1.7600.16385
   
  Details for image : e:\sources\install.wim
   
  Index : 1
  Name : Windows 7 STARTER
  Description : Windows 7 STARTER
  Size : 8,072,604,598 bytes
   
  Index : 2
  Name : Windows 7 HOMEBASIC
  Description : Windows 7 HOMEBASIC
  Size : 8,125,226,573 bytes
   
  Index : 3
  Name : Windows 7 HOMEPREMIUM
  Description : Windows 7 HOMEPREMIUM
  Size : 8,566,642,846 bytes
   
  Index : 4
  Name : Windows 7 PROFESSIONAL
  Description : Windows 7 PROFESSIONAL
  Size : 8,447,825,392 bytes
   
  Index : 5
  Name : Windows 7 ULTIMATE
  Description : Windows 7 ULTIMATE
  Size : 8,607,765,255 bytes
   
  The operation completed successfully.
   
   
  64 bit Win 7

   
  C:\Windows\system32>dism /get-wiminfo /wimfile:e:\sources\install.wim
   
  Deployment Image Servicing and Management tool
  Version: 6.1.7600.16385
   
  Details for image : e:\sources\install.wim
   
  Index : 1
  Name : Windows 7 HOMEBASIC
  Description : Windows 7 HOMEBASIC
  Size : 11,710,161,360 bytes
   
  Index : 2
  Name : Windows 7 HOMEPREMIUM
  Description : Windows 7 HOMEPREMIUM
  Size : 12,222,587,449 bytes
   
  Index : 3
  Name : Windows 7 PROFESSIONAL
  Description : Windows 7 PROFESSIONAL
  Size : 12,122,886,417 bytes
   
  Index : 4
  Name : Windows 7 ULTIMATE
  Description : Windows 7 ULTIMATE
  Size : 12,285,492,779 bytes
   
  The operation completed successfully.

Brink · 29 Jun 2011

Karl,

It's another good option. I only used what I had at steps 8-10 here since they already had the WIM opened in 7-Zip ready for extraction.