UUID 0XC002000C: Object Already Registered Fix

This one's a pain. Let's fix it.

You're staring at 0XC002000C — RPC_NT_ALREADY_REGISTERED. The object's already been registered, and Windows isn't having it. I've seen this on Windows Server 2019 and 2022 mostly, but also on Windows 10 Pro. The fix is straightforward once you know where to look.

Step 1: Find the duplicate endpoint

Open an elevated Command Prompt or PowerShell. Run:

rpcdump.exe /list

If you don't have rpcdump.exe installed (it's part of the Windows SDK), grab it from a dev machine or use rpcdump /list from Sysinternals. Look for duplicate UUID entries. The error almost always shows up when two services try to register the same interface UUID. I've seen it most with DFS Replication service and third-party backup agents.

Step 2: Kill the offending process

Once you spot the duplicate UUID, cross-reference it against the Process ID (PID) column. Then run:

taskkill /F /PID <offending_pid>

Don't bother restarting the service yet — you need to find what's causing the double registration first.

Step 3: Check startup dependencies

Run services.msc and look for services that start automatically and depend on RPC. The usual suspect: a service that starts twice — once normally and once via a scheduled task or a second service that calls the same RPC endpoint. I've debugged this on a client's Windows Server 2022 where they had both the built-in DFS service and a third-party sync tool both trying to register the same UUID. Disable the duplicate, and the error vanishes.

Why this error happens

The RPC endpoint mapper maintains a list of all registered UUIDs. When a process tries to register a UUID that's already in the mapper's table, you get 0XC002000C. It's a protection mechanism — stops two services from fighting over the same interface. The root cause is almost always a misconfigured service that starts twice, or two different applications that happen to share the same UUID (rare but happens with bad implementations).

Less common variations

I've run into three edge cases you should know about:

• Corrupted RPC endpoint mapper — rare, but I've seen it after a failed Windows update. Run sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth. Then reboot.
• UUID conflicts with VMware tools — VMware's vmtoolsd.exe has been known to register custom UUIDs that clash with Windows services. Uninstall and reinstall VMware Tools if you're on ESXi.
• Antivirus interference — Some AV products (looking at you, older Symantec Endpoint Protection) hook into RPC and cause duplicate registrations. Disable the AV temporarily to test. If the error stops, update or replace the AV.

If none of those work, check the System Event Log for Event ID 8193 or 5719 — they'll point to the exact service causing the problem.

Prevention

Stop this from coming back:

• Never install two products that claim to manage the same RPC interface. DFS vs third-party sync tools is a classic trap.
• Review your scheduled tasks. If you have a task that starts a service, make sure the service isn't already set to Automatic start.
• Patch Windows regularly. Microsoft fixed a few RPC duplication bugs in KB5005110 and later cumulative updates.
• Use rpcdump /list as a quick health check — run it after any major software install to catch duplicates early.

That's it. Go kill that duplicate process and get back to your day.