Independent printer help. Not affiliated with any printer manufacturer.

What this error means

You see "Windows cannot connect to the printer. Operation failed with error 0x0000011b" when a PC tries to connect to a printer that is shared from another Windows computer. Starting in 2021, Microsoft tightened how Windows PCs authenticate print connections with each other to close a security hole, and a connection that doesn't meet the stricter rules is refused with this code. The printer itself is fine and usually still prints from the computer it's attached to.

Common causes

  • The host PC and the connecting PC are on different Windows update levels
  • An old printer connection or driver set up before the security change
  • The connecting PC is trying to pull a driver from the host in a way current rules block
  • The host runs an old Windows version that no longer receives updates

How to fix it

Start with the first fix. They’re ordered from safest and quickest to most involved.

Fixes for Windows

0 of 6 steps tried

  1. Update both computers

    On the PC that shares the printer and on every PC that connects to it, open Settings > Windows Update (Windows 10: Settings > Update & Security > Windows Update), install everything offered and restart. Most 0x0000011b cases clear once both machines are fully up to date.

  2. Remove and re-add the shared printer

    On the connecting PC, go to Settings > Bluetooth & devices > Printers & scanners, select the printer and choose Remove. Restart, then press Win + R, type two backslashes followed by the host PC's name (for example \\OFFICE-PC) and press Enter. Right-click the shared printer and choose Connect.

  3. Install the driver on the connecting PC first

    Download the current driver for your printer model and Windows version from the manufacturer's official support site and install it on the connecting PC before you reconnect. When a matching driver is already installed, Windows doesn't need to fetch one from the host, which avoids a common failure point.

  4. Connect to the printer directly instead of through the PC

    If the printer has Wi-Fi or Ethernet, skip sharing altogether and add it to each computer by IP address. Choose Add device, then Add manually (Windows 10: The printer that I want isn't listed), select Add a printer using an IP address or hostname and enter the printer's address. This removes the PC-to-PC connection that triggers the error.

  5. Use a local port that points at the share

    In the same Add manually window, choose Add a local printer or network printer with manual settings, then Create a new port > Local Port, and enter the share path, for example \\OFFICE-PC\Printer. Pick the driver you installed earlier. This type of connection often works where the standard shared connection is refused.

  6. Temporary registry workaround on the host PC (Advanced, lowers security)

    Use this only if nothing else works, and only as a stopgap: it switches off the print connection hardening on the host PC and reopens the vulnerability Microsoft patched. Microsoft has been removing this option, so on current Windows builds it may have no effect. Back up the registry first (in regedit, File > Export). On the host PC, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print, create a DWORD (32-bit) Value named RpcAuthnLevelPrivacyEnabled with value 0, and restart the Print Spooler. Delete the value as soon as both PCs are updated or you have switched to a direct connection.

Common questions

Should I uninstall the Windows update that caused it?

No. Removing security updates leaves both PCs exposed, and the change returns with the next update anyway. Updating both machines and reconnecting is the lasting fix.

Does 0x0000011b mean my printer is broken?

No. It's a rule about how two Windows PCs talk to each other. Printing from the computer the printer is attached to keeps working.

How do I avoid this on a home network?

If your printer supports Wi-Fi or Ethernet, connect each computer straight to the printer by IP address rather than sharing it through one PC. Direct connections aren't affected by this error.

Press Enter to see all results. Use ↑ ↓ to move.