RPC_NT_WRONG_PIPE_VERSION (0XC003005E) Fix

Frustrating? Yeah, I've seen it a dozen times.

This error pops up when a client tries to talk to a server via RPC, but the pipe version numbers don't line up. The common scenario: you're trying to remotely manage a Windows Server 2022 box from a Windows 11 machine, or vice versa, and you get hit with 0XC003005E. It's not a hardware issue, it's a protocol version mismatch.

The fix: Align the RPC pipe version

Don't waste time reinstalling anything. The culprit is almost always a missing or corrupted registry key that defines the RPC pipe version. Here's what works:

1. Open Registry Editor as admin. No, not as a regular user — use Regedit from an elevated command prompt.
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ServerPipes. If it's missing, create it. Right-click Rpc, select New > Key, name it ServerPipes.
3. Create a new DWORD (32-bit) value called DefaultPipeVersion. Set it to 2. That forces the server to accept pipe version 2, which is what most modern Windows clients use.
4. Reboot the server. No, restarting the RPC service won't cut it — a full reboot is required for the registry change to take effect.

Test your RPC connection again. If you're still stuck, check the client side: on the client machine, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientPipes, create the same DefaultPipeVersion DWORD, and set it to 2. Reboot the client too.

Why this works

RPC uses named pipes for communication, and each pipe has a version number. Windows 10/11 and Server 2019/2022 all support pipe version 2, but sometimes the server side still defaults to version 1 if the registry key didn't get written during OS updates or if an older version of the RPC runtime was installed. The DefaultPipeVersion DWORD tells the RPC subsystem which version to advertise. Setting it to 2 makes both sides agree on the protocol. No more mismatch, no more error.

Less common variations

Sometimes the error isn't fixed by just that registry key. Here are the edge cases I've run into:

• Mixed OS environments: You've got a Windows 8.1 or Server 2012 R2 box trying to talk to a newer server. Those older OSes default to pipe version 1. Set the DWORD to 1 on the server side instead of 2 to match the older client. Don't bother changing the client — it's stuck at version 1.
• Corrupted RPC service files: Run sfc /scannow and dism /online /cleanup-image /restorehealth. Rare, but I've seen it after dirty Windows Updates that skipped RPC DLLs.
• Third-party RPC interceptors: Antivirus or backup software that hooks into the RPC stack. Temporarily disable the service to test. If the error goes away, you know who to blame. Whitelist the RPC ports (135, 445, plus dynamic ports) in your AV.
• Firewall blocking RPC dynamic ports: RPC uses port 135 for the endpoint mapper, then negotiates a random high port (1024-5000 or 49152-65535, depending on OS). If your firewall only allows 135, the pipe negotiation fails. Open the full range for RPC traffic between the two machines.

Prevention: Stop it from coming back

This error shouldn't recur if you follow these rules:

• Keep OS versions consistent: If you can, avoid mixing Windows Server 2022 with Windows 10 pre-1903. Both are fine, but the older build's RPC stack is dodgy. Upgrade all clients to at least Windows 10 1909 or Windows 11.
• Deploy the registry fix via Group Policy: Push DefaultPipeVersion = 2 to all servers in your domain under HKLM\SOFTWARE\Microsoft\Rpc\ServerPipes. That way, new builds don't default to version 1.
• Log RPC errors early: Enable RPC auditing in Event Viewer under Applications and Services Logs/Microsoft/Windows/RPC. Look for event ID 1912 or 1913 — those are the pipe version mismatch events. Catch them before users complain.

That's it. Three registry keys, a reboot, and you're done. No need to rebuild anything.