Alex Ruben
How To Resolve Printer Error KB5005565 When Accessing Shared Printer 0x0000011b
If you’ve been fighting with that annoying 0x0000011b error when trying to access a shared printer post-Windows update (KB5005565), you’re not alone. It’s one of those weird issues that pops up after a patch—like Windows decided to screw with the network permissions or something. Usually, it boils down to some registry setting or service hiccup, but the good news is, it’s fixable. This guide lays out some steps that kinda work in most setups I’ve seen. Expect to restore your printer access without too much chaos.
How to Fix Printer Error 0x0000011b in Windows 10 & 11
Open the Registry Editor safely
This part feels a bit sketchy because editing the registry is always a little risky—so backup first if possible. Basically, this is about tweaking a setting that Windows plays with after updates, which messes with the authentication stuff between your PC and the shared printer. If you’re seeing the error, chances are some registry key is blocking the connection.
- Hit Windows + S and type
regedit. Don’t worry, it’s just the registry editor. - Select it from the list, then click Yes when UAC asks if you really want to make changes.
Navigate to the right registry path
This is the part where Windows is a bit obtuse. The path involves several folders, but here’s the quick way to get there:
- In the Registry Editor, expand HKEY_LOCAL_MACHINE.
- Then go to System > CurrentControlSet > Control.
- Look for a folder named Printer. If you don’t see it, you might need to create or look around a bit more. On some systems, it’s under a different key, so don’t panic if it’s not exactly here.
Create a new DWORD to fix permissions
This is the part where the fix often hinges. The idea is to add or modify a value that controls how Windows handles printer sharing security. On some setups, the problem is caused because the authentication level is set weirdly, and changing this registry value tricks Windows into accepting the shared printer connection again.
- Right-click inside the right pane of the Printer folder and select New > DWORD (32-bit) Value.
- Name it
RpcAuthnLevelPrivacyEnabled. - Press Enter to save that name—sounds simple, but hey, it’s that registry tweak.
Adjust the value to zero
This part confuses some people because setting it to 0 often fixes the error by disabling certain encryption requirements that are, frankly, broken after the update.
- Double-click on
RpcAuthnLevelPrivacyEnabled. - In the Value data box, type
0. - Click OK and close the registry editor.
Restart the Print Spooler service
Because Windows really, really loves to be slow about applying registry changes, you gotta restart some services. The Print Spooler handles all your printing jobs, so restarting it helps clear out snags.
- Press Windows + R and type
services.mscthen hit Enter. - Find Print Spooler in the list. Double-click it.
- Set Startup type to Automatic, just in case it’s stuck otherwise.
- Click Stop if it’s running, then Start again. Or just click Restart if available. This can be weird in some versions—it’s hit or miss.
Final act: reboot and test
After all that, it’s tempting to just punch the computer and hope for the best—but actually, rebooting is the final step to get everything synchronized. Once back up, try printing again. Sometimes the fix is immediate, other times it takes a minute or two for the network to settle.
Extra Tips & Common Pitfalls
While not mandatory, a few extras can help prevent this mess from happening again:
- Make sure your printer drivers are up to date. The manufacturer’s website usually has the latest versions.
- Verify your network connection is solid—Wi-Fi drops can make sharing all kinds of fun errors.
- Check for new Windows updates—Microsoft might’ve already rolled out a fix for this in another patch, so don’t ignore updates.
Wrap-up
This registry tweak, combined with restarting the Print Spooler, tends to fix that pesky 0x0000011b error pretty reliably. It’s kinda weird that Microsoft broke this in the first place, but hey, at least now there’s a workaround. Sometimes, it’s just a matter of waiting for them to push out a real fix, but for now, this should get your shared printer back to life.
Frequently Asked Questions
What is the 0x0000011b error?
It’s mostly a communication hiccup—think of it like Windows refusing to talk to a shared printer because some security setting got borked after the last update. Not that complicated, but enough to drive someone nuts.
Can I fix this without editing the registry?
Sometimes, restarting the Print Spooler or updating drivers helps, but the registry tweak is the most common fix. Honestly, it’s worth trying that first because it addresses the root security setting issue directly.
What if this method doesn’t work for me?
Then you might need to look at your network sharing settings, make sure the printer driver is compatible, or reinstall the printer entirely. Sometimes, a fresh driver install from the manufacturer’s site does the trick.
- Fingers crossed this helps—worked for me on a few different setups, so give it a shot.