The shared printer shows up, you double-click it, and Windows refuses: operation failed with error 0x0000011b. This error is not about your printer at all - it is about two PCs disagreeing on security updates.
Error 0x0000011b was born in 2021, when Microsoft patched the PrintNightmare vulnerability and changed how network printing authenticates. After those updates, a print server PC and a client PC must be on a matching patch level for the connection to be allowed. When one side has the security update and the other does not, adding the printer fails with 0x0000011b - even though printing worked for years and nothing about the printer changed. This guide walks the honest fix order: update both PCs, restart both, reconnect cleanly. It also names the famous registry workaround - and explains, plainly, why using it reopens the exact hole the patch closed.
The printer, cable and driver are innocent. The two PCs are simply speaking different security dialects, and printing is refused until they match.
PrintNightmare let any network user install printer drivers - and with them, malicious code - through the print spooler. Microsoft response was to require administrator rights and stronger authentication for network printing (the RPC authentication level change). That is good security. The side effect: a patched server refuses under-patched clients, and you get 0x0000011b. Anyone whose "fix" disables this protection is handing the vulnerability back.
The cure is boring and it works: both sides fully updated, in this order.
Leftover half-installed printer entries keep the error alive even after patching. Remove them before reconnecting.
printui /s /t2, and in the Drivers tab remove the leftover driver for that printer model if it is not used by another printerservices.msc\\ACCOUNTS-PC and double-clicking the shared printerSearch results will push you to set RpcAuthnLevelPrivacyEnabled to 0 on the print server. Be clear about what that does: it turns off the PrintNightmare protection on that server, for every PC that prints through it, permanently, until someone turns it back on. If you ever meet a network where it was applied in 2021 and forgotten, that server has been exposed ever since. The defensible use is a few hours of emergency printing while updates finish - followed by removing the value and restarting the spooler. The real fix is, and remains, matched updates.
Then the mismatch is elsewhere: check that the print spooler service runs on both PCs, confirm you can open the server share itself (folder access) to rule out a general SMB problem, and try adding the printer as a local printer on a TCP/IP or Local Port pointing at \\ACCOUNTS-PC\PrinterShare - a route that sidesteps the connection wizard on stubborn clients. If the server is a very old Windows version that no longer receives updates, the honest long-term answer is moving the printer to a maintained PC or giving the printer its own network connection.
The whole troubleshooting run, live on screen - the same order a technician follows on site.
▶️ Watch Full VideoAlmost always an update installed on one side only - typically the print server updated overnight while your PC did not, or the reverse. Check Windows Update history on both PCs for the most recent quality update dates and bring the behind one current.
Temporarily setting it and removing it the same day limits exposure, but many networks forgot it in place. If your situation truly cannot wait for updates, set it, print, remove it, restart the spooler - and write down that you did it.
No. This error is specific to printers shared from a Windows PC acting as print server. A printer connected by its own network cable or Wi-Fi with its own IP is added directly and never passes through this check.