The remote procedure call failed when the PIN code was used as a connection option

Only admnistrator owned posts can execute the include me shortcode

A few days ago, we reported the Remote Procedure Call RPC bug for Windows Store applications in Windows 8. As already mentioned, there may be different scenarios if you can get around this error. Today, in this article, we will discuss such a scenario. When we tried to configure the PIN login function in Windows 8.1, we got stuck with this error.

Remote procedure call failed

Only admnistrator owned posts can execute the include me shortcode

RPC failed due to incorrect registry entries. This particular problem can be solved if we started the service RPC in mode Automatic, which is delayed. But the problem is that when we try to change the start type (16) of this service in the Services window (16), the option is grayed out (see screenshot below).

To solve the problem, we must once again rely on the manipulation of registry entries. Here’s how you can fix it:

PIN cannot be set as connection option because RPC failed

1 Press the Windows key + R combination, type Regedt32.exe into the Run dialog box and press Enter to open Registry Editor.

2 Navigate to next location :

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesRpcS

3 Take possession of the key RpcS in the left area and make sure you have full control over this key. Make sure the DWORD with the name Start exists and has a value (16) of 2. Create a new DWORD with the name DelayedAutostart with Right Click -> New -> DWORD Value -> DWORD Value.

4 Finally, double-click on the DWORD thus created and change its value data to 1 :

You can now click the registry editor (16) and restart the computer, the error should now be corrected.

Hope this helps!

See this when you receive the error message The remote procedure call failed when using DISM.

Only admnistrator owned posts can execute the include me shortcode[toggle title=”Related Video”][/toggle]