SECURITY WARNING: Never run commands you don't understand. Always review code before execution. Use at your own risk.
FixMyError.net
Windows New Added 9 October 2026

Windows: The RPC server is unavailable (0x800706BA)

The client could not complete a remote procedure call to the target machine. RPC first contacts the endpoint mapper on TCP 135, then switches to a dynamic high port, and a firewall that allows 135 but not the high range is the classic cause. It surfaces in WMI, remote management, domain joins and certificate enrolment, so it looks like a fault in whichever tool you were using. DNS pointing at a stale address is the other usual suspect.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix
# PowerShell: does the name resolve to the machine you expect?
Resolve-DnsName server01

# Endpoint mapper reachable?
Test-NetConnection server01 -Port 135

# RPC then uses 49152-65535. On the target, find a listening port to test:
#   netstat -ano | findstr LISTENING
Test-NetConnection server01 -Port 49668

# On the target: enable the built-in rule groups rather than single ports
Enable-NetFirewallRule -DisplayGroup "Windows Management Instrumentation (WMI)"
Enable-NetFirewallRule -DisplayGroup "Remote Service Management"

# And confirm the services are running there
Get-Service RpcSs, RpcEptMapper, Winmgmt

How to diagnose Windows errors

Windows errors surface as numeric codes that mean little on their own, but the operating system keeps detailed logs that almost always contain the real cause. Two categories dominate developer machines: missing Visual C++ redistributables (a DLL-not-found error for a runtime the application assumed was present) and architecture or dependency mismatches (the 0xc000007b family, usually a 32-bit/64-bit mix).

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

  1. Read Event Viewer under Windows Logs → Application and System, filtered to the time of the failure. The numeric code in the dialog maps to a detailed entry there.
  2. For MSI failures, install with verbose logging: msiexec /i package.msi /l*v install.log, then search the log for "Return value 3". The lines just above name the failing action.
  3. For missing DLLs, install the matching Visual C++ Redistributable and confirm the architecture matches the application (x64 versus x86).
  4. Repair system corruption with sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth, in that order.
  5. For access-denied errors, check both NTFS permissions and whether the process needs elevation; UAC virtualisation can make writes appear to succeed while landing elsewhere.

Tools worth reaching for

  • Event Viewer
  • msiexec /l*v
  • sfc /scannow
  • DISM /RestoreHealth
  • Process Monitor (ProcMon)

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

learn.microsoft.com learn.microsoft.com

Related Windows errors

See all 20 Windows errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.