Yeah, that 0x80080006 error is annoying — especially when it kills a service or app mid-task. Let's get you sorted.
The Fix: Reset DCOM and RPC Services
In 90% of cases, this error means the DCOM service (or the RPC Endpoint Mapper) isn't running or got stuck. Here's the fix that works most often.
- Press Windows + R, type
services.msc, and hit Enter. - Scroll down and find DCOM Server Process Launcher. Right-click it and select Restart. If it's not running, double-click it, set Startup type to Automatic, and click Start.
- Do the same for Remote Procedure Call (RPC) and RPC Endpoint Mapper — restart them if they're running, or start them if not.
- After each restart, click OK. You don't need to reboot.
Now try whatever you were doing again. If the error clears, you're done. If not, keep reading.
Why This Works
COM objects (like OLE services) rely on the RPC infrastructure. When the DCOM launcher or RPC service gets a hiccup — often after a system update or a hung process — the communication channel breaks. Restarting those services clears the stuck state. It's the quickest win.
If That Didn't Fix It: Check DCOM Permissions
Sometimes the service runs fine but the account trying to use it doesn't have the right permissions. This bites a lot on Windows Server 2016 and 2019, especially when running scheduled tasks or IIS apps.
- Open Component Services: Press Windows + R, type
dcomcnfg, and hit Enter. - Go to Component Services > Computers > My Computer > DCOM Config.
- Find the component that's throwing the error (you might see it in the app's event log). Right-click it and choose Properties.
- Go to the Security tab. Under Launch and Activation Permissions, select Customize, then click Edit.
- Add the account that's running the app (like NETWORK SERVICE or LOCAL SERVICE) and give it Local Launch and Local Activation permissions.
- Click OK on all dialogs.
After you change permissions, the setting applies immediately. Re-run your app or service.
Less Common Variations
Corrupted Registry Entry
Sometimes the DCOM registration for a specific component gets mangled. You'll usually see this after a bad uninstall or reinstall.
- Open Registry Editor (regedit).
- Go to
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID. - Search (Ctrl+F) for the component's GUID — you'll find it in the error details or event log.
- If you find a broken entry, export it as a backup, then delete it.
Careful here—only delete if you're sure it's isolated. Deleting the wrong key can break other things.
System File Corruption
If the error pops up across multiple apps, your system files might be damaged. Run these commands in an elevated command prompt:
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealthLet sfc finish first. It might take 10–15 minutes. Then run DISM. Reboot after both.
Firewall or Antivirus Blocking RPC
On a network or server, a firewall rule can block RPC dynamic ports. Check your firewall logs for blocked connections from the app. If you're using Windows Firewall, make sure the Remote Procedure Call (RPC) inbound rule is enabled. For third-party AV, temporarily disable it to test — but only for a couple of minutes.
Prevention
- Keep Windows updated. The culprit is often a patch that broke a service, and a newer patch fixes it.
- Don't let apps run as SYSTEM unless they need to. Limit accounts to least privilege — that reduces permission-related failures.
- If you're on Server 2019, check for known issues with DCOM after certain cumulative updates. Search for the KB number and any hotfixes.
- Monitor Event Viewer under Windows Logs > System for repeated DCOM warnings. Early detection saves you from a full outage.
That's the whole playbook. Try the service restart first, then permissions, and you'll resolve most cases of 0x80080006.