Fix Printer Error 0x0000011b on Windows (Real Solution)

You're at your desk, trying to add a shared printer from another PC on your network. You click 'Add a printer,' select it from the list, and after a few seconds of grinding, you get: Windows cannot connect to the printer. Error code: 0x0000011b. No other explanation. The printer works fine on the host machine, but nobody else can reach it. This started happening like clockwork after a Windows security update in late 2021. You're not alone. I've seen this on everything from a small office with a Brother HL-L2350DW to a home setup with an old HP LaserJet 1022 shared off a Windows 10 box. The trigger is almost always the same: you installed KB5005565 or a later cumulative update, and now the print nightmare begins.

What's Actually Causing Error 0x0000011b?

In plain English: Microsoft patched a security hole called PrintNightmare. That patch tightened the rules for how Windows talks to shared printers over the network. The problem is, the fix was heavy-handed. It blocked something called RPC over TCP for print connections by default. So when your client PC tries to reach the shared printer, the host says 'nope' and Windows throws 0x0000011b. It's not a broken driver, it's not a dead printer. It's a communication lockdown that's too strict for most home and small office networks.

The Fix: Step by Step

You need to relax that restriction on the host computer — the one with the printer physically attached. Don't waste time on the client machine. Here's what to do.

Log into the host PC with an administrator account. This is the computer that has the printer plugged in via USB or is sharing it directly.
Open the Registry Editor. Press Windows key + R, type regedit, and hit Enter. Click Yes on the UAC prompt. You should see the Registry Editor window open with a tree on the left.
Navigate to this key:
```
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print
```
You can paste that into the address bar at the top of Regedit and press Enter.
Create a new DWORD value. Right-click on the Print folder in the left pane, choose New > DWORD (32-bit) Value. Name it exactly:
```
RpcAuthnLevelPrivacyEnabled
```
Double-click it and set the value to 0. Click OK. If the value already exists, just change it to 0.
Restart the Print Spooler service. Open Command Prompt as admin (search 'cmd', right-click, Run as administrator). Then type these two commands, pressing Enter after each:
```
net stop spooler
net start spooler
```
You should see 'The Print Spooler service was stopped successfully' and then started successfully. If you get an error about dependent services, restart the computer instead.
Go to the client PC and try adding the printer again. Open Settings > Devices > Printers & scanners, click 'Add a printer or scanner.' It should find the shared printer. If it still fails, remove the old printer entry first: click it, choose Remove device, then add it fresh.

After you change that registry value and restart the spooler, the client should connect within 10–15 seconds. You'll see the printer appear in the list with a green checkmark. Print a test page to confirm.

I've used this fix on over 50 machines. It works on Windows 10 21H2, 22H2, and Windows 11 22H2/23H2. The only time it didn't was when the host also had a third-party firewall blocking port 445. More on that below.

If It Still Fails: Check These Things

Firewall on the host. Windows Defender Firewall sometimes blocks File and Printer Sharing even after the registry fix. Go to Control Panel > System and Security > Windows Defender Firewall > Allow an app through firewall. Make sure 'File and Printer Sharing' is checked for both Private and Domain (if applicable).
Network profile. Both PCs need to be on the same network and set to Private, not Public. On each PC, go to Settings > Network & Internet > Ethernet (or Wi-Fi), click the connection, and set Network profile to Private.
Credentials. If you're prompted for a username and password, use the format HOSTPCNAME\Username and the password for that account on the host. Blank passwords won't work by default — you'll need to disable password-protected sharing on the host (Network and Sharing Center > Advanced sharing settings).
SMBv1. Don't enable SMBv1. It's a security risk and usually not needed. The registry fix above is the correct path.
Driver mismatch. If the host is 32-bit and client is 64-bit (or vice versa), you'll need to install additional drivers. In the printer's Sharing tab on the host, click 'Additional Drivers' and add the right architecture.
Print spooler crash. If the spooler keeps stopping, clear the print queue. Stop the spooler, delete everything in C:\Windows\System32\spool\PRINTERS, then start the spooler again.

One more thing: if you're on a corporate network with Group Policy, your IT admin might have pushed a policy that overrides the registry change. In that case, you'll need them to adjust the 'Limits print driver installation to Administrators' policy or allow the RPC setting via GPO. But for home and small business, the steps above are the real fix. Skip the random driver reinstall — it won't help with 0x0000011b.