Fix 0x80010012 (RPC_E_SERVER_DIED_DNE) in Windows

You're right in the middle of composing an email in Outlook 2019, or maybe dragging a file in Windows Explorer, and bang — dialog box says "RPC_E_SERVER_DIED_DNE (0x80010012)". The COM object that was handling your action just died. It's especially common when you have a lot of add-ins running (think Outlook with Slack, Teams, and a PDF plugin) or after a failed Office update. I've seen it trigger when a COM component from a third-party app (like a cloud storage sync tool) tries to talk to Explorer.

What's actually happening?

COM (Component Object Model) is Windows' way of letting apps share features. When one app asks another to do something — like Outlook asking Word to render an email — it creates a server process. That server process can crash silently. The error code 0x80010012 literally means "the server died and is no longer available." Your app is still waiting for a response from a ghost.

This isn't a broken Windows file or a virus. It's a timing or stability issue inside the COM infrastructure. The fix is to reset those servers without reinstalling everything.

The real fix: Reset COM servers

Skip the disk cleanup and SFC scans — they don't touch this. Here's what works.

Step 1: Kill all COM processes

Press Ctrl+Shift+Esc to open Task Manager.
Go to the Details tab. Look for any dllhost.exe or comhost.exe processes. Right-click each one and choose End task.
Also end outlook.exe or explorer.exe (don't worry — Windows will restart Explorer after a few seconds).

This clears out all dangling COM server instances. You might see a brief flicker as Windows restarts Explorer, that's normal.

Step 2: Clear the COM registry cache

Windows stores a cache of COM classes in a specific registry key. If it's corrupted, you get this error.

Press Win+R, type regedit, and hit Enter.
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\COM\
Look for a key named AppID or ClassID — don't delete those. Instead, find the key PendingDelete under COM.
If PendingDelete exists, right-click it and choose Export to back it up, then delete it.

I've seen corrupted cache entries linger here for weeks. Cleaning it forces Windows to rebuild the COM database on next reboot.

Step 3: Re-register COM libraries

This step rebuilds your COM class registrations from scratch.

Open Command Prompt as Administrator (search for "cmd", right-click, choose Run as administrator).
Run these commands one at a time:
regsvr32 /u /s vbscript.dll
regsvr32 /s vbscript.dll
regsvr32 /u /s jscript.dll
regsvr32 /s jscript.dll
Then run this to reset the entire COM subsystem:
for %i in (%windir%\system32\*.dll) do regsvr32 /s %i 2>nul

This last command takes about a minute. It'll re-register hundreds of DLLs. You'll see no output — that's fine.

Step 4: Reboot and test

Restart your machine. Open the app that was crashing (usually Outlook or File Explorer). Try the same action that triggered the error before. If it works, you're golden.

If it still fails

Sometimes the root cause is a specific add-in or service. Here's what to check:

Outlook add-ins: Go to File > Options > Add-ins. Disable all non-Microsoft add-ins. Restart Outlook. If the error disappears, enable add-ins one by one to find the culprit. I've seen Zoom plugin and Dropbox for Outlook trigger this.
Third-party COM servers: Apps like Adobe Acrobat, Google Drive, or OneDrive install their own COM objects. Try disabling or updating them.
Antivirus interference: Some security software blocks COM calls. Temporarily disable your antivirus and see if the error stops. If yes, add an exception for the affected app.
Windows Update: Make sure you're on the latest cumulative update for your OS version (Windows 10 22H2 or Windows 11 23H2). Microsoft fixed a batch of COM bugs in late 2023 patches.

If none of that works, you might have deeper corruption. Try an in-place repair install using the Windows 11/10 ISO — it keeps your files and apps but replaces system files. That's a last resort, but it's saved me twice.