RPC Server Is Unavailable (0x800706ba) on Windows 11

The “RPC server is unavailable” (0x800706ba) error on Windows 11 usually appears when your system fails to communicate with another service, device, or process. You might see this error while using Remote Desktop, opening network resources, running services, or even during system updates. This error usually means that your computer is unable to establish a connection between two components that need to communicate. This communication failure can occur due to problems such as network issues, disabled services, firewall blocks, or incorrect system settings.

In this article, you’ll learn what RPC is in Windows, why the “RPC server is unavailable” error happens, and A set of practical fixes you can follow to fix it.

What Is RPC in Windows?

Microsoft describes the Remote Procedure Call (RPC) as a software communication protocol (or model) that allows Windows programs and services to communicate with each other, either on your own PC or over the network.

Some examples where RPC is used:

• When your PC communicates with a network printer
• When you open a shared folder on another computer
• When Windows tools manage remote devices or services

When RPC can’t do its job, Windows shows the error “RPC server is unavailable (0x800706ba)”. This means the program that sent the request could not reach the service it needed.

What Causes “RPC Server Is Unavailable” Error?

This error usually happens when your system fails to communicate with another service or device. Since RPC (Remote Procedure Call) handles communication between processes, any interruption can trigger this error.

• RPC Services Not Running: If the required RPC services are not running, the system cannot process remote procedure calls, resulting in this error.
• Network Connectivity Issues: Poor or interrupted network connections can prevent communication between systems, triggering the error.
• Firewall Blocking RPC Traffic: Firewalls or security software may block the RPC communication, causing the server to appear unavailable.
• DNS Resolution Problems: Incorrect DNS settings or issues with the DNS server can prevent the system from locating the RPC server, resulting in this error.
• Corrupt System Files: Corrupted system files can interfere with the RPC services and lead to errors.

Ensure RPC Services are Running/Restart them

If the main RPC services are stopped, frozen, or not set to start automatically, Windows cannot handle requests between programs or across the network. Restarting these services brings back the communication channel that RPC needs.

RPC services must be running for remote procedure calls to be processed correctly.

• Press Win + R, type services.msc, and press Enter to open the Services window.
• Locate the following services: Remote Procedure Call (RPC), RPC Endpoint Mapper, and DCOM Server Process Launcher.
• Ensure each of these services is running and set to Automatic. To do this, right-click on each service, select Properties, and set the Startup type to Automatic. If the service is not running, click Start.
• If it says Running, click Stop, wait a few seconds, then click Start again.
• Restart your computer and check if the error is resolved.

This step ensures that the critical services needed for RPC communication are active and running correctly.

Check if Windows Firewall blocking RPC server

As discussed before, firewalls or any other security-related applications running on the system can block traffic from RPC requests. If you have a third-party firewall installed, try configuring it to allow incoming and outgoing connections for RPCs and other applications that you intend to use in RPCs.

If you are using Windows Firewall, configure it to allow incoming and outgoing connections for RPCs and other applications by following steps.

• First, open the Control Panel, search for Windows Firewall.
• And then click Allow an app through Windows Firewall below Windows Firewall.

• Click Change settings (you may be asked for admin permission).
• Then scroll down to find Remote Assistance. Ensure its communication is enabled (All the boxes of this item are ticked).
• Similarly, allow Remote Event Log Management, Remote Service Management and Windows Management Instrumentation (WMI)
• Click OK to save changes.

If you also use a third‑party antivirus or firewall, open that program and:

• Look for any rules blocking remote connections, file sharing, or RPC.
• Temporarily disable its firewall feature and test again.

If the error disappears while the third‑party firewall is off, you’ve found the cause. Adjust its settings or consider using only Windows Security.

Enable File and Printer Sharing

Many users see the “RPC server is unavailable” error when trying to access a shared printer or folder. If file and printer sharing is turned off, Windows will block the traffic needed for these connections, and RPC will fail.

1. Open Settings. Go to Network & Internet.
2. Click Wi‑Fi or Ethernet, depending on how you are connected.
3. Click your current network name.
4. Under Network profile type, select Private. This allows sharing within your home or office.
5. Go back to Network & Internet and click Advanced network settings.
6. Click Advanced sharing settings.
7. Under Private network, turn on:
   • Network discovery
   • File and printer sharing

Restart your PC and try connecting to the shared printer or folder again.

Fix DNS and Name Resolution Issues

RPC clients use the server’s hostname (e.g., server01.domain.com) to initiate a connection. 
If DNS returns an incorrect, outdated, or non-existent IP address due to stale or corrupted cache entries, the client cannot locate the server, resulting in the “RPC server unavailable” error.

Right‑click the Start button and choose Windows Terminal (Admin) or Command Prompt (Admin). Now run the following commands and press Enter

• ipconfig /flushdns
• ipconfig /registerdns
• ipconfig /release
• ipconfig /renew

Close the window and restart your PC.

Extra check:
If you’re trying to reach another computer, try using its IP address instead of its name. If that works, the issue is definitely name resolution (DNS) related, and your network admin or ISP might need to adjust DNS settings.

Enable DCOM

RPC and DCOM often work together when Windows components communicate across machines. If DCOM is disabled, certain RPC‑based actions can fail even if the network and services look fine.

1. Press Windows key + R to open the Run box.
2. Type dcomcnfg and press Enter. This opens Component Services.
3. In the left pane, expand Component Services → Computers.
4. Right‑click My Computer and choose Properties.
5. Go to the Default Properties tab.
6. Make sure Enable Distributed COM on this computer is checked.
7. Under Default Authentication Level, choose Connect.
8. Under Default Impersonation Level, choose Identify.
9. Click Apply, then OK and close the window.

Restart your PC and test again.

Check Network Connectivity and Profile

If your network connection is unstable or Windows thinks you’re on a “public” untrusted network, it may restrict the communication that RPC needs. Setting the correct profile and checking basic connectivity often resolves the error.

1. Check the network icon in the taskbar:
   • Make sure you are actually connected to Wi‑Fi or Ethernet.
2. Open a browser and visit a few websites to confirm the internet is working.
3. Open Settings → Network & internet.
4. Click your current Wi‑Fi or Ethernet connection.
5. Make sure the Network profile type is set to Private, not Public.
6. If you’re on a VPN, disconnect temporarily and test again.

If you’re accessing another Windows PC, make sure that device is also connected, turned on, and using a Private network profile.

Check the Windows registry for RPC corruption

If you tried all the fixes above and “RPC server is unavailable (0x800706ba)” still appears, there might be a problem with the RPC‑related registry entries. Editing the Windows registry can sometimes fix this – but it’s also risky.

If you’re not comfortable with advanced Windows settings, it’s better to skip this step or ask a professional for help.

Important: Back Up the Registry First

1. Press Windows + R, type regedit and press Enter to open Registry Editor.
2. Click File → Export.
3. Under Export range, select All.
4. Choose a location and file name, then click Save.

If something goes wrong, you can come back to File → Import and restore this backup.

Step 1: Check RpcSs (RPC Service)

1. In Registry Editor, go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RpcSs
2. In the right pane, double‑click Start.
3. Make sure Value data is set to 2 (this means “Automatic”).
4. Click OK.

Step 2: Check DcomLaunch (DCOM Server Process Launcher)

1. Go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DcomLaunch
2. In the right pane, double‑click Start.
3. Set Value data to 2.
4. Click OK.

Step 3: Check RpcEptMapper (RPC Endpoint Mapper)

1. Go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RpcEptMapper
2. Double‑click Start in the right pane.
3. Set Value data to 2.
4. Click OK.

After you finish, close Registry Editor and restart your PC. Then test again to see if the “RPC server is unavailable” error is gone.

Note: If important registry entries are missing or appear very different from those in a normal Windows installation, this can be a sign of deeper system corruption. In that case, a repair install or even a clean install of Windows might be safer than trying to fix everything by hand.

How to Prevent This Error in the Future

Once you fix the “RPC server is unavailable (0x800706ba)” error, you probably don’t want to see it again. Here are some simple habits that help keep things stable on Windows 11:

1. Keep Windows Updated: Go to Settings → Windows Update and install important updates. These often fix hidden bugs in networking and services.
2. Avoid Tweaking Core Services: Don’t randomly disable services in services.msc to “speed up” your PC. Turning off the wrong service can break RPC and other key features.
3. Use One Reliable Security Suite: Avoid running multiple antivirus or firewall programs at the same time. Stick with Windows Security or one trusted third‑party solution.
4. Shut Down Properly: Always use the normal Shut down or Restart options. Cutting power suddenly can corrupt system files and cause strange errors later.
5. Create Restore Points: Before making big changes (installing new software, heavy tweaks), create a system restore point. If something goes wrong, you can roll back easily.

Frequently Asked Questions