Fix printer error 0x0000011b

0x0000011b shows up when a PC cannot connect to a printer shared from another Windows computer. It is tied to Microsoft's print spooler RPC hardening for CVE-2021-1678, enforced by updates from September 14, 2021. The fix that lasts is to install current Windows updates on the PC that shares the printer and on every PC that prints to it, then re-add the printer.

Checked November 10, 2026 against the manufacturer's own pages.

The short version

What to install and where it comes from. Every link goes to the manufacturer or Microsoft, never to a copy.

Code0x0000011b (decimal 283)
Official nameNone documented: 283 is not listed in Microsoft's system error code tables
Where it appearsAdding or printing to a printer shared by another Windows PC or print server
Security change behind itPrinter RPC binding hardening for CVE-2021-1678 (KB4599464), enforced from the September 14, 2021 updates
Windows versionsWindows 11, Windows 10 and Windows Server print hosts
Microsoft Support: Managing deployment of Printer RPC binding changes for CVE-2021-1678 (KB4599464)support.microsoft.comMicrosoft Learn: Printers Policy CSP (ConfigureRpcAuthnLevelPrivacyEnabled)learn.microsoft.comMicrosoft Support: September 14, 2021 KB5005565 for Windows 10support.microsoft.comMicrosoft Support: Fix printer connection and printing problems in Windowssupport.microsoft.com

Official files only, nothing bundled

Step by step

  1. Update the PC that shares the printer first

    On the computer the printer is plugged into, open Settings, Windows Update, Check for updates. Install everything offered and restart. KB4599464 says the update must be on all client and server devices, and the host is the side most often left behind.

  2. Update every PC that prints to it

    Repeat Settings, Windows Update, Check for updates on each client. A client and host on very different update levels is the classic setup for 0x0000011b, because the host now insists on the stronger RPC level.

  3. Restart the Print Spooler on the host

    Press Windows + R, type services.msc, right-click Print Spooler and choose Restart. Microsoft notes that the RPC privacy setting only takes effect after a device restart or a spooler restart.

  4. Remove the shared printer and add it again

    On the client go to Settings, Bluetooth & devices, Printers & scanners, select the printer, then Remove. Choose Add device, then Add manually, and pick Select a shared printer by name with the host's name and share name.

  5. Connect straight to the printer if it is on the network

    If the printer has its own network port, choose Add manually, then Add a printer using an IP address or hostname. Install the driver from the maker's site (hp.com, epson.com, canon.com or brother.com). The PC then talks to the printer itself, not to another PC's spooler.

  6. Leave RpcAuthnLevelPrivacyEnabled at its default

    Many guides tell you to set this value to 0 on the host. Microsoft's own article labels 0 as not recommended and says devices are then not protected. Treat it as a stopgap of last resort, not a fix.

Faster option: update drivers automatically

The steps above fix this one device. If several drivers are old, a driver updater finds and installs them all in one go, and backs up the current ones first.

  1. Driver Updater scan listing outdated drivers1. Scan. Download the free version and run a scan.
  2. Missing driver found with the newest version2. Review. See each old or missing driver with its newer version.
  3. Update complete with every driver updated3. Update. Update one driver free, or all at once with Pro.

Update this driver automatically

Finds and updates this driver and every other outdated driver on your PC.

Auslogics Driver Updater · Free scan · Windows 11, 10, 8, 7 · Backup before every change

What Microsoft changed in the print spooler

Microsoft’s KB4599464 article explains the change in two phases. The January 12, 2021 update added a registry value named RpcAuthnLevelPrivacyEnabled under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print (type REG_DWORD). At that point it was off unless an admin set it to 1, which raises the authentication level for the printer IRemoteWinspool interface. The September 14, 2021 update moved to the enforcement phase: from then on, updates treat a missing value as 1, so the stronger level is on without any registry edit.

That is the same patch day as KB5005565 for Windows 10, which is why the error is usually linked to that update. Microsoft’s article does not list the code 0x0000011b itself. The error appears on the client when the host demands packet privacy and the connection cannot meet it.

Why the registry workaround is a poor trade

Setting the value to 0 on the host does let old connections through. Microsoft documents 0 as “Not recommended” because it disables the higher authentication level, which leaves the print server open to the spoofing flaw. On Windows 11 version 24H2 and later, the Printers Policy CSP lists a policy called Configure RPC packet level privacy setting for incoming connections. If it is enabled or not configured, privacy stays on. Use it only to keep privacy on, and fix the outdated machine instead.

Shared printers on older hosts and network storage

Some homes and offices share a printer from a PC that no longer gets updates, or from a router or storage box. Those hosts may never support the new level. The clean answer is to stop sharing through that box and give each PC a direct connection to the printer over the network, with the maker’s current driver.

Questions

Did Microsoft remove the RpcAuthnLevelPrivacyEnabled setting?

No. Microsoft still documents it. Updates from September 14, 2021 turn enforcement on by default, and Windows 11 version 24H2 adds a Group Policy for the same value. Its own pages do not say the value was removed.

Should I uninstall KB5005565 to get printing back?

No. Removing a security update reopens the spooler flaw it closed, and later cumulative updates carry the same change anyway. Bring both computers up to date instead.

Does 0x0000011b mean my printer driver is broken?

Usually not. The driver can be fine while the connection between two PCs is refused at the RPC authentication step. A USB printer on your own PC is not affected by this change.

Why does it work on one PC but not another?

The working PC often has a matching update level with the host, or connects to the printer by IP address. Compare the OS build under Settings, System, About on each machine.