the RPC server is unavailable on windows 7 stand alone logon

Anonymous

When I try to logon to my windows 7 64bit stand alone machine, I get the error message "the RPC server is unavailable"

It accepts the login - says welcome to windows then the error message waits a while then reboots. It has a fingerprint reader, but gives the same error when using a password. It will not start go any further then this in "safe mode" or "last know good configuration mode" or any other mode.. Did a checkdisk booting from a cd rom. Booting from a CD rom, I can see all of the files..

HP dv9000 4 gig ram

Stand alone - no Domain or homegroup

Windows 7 Ultimate installed since it was released

fingerprint reader installed, but I get the same error using a password

up to date on service packs, MS Defender, AVG (free ver), Malware (free ver), Spybot (free ver)

Hoping to not have to do a re-install

thanks in advance...

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

Another solution is to make sure "DHCP Client" and "RPC Endpoint Mapper" "Remote Procedure Call (RPC) Locator" "Remote Procedure Call (RPC)" are all running and set to automatic.

I hope this helps too.

0 comments

55 additional answers

Anonymous

2013-08-07T05:00:35+00:00

Totally agree, this is disgraceful that "Microsoft" don't take responsibility for this. The amount of time this has costed us all is a joke None of the suggested fixes here worked for me and currently have a Notebook that I cannot log into (other than Safe mode).

This is a Microsoft Forum.....................where are the Microsoft Support people here????? Obviously they know they have stuffed up badly and are hiding away. So bloody annoying.
Was this answer helpful?

0 comments No comments
Anonymous

2013-06-14T18:32:49+00:00

I am disgusted by this. The average user or **** even the above average user is NOT going to be able to fix this! Complete BS. All these years and it still happens?
Was this answer helpful?

0 comments No comments
Anonymous

2013-06-14T18:24:15+00:00

You know what I see here...a complete lack of anger over this stupid issue. It is June 20132 and this just happened to a customers brand new machine with a freshly installed office 365. Complete BS. FIX THE PROBLEM MICROSOFT!
Was this answer helpful?

0 comments No comments
Anonymous

2013-06-11T04:27:48+00:00

Solution #3

So My problem was similar, the computer displayed an RPC error when i was trying to log in. Because of this i could not take advantage any of the general solutions offered on tech sites and boards. But...

After looking around a bit, and poking at the system, i discovered that there was no Registry entry for RPC locator. a little more looking around and i found that the file Locator.exe had been renamed to something like lodctr.exe.

so i used the command prompt to change the file name back to what it is supposed to be.

and it worked!

Here it is in sequence ->

Startup / restart computer

hit F8 during startup to get to windows boot options

Start in repair mode

Open command prompt

Type dir /p to get a listing of all files in the sys32 folder

From here try and locate a file named similar to Locator.exe

Rename <bad file name> Locator.exe

dir /p to make sure the changes took hold

restart.

and there you go

It is worth mentioning that i did try system restore a couple times before i found this fix. It failed with an 'Unexpected error' error each time. I mention this, because when i finally got into the OS, windows informed me that it had completed a System restore attempt.
Was this answer helpful?

0 comments No comments