Fix 0X8001000A: RPC_E_CANTTRANSMIT_CALL (Outlook/Office)

Outlook or Office throws 0X8001000A when RPC calls can't send. Fix by clearing COM+ cache, repairing Office, or checking DCOM permissions. Real fix steps below.

You're in the middle of replying to a client email, and suddenly Outlook goes gray and stops responding. You kill it, reopen, and get a popup: RPC_E_CANTTRANSMIT_CALL (0X8001000A). It's not just Outlook either—Word, Excel, and even some custom line-of-business apps throw this when they try to talk to another process through RPC (Remote Procedure Call). I've seen this on Windows 10 and 11, mostly with Office 2016 and 365, but also with older Office 2013. The trigger is usually when you've got a bunch of add-ins loaded, or you're using a network drive for your OST/PST file, or you've just patched Windows and something in the COM+ catalog got scrambled.

What Actually Causes This Error?

Plain English: when an app tries to call a function in another component (like Outlook talking to Exchange, or an Excel add-in reaching out to a COM object), Windows sends a message through the RPC channel. That channel relies on a hidden helper called COM+ running in the background. When the COM+ catalog gets corrupted, or a stale registration from an uninstalled program still lingers, the transmission fails. The error code 0X8001000A literally means "the call couldn't be transmitted." It's not your network, it's not your Exchange server—it's local to the machine.

Most of the time, I trace it back to one of three things: a half-broken Office add-in, a corrupted COM+ registration, or a permissions issue on the DCOM endpoint. Had a client last month whose entire print queue died because of this—their label printer software left behind a COM object that clashed with Outlook. Remove the add-in, problem went away. But you can't always find the culprit that easy, so here's the systematic fix.

The Fix: Step-by-Step

Start with the quickest thing that works 60% of the time, then move down. Don't skip steps—each one builds on the last.

Step 1: Kill the COM+ Surrogate and Restart it

Open Task Manager (Ctrl+Shift+Esc). Look for COM Surrogate or dllhost.exe processes. Right-click each and End Task. Then open Command Prompt as Administrator and run:

net stop comsysapp
net start comsysapp

This restarts the COM+ system application. If the error was from a transient glitch, this clears it. I've seen this fix the issue for a day or two, but if it comes back, move to step 2.

Step 2: Clear the COM+ Catalog Cache

This is the real fix for most people. The COM+ catalog stores registration info for all components. When it gets bloated with old entries, calls start failing. Here's how to rebuild it:

Close all Office apps.
Open Command Prompt as Administrator.
Run regsvr32 /u comsvcs.dll and then regsvr32 comsvcs.dll to re-register the COM+ services.
Now delete the cached catalog files. Navigate to C:\Windows\System32\Com\ and find files named *.catalog (they may be hidden). Right-click and delete them. You'll need to take ownership first—right-click the folder, Properties, Security, Advanced, change owner to your admin account, then try again.
Reboot. Windows will rebuild the catalog from the registry.

I've done this on a dozen machines. It's the closest thing to a silver bullet for this error.

Step 3: Repair Office Installation

If the cache clear didn't stick, the problem might be in the Office install itself. Go to Control Panel > Programs and Features, find Microsoft Office, right-click, and choose Change. Select Quick Repair first. If that doesn't do it, run Online Repair—it takes longer but it's thorough. This fixes any corrupted DLLs that might be interfering with RPC.

Step 4: Check DCOM Permissions

Sometimes the error pops up when a non-admin user tries to run an Office add-in that needs higher privileges. Open Component Services (type dcomcnfg in Run). Expand Component Services > Computers > My Computer > DCOM Config. Find the entry for Microsoft Office Outlook or Microsoft Word (it might be under a generic name like Microsoft Office 16.0 Object Library). Right-click, Properties, go to Security tab. Under Launch and Activation Permissions, click Edit and make sure Everyone or the specific user has Local Launch and Local Activation checked. Apply and restart.

Step 5: Remove Suspicious Add-ins

If you're still stuck, the culprit is likely a third-party add-in. Go to File > Options > Add-ins in Office. At the bottom, change the Manage dropdown to COM Add-ins and click Go. Uncheck everything that isn't Microsoft (like Adobe Acrobat PDF Maker, or some CRM plugin). Restart. If the error disappears, re-enable them one by one to find the bad apple.

If It Still Fails

You've cleared the cache, repaired Office, fixed permissions, and disabled add-ins—but the error still shows. Don't waste time. Run the System File Checker to rule out OS corruption:

sfc /scannow

Then check the Windows Event Log under Application—look for errors with source Microsoft-Windows-Complus or DCOM. The event details often name the exact CLSID or EXE that's failing. Google that CLSID—it'll lead you to the specific app causing the mess. I had a client where it was an old antivirus shell extension. Removing that app fixed it permanently.

Last resort: create a new Windows user account and test Office from there. If it works, it's a profile-level corruption. Migrate your data and move on. That's the hard truth—sometimes profiles get so tangled that rebuilding is faster than untangling.

One more thing: if you're on a company network and this happens across multiple machines, talk to your admin. It might be a Group Policy pushing a broken DCOM setting. But for a single machine, these steps will get you back to work in under an hour.