WinXP SP2 problems

[Mungos]

have famous problems with help & support which cant start,and when from cmd, try sfc /scannow getting error

'Windows File Protection could not initiate a scan of protected system files
The specific error code is 0x000006ba. The RPC Server is unavailable'

i try an repair (not fresh install),but with no success
i try microsoft article
http://support.microsoft.com/default.aspx?scid=kb;EN-US;296241
but with no success


can anyone can help to solve problem?

[classicsoftware]

This begs the question, why were you trying to get help & support? Have you tried in safe mode? Were you experiencing any problems that lead you to try to run help & support? Install any new software lately? Install any new hardware lately?

[Bassmaster]

Probably a dumb answer but I just got XP a couple weeks ago and am very unfamiliar with it...Wouldn't System Restore fix the problem?

[classicsoftware]

Probably a dumb answer but I just got XP a couple weeks ago and am very unfamiliar with it...Wouldn't System Restore fix the problem?

Maybe, if it is hardware related no. If it's software related, yes.

[Bassmaster]

I was thinking it was a software problem. I didn't know a hardware problem would cause this type of error. :eek:

Thanks for the info. :)

[Mungos]

in safe mode or not,help dont work even sfc
i dont use system restore :)
maybe i installed some application cant remember which
i think registry is broken...

[jcnoernberg]

if you goto run>services.msc, what does it say under Remote Procedure Call? Can you start it from there if it is not running?

[Mungos]

nothing wrong with RPC.it is started
help & support service is not started even automatic

have new problem
when use netdiag tool from cmd
getting message

Failed to get information for a network adapter.The error occurred was:'' the pipe is being closed.''
(232) [Fatal] cannot find TCP/IP configuration from the registry.

is this ok for pc without network,only have dial-up...

[FastLearner]

DLS, Cable, or Dialup: In any case, you will need to have a healthy TCP/IP stack if you want to connect to the Internet.

Go to Start | Run and type in cmd and press OK. At the prompt, type ping localhost and press Enter. this will test your TCP/IP stack. Tell us what happens.

[thedon]

I've been having the exact same problems stemming from what I thought could have been memory problems before crashing my computer.

Since then I've reformatted and reinstalled windows xp pro.
Installed sp1 and 2 and am now having these problems.

I've used winsockxpfix and ispfix

After pinging my local host I received this message:
Pinging broken [127.9.0.0.1] with 32 bytes of data:
Reply from xxxx bytes = 32 time < 1 ms TTL = 128
Reply from xxxx bytes = 32 time < 1 ms TTL = 128
Reply from xxxx bytes = 32 time < 1 ms TTL = 128
Reply from xxxx bytes = 32 time < 1 ms TTL = 128

Ping statistics for 127.0.0.1:
Packets: Sent=4, Received=4, Lost - 0 <0% loss>, Approximate round trip times in milli-seconds: Minimum=0ms, Maximum=0ms, Average=0ms

Thoughts?