Jose
It should read sfc /scannow not sfc /scnnow
--
Peter
Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.
"Jose" wrote in message
news:38250427-9eff-4b7b-b9cc-0e89aeb44da0@g19g2000yqe.googlegroups.com...
On Mar 6, 8:03 pm, Jan Philips
wrote:
> I tried to run a system file check. It said to insert the XP SP3
> disc. My computer came with something older (I don't remember which
> SP, but it was about 2-1/2 years ago). Is there a way to run a SFC
> without the SP3 disc?
> --
> Replace you know what by j to email
Sure, you can run it the system file checker.
Click Start, Run and in the box enter:
sfc /scnnow
Unless your system has been compromised by malicious software or the
built in Windows File Protection function is broken SFC should find
nothing to do. It will give you a good feeling if it runs without
finding anything. If it finds something to do, you have now or have
had some other problem.
If you have SP3 installed and only posses an SP1 or SP2 installation
CD, running sfc /scannow will complain - a lot. The messages may not
be errors, but just informational messages. It will check 3498 files
that Windows considers important.
This is because it is trying to match and compare files and the
installed SP does not match up with what is on the installation CD.
You can read about why and perhaps make an adjustment to get it to
work by reading this article. It depends on your system:
http://www.updatexp.com/scannow-sfc.html
To prevent this, you can use your old XP installation CD to make a new
installation CD with SP3 included (slipstream) and then run sfc /
scannow using the up to date CD as a reference. This slipstreamed CD
is a good thing to have anyway in case you need to fix something some
other day.
Thinking that running sfc /scannow will work right out of the chute is
an expectation that generally exceeds reality unless you are prepared
in advance with an installation CD that matches your currently
installed service pack (usually you have to make such a CD).
It most certainly should run without a hitch when all the pieces are
in place and result in a warm fuzzy feeling, but I have personally
never seen it resolve any problem that was not caused by something
else and will never even recommend it, but that could just be me.
When it comes to shoot in the dark troubleshooting, the advice to "run
sfc /scannow" is rarely preceded by the "before you run sfc /
scannow..." advice which generates more confusion, concern and
questions shortly afterwards.
Please do try it though and see how you get on. It won't hurt
anything and you should want it to work. If it doesn't work, we can
try to make it work to make you feel better. It makes me feel better
to see it find nothing to do and not complain.
When sfc /scannow runs successfully, you will see a starting and
complete message in the Event Log. It can take a long time to run and
slow your system down - a lot. When it starts and stops succesfully
you will see events like this in the Event log:
Event Type: Information
Event Source: Windows File Protection
Event Category: None
Event ID: 64016
Windows File Protection file scan was started.
Event Type: Information
Event Source: Windows File Protection
Event Category: None
Event ID: 64017
Windows File Protection file scan completed successfully.
Note that sfc /scannow will not run in Safe Mode (try it) and will
generate this error if you do try it:
Windows File Protection could not initiate a scan of protected system
files.
The specific error code is 0x000006ba [The RPC server is
unavailable.].
You cannot start the RPC Server in Safe Mode either.
If you are having some particular issue of suspicious files, describe
what the issue is and we can help with that.
