Error 0x0000011b is one of those Windows printing errors that's been around for years, but it's worth being precise about which version of it you're actually hitting, because the cause — and the fix — depends on whether your printer is network-shared or connected directly via USB.
The common case: network-shared printers
This is the version of the error most people run into, and it's been happening since 2021. It stems from a Windows security update (KB5005565 and related patches) that addressed a Print Spooler vulnerability by tightening RPC (Remote Procedure Call) authentication requirements for network printer connections. The stricter authentication can break existing connections to printers shared from another computer on the network, especially in small office or home network setups without a proper Windows domain.
Fix: adjust the RPC authentication registry key
- Press Windows key + R, type
regedit, and press Enter. - Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print - Right-click in the right-hand pane, select New → DWORD (32-bit) Value, and name it
RpcAuthnLevelPrivacyEnabled - Double-click the new value and set it to 0 to relax the authentication requirement (note: this does slightly reduce the security hardening the original update was meant to add — only do this if you understand and accept that tradeoff, ideally on a trusted home or small office network rather than a larger enterprise one).
- Restart the computer and try connecting to the printer again.
Better long-term fix: if you're dealing with this repeatedly across a small office, consider moving from peer-to-peer printer sharing to a dedicated print server with printers assigned static IP addresses. This sidesteps the RPC authentication issue entirely since you're connecting via IP rather than through Windows file/printer sharing, and it's significantly more stable for any network with more than a couple of people sharing a printer.
The newer case: USB-connected printers after KB5087544
This is a separate, more recent issue. Microsoft's own documentation for update KB5087544 (released May 12, 2026 for Windows 10 LTSC and Extended Security Update/ESU systems) lists intermittent 0x0000011b errors specifically affecting some multifunction printers from Brother, Canon, and Ricoh when connected via USB — not network printers at all.
Important to note: this specific case only applies to Windows 10 systems enrolled in the Extended Security Update program, not the general Windows 10 or Windows 11 population — so if you're not on ESU, this particular cause doesn't apply to you, and you're more likely dealing with the network-printer case above instead.
Fix: Microsoft's official workaround
As of this update, Microsoft has not yet shipped a permanent fix for this specific USB case — they've acknowledged it and are working on a resolution. In the meantime, their documented workaround is straightforward:
- Switch the affected printer to a network connection instead of USB, if the printer supports Wi-Fi or Ethernet. This avoids the bug entirely since it's specific to the USB connection path.
- If a network connection genuinely isn't an option for your setup, keep an eye on Windows Update for a follow-up patch addressing this specifically — Microsoft has indicated a fix is in progress.
How to tell which one you're dealing with
A quick way to narrow it down:
- If your printer is shared over the network from another PC, and you're not specifically on Windows 10 ESU — you're almost certainly hitting the older, well-documented RPC authentication case. Use the registry fix above.
- If your printer is connected directly via USB, it's a Brother, Canon, or Ricoh multifunction model, and you're on Windows 10 with ESU — you're likely hitting the newer KB5087544-specific bug. Switch to network connection as the current workaround.
Both produce the identical error code and message, which is exactly why it's worth checking your specific setup against these two cases rather than assuming it's the same fix that worked for someone else's different situation.