System File Checker, or SFC, is one of the best features of Windows; it is also one of the least used. And that’s too bad. Many computer problems can be easily solved by running it, yet very few people use it. To be honest, we often forget about it too. It just so happens that this week we had a problem with one of our computers, used SFC to repair some system files that had been altered during one of our infamous experiments. Yes, we do things like that sometimes…
The System File Checker is used to scan for missing, altered or corrupted system files and to extract the original (correct) file and replace or repair damaged files. You will find SFC on Windows XP, Windows Vista, and Windows 7
Probably one of the reasons why SFC isn’t more widely used is because it’s not a simple point-and-click program. It requires users to run it from a DOS-like window and enter commands and use command-line switches. But before you decide to skip this tip – with all this talk of DOS boxes and commands and switches – don’t skip this tip. Most of you could benefit from this tip, and with just a little patience, all of you could learn to run it. So, hunker down, and we’ll make it as simple as possible.
There are only slight differences in these instructions for different versions of Windows. In Windows XP you can run this without opening the Command window with administrator rights, while Vista and Windows 7 users will need to open the Command window as an administrator. While you may be the only person who ever uses your computer, on Vista and Windows 7, you’re not, by default, an Administrator. Somewhere in Microsoft’s big brain, they’ve decided Windows is safer if users aren’t administrators by default. This must have occurred to them after Windows XP came out. But that’s a discussion for another day.
Before you start to run System File Checker, make sure you have your Windows installation disk inserted in your CD/DVD drive. If you want to repair or replace missing, altered or damaged files, that’s where Windows is going to get them. If you’re one of those who doesn’t have a Windows installation CD, the restore (or “recovery”) disk that came with your computer should work for you.
Plan on at least 45 minutes to run System File Checker. It may not take it that long but sometimes it can even take longer. Whether or not SFC tells you to, you should reboot after you’ve run System File Checker, especially if it has repaired or replaced any files.
OK. To run System File Checker (hereinafter known as SFC because I’m tired of typing System File Checker) do this:
Windows XP users – Press the Windows Key + the “R” key. In the Run command line type CMD and press enter.
Windows Vista and Windows 7 users: Click Start, All Programs, System Tools, Accessories, and right-click on “Command Prompt” and select “Run as administrator”. This is important. If you don’t do this, you won’t be able to do any of the following.
OK. Now that you’re all sitting there with a big black box on your screen (we hope), you need to type in some commands. DOS stuff is not very forgiving, so you have to type these commands exactly – and spaces are important too.
To run SFC so that it scans and replaces/repairs altered, missing, or damaged Windows System Files, type the following at the cursor:
(Note: there is a space between SFC and the backslash, see it? Good. Don’t forget that space!)
Here are some other commands and switches you can use with SFC:
The SFC /VERIFYONLY command scans the integrity of all protected system files but doesn’t repair or replace any damaged, missing, or altered files.
The SFC /SCANFILE command allows you to check the integrity of a single file. For instance:
There are other SFC commands and switches you can use, but for us and most of you, the only command you’ll need to use is:
So there you go. Try System File Checker to check the integrity of your Windows system files. It works well and can fix some of those common, nagging Windows errors.