Remote Procedure Call Failed: Fixes That Work

The “Remote Procedure Call failed” error means Windows could not reach a service it needed, and the fix is usually to restart the RPC service, check the RPC Endpoint Mapper, or repair a corrupted system file. This article explains why the error happens and gives step-by-step fixes you can try in order, from the simplest to the most advanced.

What Is the Remote Procedure Call (RPC)?

RPC is a Windows mechanism that lets one program ask another program to run a function, even if the two are on different computers. For example, when you open a shared folder on a network, your PC sends an RPC to the server to list the files. The server runs the request and sends back the result. This all happens quietly in the background, and you usually never see it.

The error “Remote Procedure Call failed” appears when the client can’t get a response from the server. It can show up in many places: when opening Device Manager, when using Windows Update, when printing, or when starting certain apps. The wording may vary slightly, but the cause is almost always the same: a required Windows service is stopped, disabled, or not responding.

Why Does the Error Happen?

There are several common triggers, and knowing which one you have helps you pick the right fix.

• RPC service is stopped or disabled. The main service is called “Remote Procedure Call (RPC)” and it must be running at all times. If it’s disabled, nearly everything breaks.
• Related services are stopped. The RPC Endpoint Mapper, DCOM Server Process Launcher, and RPC Locator all work with RPC. If any of these are off, RPC calls fail.
• Corrupted system files. A damaged DLL or system file can make RPC fail even when the services are running.
• Malware or a recent update. Some malware turns off RPC to hide itself. A bad Windows update can also break the service.
• Network or firewall issues. If you’re getting the error only when accessing a remote computer, the problem may be in the network path, not on your PC.

Fix 1: Restart the RPC Services

This is the first thing to try. It fixes the error in many cases, especially if the services are running but stuck.

1. Press Windows + R, type services.msc, and press Enter.
2. Scroll down to Remote Procedure Call (RPC). Right-click it and select Restart.
3. Do the same for Remote Procedure Call (RPC) Locator and DCOM Server Process Launcher.
4. Close the Services window and try the action that gave the error.

If the services are not running, right-click each one and choose Start. If the Start option is grayed out, the service is disabled; see Fix 2.

Fix 2: Set RPC Services to Automatic

Sometimes the services are set to “Manual” or “Disabled,” which causes the error. You want them set to Automatic (or at least Automatic (Delayed Start) for the main RPC service).

1. Open services.msc again.
2. Double-click Remote Procedure Call (RPC).
3. In the “Startup type” dropdown, choose Automatic (or Automatic (Delayed Start)).
4. Click Apply, then OK.
5. Repeat for RPC Endpoint Mapper and DCOM Server Process Launcher.

Note: The main RPC service is a protected system service. You can’t change its startup type from “Automatic” in normal safe mode, but you can in the registry if needed. Most users don’t need to go that far.

Fix 3: Run System File Checker and DISM

If the services are fine but the error persists, corrupted system files are the likely culprit. Windows has built-in tools to repair them.

1. Open Command Prompt as administrator (search for “cmd”, right-click, choose “Run as administrator”).
2. Type sfc /scannow and press Enter. Wait for it to finish (it can take 15–30 minutes).
3. If SFC finds errors but can’t fix them, run DISM /Online /Cleanup-Image /RestoreHealth and press Enter.
4. Restart your PC and try again.

These tools check the integrity of Windows system files and replace any that are corrupted. They don’t touch your personal files.

Fix 4: Check for Malware

Some malware specifically disables RPC to prevent security software from running. If you’ve tried the above and the error keeps coming back, run a full antivirus scan. Windows Defender (built-in) is sufficient for most cases.

1. Open Windows Security (search for it in the Start menu).
2. Go to Virus & threat protection.
3. Click Scan options and choose Full scan.
4. Click Scan now and wait for it to finish.

If the scan finds anything, remove it and restart. Then try the action that failed.

Fix 5: Repair Network or Firewall Issues

If the error only happens when accessing a network resource (a shared folder, a printer, or a remote app), the problem might be network-related.

• Make sure the remote computer is on and reachable (try pinging it).
• Check that the Windows Firewall on both computers allows “File and Printer Sharing” and “Remote Volume Management.”
• If you’re on a domain, the group policy might block RPC; contact your IT admin.
• Try disabling the firewall temporarily (only for testing) to see if it’s the cause. If it is, re-enable it and add the proper exceptions.

For a quick test, you can also try net start rpc in an elevated command prompt to manually start the RPC service.

Fix 6: System Restore or In-place Upgrade

If nothing else works, you can roll back to a point before the error started, or repair Windows without losing your files.

• System Restore: Type “restore” in the Start menu, open “Create a restore point,” click “System Restore,” and pick a restore point from before the problem began.
• In-place upgrade: Download the Windows Media Creation Tool, run it, and choose “Upgrade this PC now.” This reinstalls Windows while keeping your files and apps.

These are more drastic, but they fix stubborn corruption that SFC and DISM can’t.

Frequently Asked Questions

What does “Remote Procedure Call failed” mean?

It means a program tried to use Windows RPC to communicate with another program or service, but the call didn’t get a response. The most common cause is that the RPC service or a related service is stopped, disabled, or corrupted.

Can I fix this without reinstalling Windows?

Yes, in most cases. Restarting the RPC services, setting them to Automatic, and running SFC/DISM fixes the error. Reinstalling Windows is only needed if those steps fail and you can’t use System Restore or an in-place upgrade.

Why does the error appear when I open Device Manager?

Device Manager uses RPC to query hardware information. If the RPC service is not running, Device Manager can’t get that data and shows the error. Restarting the RPC service usually fixes it.

Is the RPC error a sign of a virus?

Not always, but it can be. Some malware disables RPC to prevent security tools from running. If the error persists after fixing services and files, run a full antivirus scan.

Will restarting my PC fix it?

Sometimes. A reboot restarts all services, so if a service was stuck, it might come back normally. But if the service is disabled or files are corrupted, the error will return after the reboot.

Can I disable RPC to stop the error?

No. Windows relies on RPC for many core functions, including printing, networking, and the user interface. Disabling it will cause far more problems. The correct fix is to make sure it’s running and healthy.

Related

• Diskpart Create FAT32 Partition: Full Guide
• System and Compressed Memory High Disk Usage Fix
• Canon EOS R6 II Autofocus Settings for Sports, Wildlife & Portraits