After upgrading to Windows 11 22H2 or newer, network printers vanish and you get "Operation could not be completed (error 0x00000709)" when trying to add them. This also affects 23H2, 24H2, and 25H2.

Microsoft changed the default RPC connection method from named pipes to TCP, which broke shared printer discovery in most environments.

The Quick Fix

Run this in an elevated Command Prompt or PowerShell:

reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Printers\RPC" /v RpcUseNamedPipeProtocol /t REG_DWORD /d 1 /f
net stop spooler && net start spooler

If the Printers\RPC key doesn't exist, the command creates it.

For shared printers: Apply this fix on BOTH the computer sharing the printer AND the computer trying to connect. This is the most common reason the fix "doesn't work."

Group Policy Method (Pro/Enterprise)

For domain environments or if you prefer Group Policy:

  1. Open gpedit.msc
  2. Navigate to: Computer Configuration > Administrative Templates > Printers
  3. Open "Configure RPC connection settings"
  4. Set to: Enabled
  5. Protocol: RPC over Named Pipes
  6. Click OK and run gpupdate /force

If the Fix Doesn't Work

Still seeing 0x00000709? Try these additional steps:

Relax RPC authentication (shared printer environments):

reg add "HKLM\SYSTEM\CurrentControlSet\Control\Print" /v RpcAuthnLevelPrivacyEnabled /t REG_DWORD /d 0 /f
net stop spooler && net start spooler

Apply this on both the host and client machines.

Clear stuck print jobs:

net stop spooler
del /F /Q %systemroot%\System32\spool\PRINTERS\*
net start spooler

Verify registry permissions:

  1. Open regedit
  2. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows
  3. Right-click "Windows" > Permissions
  4. Ensure your user account has Full Control

Verify the Fix

Get-Printer -Name "\\SERVER\PrinterName"

The printer should now appear without the 0x00000709 error.

Why This Happens

Starting with Windows 11 22H2, Microsoft enabled stricter RPC security (CVE-2021-1678 mitigation). The default changed from RPC over Named Pipes to RPC over TCP. Most existing shared printer setups rely on named pipes, so this breaks printer discovery and authentication.

The registry fix forces Windows back to the compatible protocol.

FAQ

Does this work on Windows 11 Home?

Yes. Windows 11 Home doesn't have Group Policy Editor, but the registry commands work identically.

Do I need to restart after the fix?

Restarting the Print Spooler service is usually enough (net stop spooler && net start spooler). A full reboot works too.

Does this affect local USB printers?

No. USB printers don't use RPC networking. This fix only applies to network and shared printers.

The fix worked but printers disappeared again after a Windows Update.

Some cumulative updates reset the RPC settings. Re-run the registry command after major updates if printers stop working.

Related Reading

Need hands-on help? Contact RainCity Techworks.