• Welcome to Tux Reports: Where Penguins Fly. We hope you find the topics varied, interesting, and worthy of your time. Please become a member and join in the discussions.

system file check

J

Jan Philips

Flightless Bird
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
 
E

EN59CVH

Flightless Bird
No you need to create a slipstreamed version of Windows XP disk to get
the right CD for the purpose. I suggest read this article:

<http://www.theeldergeek.com/slipstreamed_xpsp3_cd_final.htm>

hth


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
 
J

Jan Philips

Flightless Bird
On Sun, 07 Mar 2010 01:13:24 +0000, EN59CVH
<EN59CVH@discussions.microsoft.com> wrote:

>No you need to create a slipstreamed version of Windows XP disk to get
>the right CD for the purpose. I suggest read this article:
>
><http://www.theeldergeek.com/slipstreamed_xpsp3_cd_final.htm>

OK, and I've done all of the updates too.
--
Replace you know what by j to email
 
A

Andrew E.

Flightless Bird
SFC doesnt check the files of a service pack,its checking the OS files that
are not in any SP.To run SFC,simply install a retail version of XP,exit the
menu page,SFC runs auto...If youre having problems,then the installation
directory might be at fault,xp has it as D:,the cdrom with xp cd in it must
match,or be changed in regedit...

"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
> .
>
 
B

Bruce Chambers

Flightless Bird
Andrew E. wrote:
> SFC doesnt check the files of a service pack,its checking the OS files that
> are not in any SP.To run SFC,simply install a retail version of XP,exit the
> menu page,SFC runs auto...If youre having problems,then the installation
> directory might be at fault,xp has it as D:,the cdrom with xp cd in it must
> match,or be changed in regedit...
>

Must you always deliberately post the incorrect information?

--

Bruce Chambers

Help us help you:
http://www.catb.org/~esr/faqs/smart-questions.html

http://support.microsoft.com/default.aspx/kb/555375

They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. ~Benjamin Franklin

Many people would rather die than think; in fact, most do. ~Bertrand Russell

The philosopher has never killed any priests, whereas the priest has
killed a great many philosophers.
~ Denis Diderot
 
D

Daave

Flightless Bird
Bruce Chambers wrote:
> Andrew E. wrote:
>> SFC doesnt check the files of a service pack,its checking the OS
>> files that are not in any SP.To run SFC,simply install a retail
>> version of XP,exit the menu page,SFC runs auto...If youre having
>> problems,then the installation directory might be at fault,xp has
>> it as D:,the cdrom with xp cd in it must match,or be changed in
>> regedit...
>
> Must you always deliberately post the incorrect information?

Yes, it's in his contract. ;-)
 
P

Peter Foldes

Flightless Bird
When does the contract finally end ?

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Daave" <daave@example.com> wrote in message
news:-OGoyAGkvKHA.5940@TK2MSFTNGP02.phx.gbl...
> Bruce Chambers wrote:
>> Andrew E. wrote:
>>> SFC doesnt check the files of a service pack,its checking the OS
>>> files that are not in any SP.To run SFC,simply install a retail
>>> version of XP,exit the menu page,SFC runs auto...If youre having
>>> problems,then the installation directory might be at fault,xp has
>>> it as D:,the cdrom with xp cd in it must match,or be changed in
>>> regedit...
>>
>> Must you always deliberately post the incorrect information?
>
> Yes, it's in his contract. ;-)
>
 
J

Jose

Flightless Bird
On Mar 6, 8:03 pm, Jan Philips <youknowwhat.mccra...@comcast.net>
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.
 
P

Peter Foldes

Flightless Bird
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" <jose_ease@yahoo.com> wrote in message
news:38250427-9eff-4b7b-b9cc-0e89aeb44da0@g19g2000yqe.googlegroups.com...
On Mar 6, 8:03 pm, Jan Philips <youknowwhat.mccra...@comcast.net>
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.
 
K

Ken Blake, MVP

Flightless Bird
On Sun, 7 Mar 2010 17:29:00 -0500, "Peter Foldes" <okf22@hotmail.com>
wrote:

> When does the contract finally end ?



Alas, Andrew E's regular posting of misinformation is very likely not
done deliberately. It's mostly just that he knows next to nothing, and
posts misinformation that he thinks is correct.



> "Daave" <daave@example.com> wrote in message
> news:-OGoyAGkvKHA.5940@TK2MSFTNGP02.phx.gbl...
> > Bruce Chambers wrote:
> >> Andrew E. wrote:
> >>> SFC doesnt check the files of a service pack,its checking the OS
> >>> files that are not in any SP.To run SFC,simply install a retail
> >>> version of XP,exit the menu page,SFC runs auto...If youre having
> >>> problems,then the installation directory might be at fault,xp has
> >>> it as D:,the cdrom with xp cd in it must match,or be changed in
> >>> regedit...
> >>
> >> Must you always deliberately post the incorrect information?
> >
> > Yes, it's in his contract. ;-)
> >

--
Ken Blake, Microsoft MVP (Windows Desktop Experience) since 2003
Please Reply to the Newsgroup
 
Y

ybS2okj

Flightless Bird
"Ken Blake, MVP" <kblake@this.is.an.invalid.domain> wrote in message
news:snm8p59la4qnkiva6q4nqn6i74i8fo2lds@4ax.com...

> Alas, Andrew E's regular posting of misinformation is very likely not
> done deliberately. It's mostly just that he knows next to nothing, and
> posts misinformation that he thinks is correct.

So you can see all this from a distance! Is it because of your experience
of misinformation, lies and rubbish over the years? Did you not want to get
a proper training so that you can be an asset to the society in which you
live?

Senility must be affecting you in your advanced age!
 
D

Daave

Flightless Bird
I fear it's open-ended. :-(

Peter Foldes wrote:
> When does the contract finally end ?
>
>
> "Daave" <daave@example.com> wrote in message
> news:-OGoyAGkvKHA.5940@TK2MSFTNGP02.phx.gbl...
>> Bruce Chambers wrote:
>>> Andrew E. wrote:
>>>> SFC doesnt check the files of a service pack,its checking the OS
>>>> files that are not in any SP.To run SFC,simply install a retail
>>>> version of XP,exit the menu page,SFC runs auto...If youre having
>>>> problems,then the installation directory might be at fault,xp has
>>>> it as D:,the cdrom with xp cd in it must match,or be changed in
>>>> regedit...
>>>
>>> Must you always deliberately post the incorrect information?
>>
>> Yes, it's in his contract. ;-)
 
J

Jose

Flightless Bird
On Mar 7, 8:03 pm, "Peter Foldes" <ok...@hotmail.com> wrote:
> 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" <jose_e...@yahoo.com> wrote in message
>
> news:38250427-9eff-4b7b-b9cc-0e89aeb44da0@g19g2000yqe.googlegroups.com...
> On Mar 6, 8:03 pm, Jan Philips <youknowwhat.mccra...@comcast.net>
> 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.

Typo! Should be to run the system file checker, in the Start, Run
box enter:

sfc /scannow
 
R

Railhound

Flightless Bird
I agree with your point but what has happened to me is my anti virus software
F-Secure has damaged some files. In fact, I would suggest that a good many
things that are report here and in other palces are due to anti-virsus
software erroneously deleting certian files.

Anyway, I would like to run the SFC program but my Windoiws version is an
OEM version so I don't have the original CDs only a recovery copy so I can't
make a slipstrem version of SP3 (at least not that I know of).

Any suggestions to get the correct files for SFC to repair them?

"Jose" wrote:

> On Mar 6, 8:03 pm, Jan Philips <youknowwhat.mccra...@comcast.net>
> 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.
>
> .
>
 
J

Jose

Flightless Bird
On Jun 4, 2:36 pm, Railhound <Railho...@discussions.microsoft.com>
wrote:
> I agree with your point but what has happened to me is my anti virus software
>  F-Secure has damaged some files. In fact, I would suggest that a good many
> things that are report here and in other palces are due to anti-virsus
> software erroneously deleting certian files.
>
> Anyway, I would like to run the SFC program but my Windoiws version is an
> OEM version so I don't have the original CDs only a recovery copy so I can't
> make a slipstrem version of SP3 (at least not that I know of).
>
> Any suggestions to get the correct files for SFC to repair them?
>
>
>
> "Jose" wrote:
> > On Mar 6, 8:03 pm, Jan Philips <youknowwhat.mccra...@comcast.net>
> > 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.
>
> > .

Some AV softwares seem to quarantine/delete XP files. I will just say
it must be by mistake...

So far, when I have encountered those situations I have always been
able to fix it and not using sfc /scannow (which should never find
anything to do if your system is not otherwise afflicted). Usually
the system will not even boot afterwards so that makes these things
even more fun!

If your installed SP does not match your installation CD or you only
have some system recovery CD, you are likely to get quickly frustrated
with sfc /scannow. Even if it "works" I have never seen it resolve
any XP problem, but it feels good when it runs successfully.

It is also frustrating to see it suggested as something "to try" when
the necessary parts and pieces to get it to run are not included in
the suggestion as a requirement for it do behave. This results in
more Q&A back and forth and the problem continues to fester.

What is the nature of your system affliction that you think sfc /
scannow will remedy?
 
You must log in or register to reply here.
Top