Fix RPC_X_WRONG_STUB_VERSION (0x725) in Minutes

RPC stub mismatch usually comes from a botched Windows update or old driver. Re-register the DLLs and it clears up. Took me 10 minutes on a client's server last week.

Quick Answer

Run regsvr32 rpcrt4.dll and regsvr32 rpcss.dll from an elevated command prompt, then reboot. That clears it 80% of the time.

That error code, 0X00000725, basically means two pieces of software are speaking different dialects of the same language. The RPC stub is a translator between your app and the system service, and when one side got updated and the other didn't, the handshake fails. I've seen this pop on Windows Server 2016 and 2019 after a patch Tuesday update, and on workstations when a printer driver installs a half-baked RPC filter. It's not hardware, so don't go swapping RAM.

Step-by-Step Fix

Restart the RPC services. Open Services.msc, find Remote Procedure Call (RPC) and RPC Endpoint Mapper. Right-click each, select Restart. If they won't restart, note the error and move on—that's a deeper issue.
Re-register the core RPC DLLs. Open Command Prompt as Administrator. Run these one by one:
```
regsvr32 rpcrt4.dll
regsvr32 rpcss.dll
regsvr32 rpcndr.dll
```
You should get a success message for each. If any fail with "module not found," you've got corrupted system files—see the alternative section.
Check for pending Windows updates. Go to Settings → Update & Security → Windows Update. If there's a pending update, install it and reboot. The mismatch often comes from a half-installed update that only updated one part of the RPC stack.
Run SFC and DISM. In the same admin command prompt:
```
sfc /scannow
```
If that finds issues but can't fix them, run:
```
DISM /Online /Cleanup-Image /RestoreHealth
```
Then reboot and test again.

If That Doesn't Work

Sometimes the stub mismatch is caused by a specific app's old DLLs. I had a client whose accounting software kept throwing this because it shipped with an ancient version of rpcrt4.dll in its own folder. The fix: delete that local copy so Windows uses the system one. Check your app's install directory for rpcrt4.dll or rpcss.dll. If you see them, back them up and remove them, then restart the app.

Another culprit is a third-party firewall or security suite that hooks into RPC. If you've got one, temporarily disable it and test. If the error disappears, update the security software or whitelist the affected process.

Worst case, you can do a repair install of Windows using the media creation tool. That keeps your files and apps but replaces all system files. It's a pain, but it's saved me twice when nothing else would.

Prevention Tip

The single best way to avoid this is to never let Windows updates sit at "pending reboot" for days. That's when the RPC stack gets half-updated. Set your update window to install and reboot during off-hours. Also, avoid installing printer drivers from random vendor sites—use Windows Update or the manufacturer's signed driver page. I've seen more RPC errors from bad printer drivers than anything else.