Technical Anshu Home › Tutorials › Printer Error 0x0000011b
🖨️ Shared Printer Fix

Fix 0x0000011b Printer Error on Windows 10 & 11 – Quick & Easy Troubleshooting

"Windows cannot connect to the printer — operation failed with error 0x0000011b." This error started after the 2021 PrintNightmare security updates, when the PC sharing the printer and the PC connecting to it stopped agreeing on security. Here is the complete fix order, safest first.

✍️ Technical Anshu🖨️ Printer Sharing🎧 Multi-Language Audio
Fix 0x0000011b Printer Error on Windows 10 & 11 – Quick & Easy Troubleshooting
🎧 Multi-Language Audio: In the video player, click [Settings] (⚙️) ➔ [Audio track] to select your preferred audio.

📑Chapters

  1. What error 0x0000011b actually means — the PrintNightmare change behind it
  2. Restart both PCs and the Print Spooler service
  3. Update both the host PC and the client PC — the real fix
  4. Remove the shared printer completely and add it back cleanly
  5. Check the spooler service and clear stuck jobs on both ends
  6. Last resort — the RpcAuthnLevelPrivacyEnabled registry value on the host only
  7. Test print, and keep both PCs patched so it stays fixed

📋 Overview & Step-by-Step Guide

1

What Error 0x0000011b Actually Means

The message is "Windows cannot connect to the printer" with "Operation failed with error 0x0000011b". Nothing is wrong with the printer itself. In 2021, after the PrintNightmare vulnerability, Microsoft's security updates (starting with the September 2021 wave) raised the authentication privacy level Windows uses when one PC connects to a printer shared by another PC.

The error appears when the two PCs are on different patch levels: the updated PC demands the newer, more private RPC authentication, the unpatched PC does not answer the same way, and Windows refuses the connection with 0x0000011b. That is why a printer that worked for years suddenly stopped connecting right after an update — and why the fix is about matching the two PCs, not reinstalling the printer.

✅ Quick split test first: if EVERY PC in the office fails to connect, the problem sits on the host PC that shares the printer. If only ONE PC fails while others print fine, the problem is on that one client PC. Fix the side that is actually broken.
2

Restart Both PCs and the Print Spooler

Start with the simplest reset. Restart the host PC (the one the printer is attached to and shared from) and the client PC that shows the error. Then restart the Print Spooler service on both machines: press Win + R, run the command below, find Print Spooler in the list, right-click it and choose Restart.

Run
services.msc

A half-applied update or a spooler stuck mid-handshake clears at this stage more often than people expect. If the error is still there after both restarts, move on — do not keep restarting.

3

Update Both the Host and the Client — the Real Fix

This is the step that actually solves 0x0000011b, and the step most people skip: run Windows Update on both PCs until both are fully patched. The mismatch is the disease — an updated client talking to an unpatched host (or the other way round) is exactly the combination that produces this error.

Update the client PC first, restart it, then update the host PC — the one everyone forgets because "the printer is working on it locally". Local printing working proves nothing; the host's sharing side is what the updates changed. Once both PCs sit on the same patch level, try connecting to the shared printer again before touching anything else.

📌 In offices this is usually a patch-wave problem: one batch of PCs got updated, another batch did not, and the error appears "suddenly" the next morning. Bringing every PC to the same update level fixes the whole office at once, not just one desk.
4

Remove the Printer and Add It Back Cleanly

If both PCs are patched and the connection still fails, the client's stored connection and driver package are stale. Remove them completely instead of just deleting the printer icon. On the client PC, remove the printer from Settings, then open the Print Server Properties dialog with this command:

Run
printui /s /t2

In the Drivers tab, select the shared printer's driver and choose Remove → Remove driver and driver package, so no old driver files survive. Restart the PC, then add the printer again as a fresh connection (browse to the host PC, for example \\HOST-PC, and double-click the shared printer). A clean re-add forces Windows to renegotiate the connection under the new rules.

5

Check the Spooler and Clear Stuck Jobs

While you are in services.msc, confirm on both PCs that the Print Spooler service is Running and its Startup type is Automatic. A stopped or manual spooler on the host makes every client fail; a stopped spooler on the client makes only that desk fail.

Also open the printer queue on the host and cancel any stuck job sitting at the top — one jammed document blocks every job behind it and can look like a connection problem. If the spooler keeps crashing on its own, read that as a driver problem on that PC: remove and reinstall that printer's driver package (Step 4) rather than fighting the service.

6

Last Resort — the Registry Value on the Host

Only when a PC genuinely cannot be updated yet (an old host that must stay as it is for now), there is a documented bridge: on the host PC only, open Registry Editor and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print. Create a new DWORD (32-bit) Value named RpcAuthnLevelPrivacyEnabled and set it to 0. Then restart the Print Spooler service (or restart the host) and connect from the client again.

Setting this value to 0 tells the host not to enforce the raised RPC authentication privacy level for printer connections — the pre-patch behaviour — which lets the mismatched client connect.

⚠️ Understand what this reopens: this value switches OFF a protection Microsoft added in response to PrintNightmare. Treat it strictly as a temporary bridge on the host only — never on every PC — write down the date you set it, and remove the value (or set it back) as soon as the old PC is patched or replaced. The safe end state is always Step 3: both PCs updated, no registry bridge.
7

Test Print and Keep Both PCs Patched

Finish with a real test page from the client PC, not just a successful "printer added" message — 0x0000011b can hide until the first actual job is sent. Print once from the client, once locally on the host, and confirm both come out.

Then prevent the sequel: keep automatic updates on for both the host and the clients. This error is at heart an update-mismatch error, so the office rule is simple — PCs that share printers and PCs that connect to them should ride the same update wave.

🏷️Topic Search Variables & Keywords

🔍 0x0000011b 🔍 Printer Error 🔍 Windows Cannot Connect to the Printer 🔍 Shared Printer 🔍 PrintNightmare 🔍 RpcAuthnLevelPrivacyEnabled 🔍 Print Spooler 🔍 printui /s /t2 🔍 Windows 10 🔍 Windows 11 🔍 TechnicalAnshu 🔍 Printer Troubleshooting
🎙️ Full Transcript — tap to expand

Step-by-Step Troubleshooting Guide & Solutions - FIX 0x0000011b PRINTER ISSUE IT EXPERT GUIDE. On-screen demonstration by Technical Anshu....

Windows cannot connect to the printer, operation failed with error 0x0000011b. Why this shared printer error started after the 2021 PrintNightmare updates and the complete fix order, safest first.

(transcript ends here on the source page)

❓ Frequently Asked Questions

Is this tutorial 100% free to follow?

Yes! All guides and methods demonstrated by Technical Anshu use free, legal, and educational resources.

Can beginners follow this guide?

Absolutely! Every step is demonstrated on-screen with detailed instructions so anyone can follow along easily.

Where can I ask questions if I get stuck?

Leave a comment directly on the YouTube video, and our community and Technical Anshu will help you out.

🚀 Watch the Full Tutorial on YouTube

🚀 Watch the full step-by-step video tutorial on YouTube: https://www.youtube.com/watch?v=6M9TA_LrImY

Subscribe to Technical Anshu for IT support, Windows troubleshooting, and server management.

▶️ Watch Full Video
This tutorial is based on Technical Anshu's Fix 0x0000011b Printer Error video • Stuck on any step? Ask in the video comments — you will get help there 🙏