Shared Printer Error 0x0000011b Fix Windows Cannot Connect to the Printer
The shared printer worked for months, then Windows started refusing the connection with error 0x0000011b. Nothing is broken — a security update changed the rules. Here is the fix.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 15 minute fix
🎥 The full printer training video — sharing, ports and network errors shown live
Error 0x0000011b appears when you connect to a printer shared from another PC and Windows says "Windows cannot connect to the printer. Operation failed with error 0x0000011b." The cause is known: security updates (starting with the PrintNightmare fixes, notably KB5005565) raised the RPC authentication level that print sharing uses. If the host PC and your PC are not on matching update levels, the connection is refused. Your printer and driver are fine. Fix it properly in this order.
The Exact Error Dialog
Connect to Printer
Windows cannot connect to the printer. Operation failed with error 0x0000011b.
Printer itselfWorking — prints from the host PC
Real causeRPC authentication mismatch after updates
If the host PC prints normally and only network clients get 0x0000011b, the diagnosis is already done — it is the update mismatch.
1
First — Fully Update Both PCs
Microsoft later shipped updates that align both sides. Most 0x0000011b cases disappear once the host and the client are both fully updated.
On the host PC (the one the printer is attached to and shared from): Settings → Windows Update → Check for updates, install everything, restart
Do exactly the same on your PC
Remove the failed printer connection and connect again
If both are fully updated and the error stays, go to Fix 2
2
The Registry Fix on the Host PC
This tells the host to not demand the raised RPC privacy level, so clients can connect again. Do it on the host PC only, and back up the registry key first (File → Export in Registry Editor).
Press Windows + R, type regedit, Enter
Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print
Right-click in the right pane → New → DWORD (32-bit) Value, name it RpcAuthnLevelPrivacyEnabled
Double-click it and set the value to 0
Restart the Print Spooler (net stop spooler then net start spooler in admin Command Prompt) or simply restart the host PC
Connect to the shared printer again from your PC
Registry Editor — The Value to Add on the Host
KeyHKLM\SYSTEM\CurrentControlSet\Control\Print
Value nameRpcAuthnLevelPrivacyEnabled
Type / DataREG_DWORD / 0
One value, on the host only. Client PCs need no registry change for this fix.
3
The Same Fix From PowerShell
If you manage several host PCs, the PowerShell version is one line — run it in PowerShell as Administrator on the host:
If the printer itself has Wi-Fi or a LAN port, the cleanest permanent answer is to stop using the shared connection and add the printer directly on each PC by its IP address. Direct printing never touches the sharing authentication, so 0x0000011b cannot occur.
Choose Add a printer using an IP address or hostname, enter the printer's IP
Reserve that IP in the router so it stays fixed
Security honesty note: Fix 2 relaxes a security mitigation Microsoft added for a reason. On a trusted home or office network it is the accepted workaround, but prefer fully updated PCs (Fix 1) and direct IP printing (Fix 4) where you can, and treat the registry change as the fallback, not the default
🎥 Complete Knowledge and Installation in the Video
See printer sharing, ports and the complete troubleshooting method demonstrated live in the full training video.
Why did error 0x0000011b start suddenly when nothing changed?
Something did change — Windows Update. Security updates raised the RPC authentication level for print sharing. If the host PC took the update and your PC did not (or the other way round), the two sides no longer agree and the connection is refused with 0x0000011b.
Should I apply the registry fix on my PC or the host PC?
On the host PC — the computer the printer is physically attached to and shared from. The value RpcAuthnLevelPrivacyEnabled set to 0 goes in HKLM\System\CurrentControlSet\Control\Print on that machine, followed by a spooler restart or reboot.
Is uninstalling the Windows update a good fix for 0x0000011b?
It works as a temporary measure but is the worst long-term option, because that update also carries security fixes against print spooler attacks. Update both PCs fully first, use the registry value on the host if needed, or switch to direct IP printing.
This guide is based on the printer training video by Technical Anshu • Stuck on a step? Ask in the video comments — you will get an answer there 🙏