Fix Remote Procedure Call Failed Error in Windows

The “Remote Procedure Call failed” error in Windows typically appears when a program tries to use a service that depends on the RPC (Remote Procedure Call) infrastructure, and that service is stopped, disabled, or blocked. The fix usually involves restarting the RPC services, checking the RPC Endpoint Mapper, or repairing system files, and this article walks through the most effective solutions step by step.

What Is the Remote Procedure Call (RPC) Error?

Remote Procedure Call is a Windows mechanism that lets one program request a service from another program running on the same computer or on a different machine over a network. Many core Windows functions—like printing, file sharing, Windows Update, and even the Start menu—depend on RPC working correctly. When the RPC subsystem fails, you might see messages like:

“Remote Procedure Call failed”
“The RPC server is unavailable”
“RPC service terminated unexpectedly”

The error often appears when launching a specific application, during system startup, or when trying to use a network feature. It can be caused by a misconfigured service, a corrupted system file, a recent update, or even malware that has disabled critical services.

Why Does the RPC Error Occur?

The RPC infrastructure relies on several Windows services working together. The most important are:

Remote Procedure Call (RPC) – the main service that manages RPC calls.
RPC Endpoint Mapper – helps clients find the correct endpoint for a service.
DCOM Server Process Launcher – starts components that use DCOM (Distributed Component Object Model), which depends on RPC.

If any of these services is stopped, disabled, or set to start manually when it should be automatic, programs that rely on RPC will fail. The error can also occur if the service is running but the system is unable to communicate with it due to a corrupted registry, a damaged system file, or a third-party security program that blocks RPC ports (typically TCP 135 and dynamic ports).

How to Fix the RPC Error: Step-by-Step Solutions

Start with the simplest fix and work your way down. Most RPC errors are resolved by restarting the RPC services or adjusting their startup type.

Restart the RPC Services
Press Win + R, type services.msc, and press Enter. In the Services window, locate Remote Procedure Call (RPC). Right-click it and select Restart. Do the same for RPC Endpoint Mapper and DCOM Server Process Launcher. If any of these services is not running, right-click and select Start.
Set RPC Services to Automatic
Right-click each of the three services, select Properties, and in the General tab set Startup type to Automatic. Click Apply and OK. If the service is already set to Automatic but still fails, try setting it to Automatic (Delayed Start) to avoid conflicts during boot.
Run System File Checker (SFC)
Open Command Prompt as Administrator (search for “cmd”, right-click, and select “Run as administrator”). Type sfc /scannow and press Enter. This scans and repairs corrupted system files. Wait for the scan to complete—it can take 10–15 minutes. If it finds issues, restart your PC and try again.
Check for Malware
Some malware disables RPC services to prevent security tools from running. Run a full scan with Windows Defender (or your trusted antivirus) and remove any threats. After cleaning, restart the services as in step 1.
Perform a Clean Boot
If the error appears only when a specific program is running, a clean boot can help identify a conflicting service. Type msconfig in the Run dialog, go to the Services tab, check Hide all Microsoft services, then click Disable all. In the Startup tab, open Task Manager and disable all startup items. Restart and see if the error is gone. If it is, enable services one by one to find the culprit.
Run DISM (Deployment Imaging Service and Management Tool)
If SFC doesn’t fix the issue, run DISM. In the same Administrator Command Prompt, type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This repairs the Windows system image. After it finishes, restart and run SFC again.

What to Do If the Error Persists

If the basic fixes don’t work, the problem might be more specific. Try these additional steps:

Check the Registry for RPC settings – Open Regedit (Win + R, type regedit). Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RpcSs and verify the Start value is set to 2 (Automatic). Do the same for RpcEptMapper (Start = 2) and DcomLaunch (Start = 2). If you’re not confident editing the registry, back it up first.
Update Windows – Go to Settings > Update & Security > Windows Update and check for updates. Microsoft often fixes RPC-related bugs in cumulative updates.
Restore the System – If the error started recently, use System Restore (type rstrui in Run) to roll back to a point before the problem began.
Repair Install Windows – As a last resort, you can perform an in-place upgrade using the Windows Media Creation Tool. This reinstalls Windows while keeping your files and apps. It’s a longer process but often resolves stubborn system issues.

Common Misconceptions About the RPC Error

One common myth is that the RPC error always means your computer is infected with malware. While malware can cause it, the error is more often due to a service being stopped after a system update or a misconfiguration in the Services panel. Another misconception is that you need to reinstall Windows to fix it—most of the time, the steps above will resolve the issue without a full reinstall.

Also, some users believe that disabling the RPC service improves security. That is not true—RPC is essential for Windows to function, and disabling it will break many core features. You should never disable RPC services; instead, ensure they are set to Automatic.

Frequently Asked Questions

What does “RPC server is unavailable” mean?

It means the client program cannot reach the RPC service on the target computer. This can happen if the service is stopped, the computer is offline, or a firewall is blocking the RPC ports (TCP 135 and dynamic ports). Check that the RPC service is running and that your firewall allows RPC traffic for trusted networks.

Can I fix the RPC error without admin rights?

Most fixes require administrator privileges because you need to change service settings or run system file checks. If you don’t have admin rights, contact your system administrator. On a personal computer, you can usually use an account with admin rights.

Why does the RPC error appear when I start a specific game or app?

Some applications, especially older ones, depend on RPC for licensing or network features. If the app’s service is not running, or if the app is not compatible with your Windows version, you’ll see the error. Try running the app as administrator, or check for a compatibility mode (right-click the exe, Properties > Compatibility).

Will the RPC error damage my files?

No, the error itself doesn’t damage files. It just prevents certain operations from completing. However, if a program fails while writing data, you could lose unsaved work. Save your work regularly, and fix the error as soon as possible.

How long does it take to fix the RPC error?

Most simple fixes (restarting services) take under 5 minutes. Running SFC or DISM can take 15–30 minutes. A repair install might take an hour or more. The time depends on the cause and the speed of your computer.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →