Windows failed the logon. The remote procedure call failed and did not execute - posted in Windows 7: I have three users on a Windows 7 computer. None will log on, they all give Windows failed the. When I want open 'Explorer' it show me 'The remote procedure call failed and did not execute.' And according to the some helps I found that I must check 'Remote Procedure Call' and 'RPC locator' services.
I can't seem to open any folder using Explorer in Windows 7 RC b7100, as it fails with the above error. This happened after Explorer stopped picking up metadata on files, and so I killed and restarted explorer using Task Manager. Files and folders on my Desktop still show up, and files still open in their respective applications, but folders won't show, as with the error. Happens with any local folder.
I can't find anything on Google. I haven't touched any Explorer settings, and I'm not interested in an Explorer alternative. I can restart, but this has happened once before, so I'm thinking it'll happen again after a restart. Anyone have any more permanent ideas?
I love to use Windows Store Apps in Windows 8. The reason? Simplicity and smartness! But it does happen that some times, when you try some new apps, you may face issues while using them. Today, in this article, we’ll tell you about an error faced by some while using these Windows Store Apps: The Remote Procedure Call Failed.
If you too are facing this issue, you should know that this happens due to an incorrect allocation of registry entries, which could probably have been tweaked by third-party apps. In addition to this, failure of Remote Procedure Call and Remote Procedure Call Locater services may also result in the same error. So you should firstly confirm that these services are functioning properly, by running services.msc, and then proceed with this registry tweak. I am sure that I don’t need to tell you to make a system restore point first, before touching the Windows Registry.
As you can see in the error dialog box, there is nothing to help us on this error; no error code or Help link. So prior to trying out the fix mentioned below, you should give the following a try: Updating / reinstalling /synching apps, disabling all third-party apps, switching to Microsoft account from local account and vice versa, resetting app cache, running Windows Apps Troubleshooter and running the System File Checker command. If nothing helps, follow the solution referenced from Technet forums:
The Remote Procedure Call Failed
1. Press Windows Key + R combination, type put Regedt32.exe in Run dialog box and hit Enter to open the Registry Editor.
2. Navigate to the following location:
HKEY_CURRENT_USERSoftwareClassesLocal SettingsSoftwareMicrosoftWindowsCurrentVersionAppContainerStorage
3. In the left pane of this location, under the key Storage, scroll down and look for winstore_cw5n1h2txyewy subkey. This subkey is mandatory and should remain there, if you don’t find it, create one using right click on Storage key and select New key. Further create two subkeys of winstore_cw5n1h2txyewy using same way and name them Internet Settings and Software. Once you make assured everything exists, move to the next step.
4. Moving on, download the EXE version of SetACL from here. SetACL is an advanced Windows manipulation tool commonly used by IT specialists. The download link will yield it in .zip format which you have to unzip using a decompression software. Place the SetACL.exe file to C:WindowsSystem32 assuming C: is the system root drive.
5. Finally run following command using administrative Command Prompt:
That’s it! Restart the machine to see the effects.
See this post if using DISM in Windows 8.1 gives The remote procedure call failed error.
The Remote Procedure Call Failed Windows 7 Fix
The Remote Procedure Call Failed Windows 7 Login
Related Posts: