0x0000011B Error | Printer Fixes That Work Fast

You see this code when a PC tries to connect to a shared printer and Windows refuses the connection. It can pop up while adding the printer, during the first print job, or right after a Windows update. The good news is that most cases come down to one change in how Windows handles printer RPC authentication, so the fix is repeatable right now once you know where to apply it.

This guide keeps things on safe, real-world steps. You’ll start with quick checks, then move to the host-side fix that solves most shared-printer setups, and finish with fallbacks that avoid registry changes when that’s the better call for your setup.

What The 0x0000011B Error Means In Plain Terms

On many home and small-office networks, one Windows PC shares a USB printer to other PCs. When Microsoft tightened print spooler protections tied to CVE-2021-1678, Windows began requiring stronger RPC authentication for some shared-print paths. If the host and the client don’t line up on those rules, the client may fail with the 0x0000011b error during install or print.

Microsoft documents these printer RPC binding changes and the registry switch that controls them. In Windows 11, Microsoft also notes that some scenarios need extra SMB settings, depending on how the share is configured.

If you’re in a managed workplace, check whether there’s a print server or domain rules in play. If it’s just a few PCs sharing a printer, treat the “host PC” as the source of truth, since it controls the share and the spooler that remote clients talk to.

Fixing The 0x0000011B Error On Shared Printers

Most people try fixes on the client PC first because that’s where the error shows up. In this case, the host PC is usually the one that needs the change. Start by identifying the host, then confirm basic connectivity, then apply the host-side setting that brings the share back for many setups.

Identify The Host PC In Two Minutes

• Open Printer Properties — On a working PC, open the printer’s properties and note the “Share name” and “Computer name” listed for the shared path.
• Check The Share Path — Look for a format like \\HOSTNAME\PrinterShare so you know exactly which machine is publishing the printer.
• Confirm You Can Reach The Host — In the file browser, type \\HOSTNAME and confirm you can browse it without errors.

Run These Quick Checks Before Changing Anything

• Restart The Host And Printer — Power-cycle the printer, then restart the host PC to clear spooler hangs.
• Verify The Network Profile — Make sure the host is on a Private network profile, with file and printer sharing turned on.
• Try A Test Share — Share a simple folder from the host and confirm the client can open it.

If the folder share works but the printer share fails with the same code, you’re likely dealing with the RPC print rule change rather than a basic network issue.

If clients still can’t see the printer, verify that the host’s Print Spooler service is running and that File and Printer Sharing is allowed through the host firewall. A quick test is to open \\HOSTNAME from the client and load a shared folder, then retry the printer.

Host-Side Fix That Solves Most Cases

The most common fix is to change the RPC authentication privacy requirement on the host PC that shares the printer. Microsoft describes the registry value that controls this behavior, named RpcAuthnLevelPrivacyEnabled. Setting it to 0 on the host can restore compatibility for clients that fail to connect.

This is a tradeoff. Lowering the RPC privacy setting can reduce protection against certain spoofing scenarios tied to print spooler hardening. If the printer share is on a trusted home network, many people accept that risk. On business networks, prefer updating every device and keeping the stricter setting in place.

Set RpcAuthnLevelPrivacyEnabled On The Host

1. Create A Restore Point — Use System Protection to create a restore point so you can roll back if needed.
2. Open Registry Editor — Press Win + R, type regedit, then press Enter.
3. Go To The Print Path — Browse to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print.
4. Add The DWORD Value — Right-click in the right pane, choose New, then DWORD (32-bit) Value, and name it RpcAuthnLevelPrivacyEnabled.
5. Set The Value To 0 — Double-click the new entry and set Value data to 0, then click OK.
6. Restart The Spooler — Open Services, restart Print Spooler, then try connecting again from the client.

After this change, remove the printer from the client and add it again. If it connects cleanly, print a test page and a real document, since some failures show up only under load.

Keep The Host Updated On Purpose

• Install Pending Updates — Install Windows updates on the host so you’re not stuck on a half-patched state.
• Update The Printer Driver — Use the printer maker’s current driver or a stable inbox driver that matches the model.
• Reboot After Changes — Reboot the host once more after driver installs to clear old spooler sessions.

Client-Side Fixes When The Host Is Already Set

If the host-side setting is already in place and one or more clients still fail, shift to cleanup on the client PCs. A client can keep stale printer connections, cached credentials, or a mismatched driver that triggers the same connection failure message.

Clean Out The Old Connection

1. Remove The Printer — In Settings, remove the printer and delete any duplicate entries.
2. Clear The Print Queue — Open the printer queue and cancel any stuck jobs.
3. Restart Print Spooler — In Services, restart Print Spooler to release locked files.
4. Delete Driver Packages — In Print Management or Server Properties, remove unused printer drivers tied to that device.

Add The Share Again With A Clean Driver

• Connect Using The Share Path — Use \\HOSTNAME\PrinterShare and let Windows pull the driver.
• Pick A Matching Driver — If Windows asks, select the exact model driver already used on the host.
• Print A Test Page — Print from Printer Properties, then from a regular app like Notepad.

When the same code returns only on one client, compare Windows build and patch levels between a working client and the failing one. Aligning update levels can remove the mismatch that triggers the block.

Fix Login And Share Permissions Issues

• Remove Saved Credentials — Open Credential Manager, delete any saved entries for the host name, then reconnect to the share.
• Check Share Permissions — On the host, confirm the printer share allows the user account you’re using, not just “Everyone.”
• Try A Fresh User Test — Create a temporary local user on the client and connect once to rule out profile-specific settings.

On Windows 11, Microsoft notes that some printer-sharing setups rely on SMB guest access, which is off by default on newer builds. If your share depends on guest access, switch to a real username and password instead of forcing guest mode. It’s cleaner and it avoids opening a wider door on the network.

Workarounds That Avoid Registry Changes

Sometimes you don’t want to change the host RPC setting, or you can’t. In that case, you can still get printing back by changing the way the client connects. The goal is to avoid the exact remote spooler path that triggers the stricter RPC requirement.

Install The Shared Printer As A Local Printer With A Local Port

1. Open Classic Control Panel — Run control, then open Devices and Printers.
2. Add A Printer Manually — Choose Add a printer, then pick “The printer that I want isn’t listed.”
3. Select Local Printer — Choose “Add a local printer or network printer with manual settings.”
4. Create A Local Port — Select “Create a new port,” pick Local Port, then enter \\HOSTNAME\PrinterShare.
5. Choose The Driver — Select the correct model driver, then finish the wizard.

This method often works because the client treats the connection as a local port mapped to a UNC path. It can be a lifesaver on mixed networks with older printer drivers.

Switch To A Direct TCP/IP Port If The Printer Has Ethernet Or Wi-Fi

• Find The Printer IP — Print a network status page or check your router’s device list.
• Add A TCP/IP Printer — Add a printer by IP and let Windows create a Standard TCP/IP Port.
• Turn Off Sharing On The Host — If everyone prints direct to the device, the host share becomes optional.

Direct TCP/IP printing avoids the shared-spooler path. It can also reduce random “offline” states caused by a sleeping host PC.

Prevent The Error From Coming Back After Updates

Once you get printing working, lock in a stable setup so the next patch cycle doesn’t bring the same surprise. The exact right approach depends on whether the printer is shared from a personal PC, from a small office PC that stays on all day, or from a dedicated print server.

Keep All PCs On Similar Patch Levels

• Update The Host First — Patch the host, confirm printing, then patch the clients.
• Align Windows Versions — If one PC is far behind, bring it up to date before you chase printer tweaks.
• Re-test After Major Updates — After a feature update, re-add the printer if the driver stack changes.

Prefer A Print Server When Many PCs Share One Device

• Use A Dedicated Host — A small always-on PC or mini server keeps sharing stable and avoids sleep issues.
• Limit Driver Changes — Pick one driver package and stick with it across all clients.
• Document Your Setting — Write down whether RpcAuthnLevelPrivacyEnabled is set, so you can reapply it after reinstalls.

If you changed the host registry to fix this, revisit it later and test whether newer updates let you set it back to 1 without breaking printing. That gives you the stricter RPC behavior while keeping compatibility.

When you’re chasing a stubborn loop, note the pattern: if the printer fails only when added as a shared device, the shared path is the trigger. If it fails only on print, spooler or driver is the likely culprit. That mental model makes troubleshooting faster the next time the same office printer acts up.

For Microsoft’s latest guidance on print RPC changes and the related registry value, see the Microsoft article on managing deployment of printer RPC binding changes for CVE-2021-1678 and the Windows 11 RPC connection updates for print.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback