Fixes / Windows · Checked

Windows printer error 0x0000011b: what it means and how to fix it

Short answer

Error 0x0000011b means Windows refused to connect to a printer shared from another PC. A security change (CVE-2021-1678) raised the authentication level for remote printing, and the two computers no longer agree. The fastest fix is on the PC that shares the printer: add the DWORD RpcAuthnLevelPrivacyEnabled = 0 under HKLM\SYSTEM\CurrentControlSet\Control\Print, then restart the Print Spooler.

What this message means

The message appears when a Windows PC tries to add or print to a printer that is shared by another Windows computer or print server. Since the September 14, 2021 updates, the sharing computer requires encrypted (privacy-level) RPC authentication for the remote printing interface. If the connecting computer, its driver install, or the network path cannot meet that requirement, Windows cancels the connection and shows error 0x0000011b. Windows 11 version 22H2 and later add another change: printer traffic between computers uses RPC over TCP by default instead of Named Pipes, so blocked firewall ports or mixed Windows 10 and 11 setups can trigger the same failure. The printer itself is usually fine.

Common causes

CauseHow to tell
Print RPC authentication enforcement on the sharing (host) PCThe printer prints fine from the host PC, but every other computer gets 0x0000011b when adding or using the shared printer. It started after a Windows update on the host.
The printer driver cannot be installed through the shared connectionThe error appears while you are clicking Connect or adding the printer from Network in File Explorer, before any page is ever printed.
Windows 11 22H2 or later using RPC over TCP with blocked portsOne or both PCs run Windows 11 22H2 or newer, and a third-party firewall or antivirus is installed, or the connection fails only between specific machines. Port 135 or the 49152 to 65535 range is blocked.
Mismatched Windows update levels between the two PCsOne PC shows pending or failed updates in Settings > Windows Update while the other is fully current. Connections worked before one of them updated.
Stuck Print Spooler servicePrint jobs sit in the queue on the host, or the Printers list is slow to open. Restarting the host sometimes makes the error go away temporarily.

How to fix it

1. Set RpcAuthnLevelPrivacyEnabled to 0 on the PC that shares the printer

  1. On the host PC (the one the printer is plugged into or that shares it), press Windows + R, type regedit and press Enter. Approve the admin prompt.
  2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print.
  3. Right-click the Print key, choose New > DWORD (32-bit) Value and name it RpcAuthnLevelPrivacyEnabled (if it already exists, just open it).
  4. Double-click it, set Value data to 0 and click OK.
  5. Restart the host PC, or run services.msc and restart the Print Spooler service.
  6. On the other PC, add the shared printer again. Note: this lowers the protection Microsoft added for CVE-2021-1678, so use it on trusted home or small office networks only.

2. Restart the Print Spooler on both computers

  1. Press Windows + R, type services.msc and press Enter.
  2. Find Print Spooler in the list, right-click it and choose Restart.
  3. Do the same on the other computer.
  4. Try connecting to the printer again.

3. Add the shared printer through a Local Port instead of a network connection

Windows 11: Settings > Bluetooth & devices > Printers & scanners > Add device > Add manually. Windows 10: Settings > Devices > Printers & scanners > Add a printer or scanner > The printer that I want isn't listed.

  1. Install the printer driver on the client PC first, using the installer from the printer maker's website.
  2. Find the printer's share path, for example \\OFFICE-PC\HP_LaserJet (open File Explorer > Network > the host PC to see the share name).
  3. Open the Add Printer wizard using the path for your Windows version above.
  4. Choose Add a local printer or network printer with manual settings, then Next.
  5. Select Create a new port, set Type of port to Local Port, click Next and enter the full share path.
  6. Pick the printer make and model (or Have Disk), finish the wizard and print a test page.

4. Allow RPC over TCP through the firewall (Windows 11 22H2 and later)

Windows 11 version 22H2 and later, on either PC

  1. On the host PC, make sure TCP port 135 (RPC Endpoint Mapper) is not blocked by Windows Firewall or third-party security software.
  2. Allow inbound TCP ports 49152 to 65535 on the host, or fix RPC to a single port with Group Policy: Computer Configuration > Administrative Templates > Printers > Configure RPC over TCP port.
  3. Make sure File and Printer Sharing is turned on for the Private network profile on the host.
  4. Retry the connection from the client PC.

5. Switch Windows 11 back to RPC over Named Pipes (legacy setups)

Windows 11 version 22H2 and later, when RPC over TCP cannot be made to work (for example old print servers). Group Policy Editor needs Pro, Enterprise or Education; Home users use the reg add commands.

  1. On the client PC, open Command Prompt as administrator.
  2. Run: reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers\RPC" /v RpcUseNamedPipeProtocol /t REG_DWORD /d 1 /f (same as Configure RPC connection settings = RpcOverNamedPipes).
  3. If the host is Windows 11 22H2 or later, run on the host: reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers\RPC" /v RpcProtocols /t REG_DWORD /d 0x7 /f (same as Configure RPC listener settings = RpcOverNamedPipesAndTcp).
  4. Also set RpcAuthnLevelPrivacyEnabled to 0 on the host as in the first fix, which Microsoft lists as needed for Named Pipes.
  5. Restart both PCs and add the printer again.

6. Bring both PCs to the same update level

  1. On each PC, open Settings > Windows Update (Windows 10: Settings > Update & Security > Windows Update).
  2. Click Check for updates and install everything, including optional driver updates.
  3. Restart both PCs.
  4. Try adding the printer again before changing any registry values.

Next time, skip the search

Crade is an AI assistant for Mac and Windows that sees your screen. When a message like this pops up, ask “what does this mean?” and it explains the exact error in front of you, step by step.

Download Crade

Still not fixed?

Connect the printer to the network directly instead of sharing it through a PC: most modern printers support Wi-Fi or Ethernet, and adding them by IP address (Add a printer using an IP address or hostname) avoids the Windows sharing path that causes 0x0000011b. In a company network, ask IT to check the print server's RPC and Group Policy settings rather than editing the registry yourself. If the printer maker offers a universal or updated Type 4 driver, installing it on both PCs often clears remaining failures.

Questions people ask

Is it safe to set RpcAuthnLevelPrivacyEnabled to 0?

It turns off the protection Microsoft added for vulnerability CVE-2021-1678, so remote print connections are less secure. On a trusted home network the risk is low. In offices, updating all devices and keeping the value at 1 is the recommended setup.

Do I change the registry on the host PC or the client PC?

On the PC that shares the printer (the host or print server). Microsoft's guidance places RpcAuthnLevelPrivacyEnabled on the server side, and many guides wrongly tell you to change it on the client, where it has no effect on this error.

Should I uninstall the Windows update that caused it?

Not as a long-term fix. The September 2021 enforcement is part of every later cumulative update, so removing one update only works until the next one installs. Use the registry value or the Local Port method instead.

Why does the error appear only on Windows 11?

Windows 11 version 22H2 and later use RPC over TCP for printer traffic between computers by default. If port 135 or the dynamic RPC ports are blocked, or the other machine only speaks Named Pipes, the connection fails with 0x0000011b.

Does 0x0000011b mean my printer is broken?

No. It is a Windows connection and authentication error between two computers. The printer normally still prints from the PC it is attached to.

Sources

Related errors