Fix 0x000006D9 Endpoint Mapper Error

I know this error drives people nuts—it's cryptic, it pops up when you're trying to print or connect to a remote service, and the error message doesn't tell you anything useful. Let's cut through it.

The Quick Fix: Disable the Firewall (Temporarily)

In my years running a help desk, 0x000006D9 almost always comes down to the Windows Firewall blocking RPC dynamic ports. Here's the fastest way to confirm it:

Press Win + R, type wf.msc, and hit Enter.
Click Windows Defender Firewall Properties (top center).
On each profile tab (Domain, Private, Public), set the firewall state to Off.
Try your operation again (like printing or connecting to a remote service).

If the error disappears, you've found the culprit. Now turn the firewall back on—we'll fix it properly instead of leaving it off.

Why This Works

The endpoint mapper uses dynamic ports (usually 49152–65535) for RPC services. The firewall often blocks these by default, especially after updates like Windows 10 1809 or Windows 11 22H2. When the client can't reach the endpoint, you get 0x000006D9. Disabling the firewall is the brute-force test.

The Permanent Fix: Add Firewall Rules for RPC

Don't leave your firewall off. Instead, add inbound rules that allow RPC dynamic ports. Here's the clean way:

Open Windows Defender Firewall with Advanced Security again.
Click Inbound Rules → New Rule… on the right.
Choose Port, then TCP and Specific local ports.
Enter the range: 49152-65535.
Select Allow the connection.
Check all three profiles (Domain, Private, Public).
Name it something like "RPC Dynamic Ports" and finish.

You also need to allow the RPC Endpoint Mapper itself. Create another rule, but this time for Program, and point to C:\Windows\System32\svchost.exe. That covers the endpoint mapper since it runs inside svchost. I know that sounds broad, but Windows handles it correctly in most cases. If you want to be granular, you can use netsh instead.

netsh advfirewall firewall add rule name="RPC Dynamic Ports" dir=in action=allow protocol=TCP localport=49152-65535
netsh advfirewall firewall add rule name="RPC Endpoint Mapper" dir=in action=allow protocol=TCP localport=135

Port 135 is the endpoint mapper's well-known port. You'll definitely want that open too.

Less Common Causes and Their Fixes

Sometimes it's not the firewall. Here are other scenarios I've seen:

Print Spooler Service Not Running

If this error appears when printing, check the Print Spooler. Go to Services (Win + R, type services.msc), find Print Spooler, and make sure it's running. If it's not, right-click and start it. I've seen this happen after a Windows update killed the spooler.

RPC Services Are Disabled

Open Services again and verify these are all set to Automatic and running:

Remote Procedure Call (RPC)
RPC Endpoint Mapper
DCOM Server Process Launcher

If any are disabled, set them to automatic and restart. This matters most on Windows Server, but I've seen it on workstations too.

Network Profile Is Public

Windows treats Public networks more strictly. If you're on a corporate or home network, switch the profile to Private. Go to Settings → Network & Internet → Wi-Fi (or Ethernet), click your connection, and choose Private network. This can immediately unblock RPC if your firewall rules only apply to Private.

Third-Party Firewall or Antivirus Interference

Windows Firewall isn't the only suspect. Symantec, McAfee, and even some lightweight security suites have their own filters. Temporarily disable them (or their firewall component) to test. If the error clears, add exceptions for svchost.exe and port 135.

Prevention: Stop It From Coming Back

Once you've fixed it, keep it fixed. Here's what I'd do:

Set Windows Firewall rules as shown above—don't just disable the firewall permanently.
Check your firewall after every major Windows update. I've seen updates reset rules without warning.
If you use a VPN or remote access tool, make sure its service is set to Automatic and isn't dependent on a delayed start.
Keep your printer and network drivers updated. Outdated drivers can cause RPC calls to fail intermittently.

The endpoint mapper error is a classic Windows quirk—annoying but fixable in minutes once you know where to look. Remember, the firewall is your first suspect, services are second, and network profile is the sneaky third. Tackle them in that order and you'll be back to work before you know it.