I love to use Windows Store Apps in Windows 11/10. The reason? Simplicity and smartness! But it does happen that sometimes 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 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 first 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 with 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.
The Remote Procedure Call Failed for Windows Store apps
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_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppContainer\Storage
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 the 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:\Windows\System32 assuming C: is the system root drive.
5. Finally, run the following command using administrative Command Prompt:
SetACL -on "hkcu\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppContainer\Storage\winstore_cw5n1h2txyewy" -ot reg -actn ace -ace "n: S-1-15-2-2608634532-1453884237-1118350049-1925931850-670756941-1603938316-3764965493;p:full;i:so,sc;m:grant;w:dacl"
That’s it! Restart the machine to see the effects.
How to fix The remote procedure call failed in SQL Server Configuration Manager?
If you receive The remote procedure call failed error in SQL Server Configuration Manager window, then open the Services window, look for the SQL Server Agent service, and start it. Access the Properties of this service and set its Startup type to Automatic. Also, if you have installed multiple versions of SQL Server, then make sure you are running the latest version of it. Search for SQLServerManager in the SysWOW64 folder and run the latest version from the list.
How do you fix The remote procedure call failed and did not execute?
When users try to update their computer, open File Explorer, Documents, etc., sometimes they receive The remote procedure call failed and did not execute error. To fix this issue, open the Services window, find Remote Procedure Call (RPC) service from the list, and start it (if not already). Now open its Properties and set the Startup type for this service to Automatic. Also, set the Startup type of the Remote Procedure Call (RPC) Locator service to Manual, and restart your PC.
Check these related posts if you receive:
