0x00000b11 Printer Error
Nettie Vitale
If you start getting error code 0x0000011b after installing the latest Windows updates, uninstall them and see if that helps. Many Windows 11 users confirmed that uninstalling KBKB5005565 and KB5005568 resolved the issue. Here is the guide:
After reading this post, you may know how to fix printer error 0x0000011b. Is this article helpful to you? And if you have other solutions to the problem, you can share them with us in the following comment zone.
I have tried to add multiple network printers (that can be added to other computers on the network but can't be added to mine) and always get error code 0x0000011b. I have removed all conflicting drivers, tried all printer troubleshooters on both computers, restarted print spooler services, and the computers of course.
What a nightmare! All our MDM workstation users began to hate Microsoft for this Onprem Printserver, I've added the DWORD key and set to 0, waiting to reboot the server. Will come back and report you.
Sharing printer is quite common for both working and home environments. However, there are many issue reports on shared printers from the year 2021, and the error goes Operation Failed with Error 0x0000011b. By this article posts, Microsoft hasn't released an overall fix for this issue. This article introduces some proven effective fixes.
This issue is about a printer connecting error. And it happens when a PC connects to a shared printer on another PC, which stops the printing needs. However, the shared printer shows up on the remote PC and seems OK to be connected. It may also appear when trying to download the printer driver. And both Windows 10 and 11 have such an issue.
The security patches Microsoft released to protect Windows 10 and 11 from Windows Print Spooler Spoofing caused vulnerability in remote code. And the involved patches are KB5005565 and KB5005568. These patches affected the remote connection to a printer via a shared network and asked for an admin right.
For the spotted root reason, there are several temporary fixes approved effective to settle this problem. A quick solution is to allow administrative users to install the printer driver. Or you can reverse the Windows Print Spooler Spoofing patch default setting by disabling them. Below are the detailed steps for these two methods.
Method 1: Install the printer driver again without admin
As mentioned above, when the 0x0000011b error occurred, printing is only allowed with admin rights connection to the target printer. To change this registry key needs to be edited. Follow the steps below for this:
Another method is to remove the newly updated patches and eliminate the change but leave with the vulnerability these patches mean to cover. However, this can be the worry-free fix for this issue until Microsoft release an official solution.
A new security patch released by Microsoft may have caused printers shared over the network to malfunction, resulting in the operation failed 0x0000011B error. The error has primarily affected Windows 10 21H1 build running computers. However, you may also experience it on Windows 11 systems.
Your newly added printer will now appear under Device and Printer in Control Panel and the Settings app. Give a new print job to see if the error is resolved.
The problematic security update included a security fix to patch the Printer Spooler Spoofing vulnerability dubbed CVE-2021-1678. However, the new changes seem to have triggered the 0x0000011B operation failed error.
Assuming the issue is triggered after you installed a Windows security update, uninstalling the update should undo the changes and fix the error. You can uninstall some individual updates from the Windows updates section. This feature is specifically available to undo issues that may have occurred after installing an update.
Note that the concerned update (KB5005565) was released to fix a print spooler vulnerability on Windows OS. Uninstalling the update can leave your computer vulnerable again. Use this as a last resort if none of the above methods helped resolve the error.
This error has largely affected Windows 10 computers. To fix the issue, try to install all the pending Windows updates that may include a hotfix. You can also add the printer manually to a local port or edit the registry entry to disable the problematic setting. If nothing works, uninstalling the security update may be the last resort. However, doing so can put your computer at risk of print spooler spoofing vulnerability.
Similar issue in domain environment, Print server MS Windows 2016 Core, clients Windows 10.
Printers can't be connected, set as default or installed on client machine/
Removing KB5005573 from printserver solved our problem.
Isso resolveu o problema que tive em um cliente. Servidor de impresso est em um Windows Server 2016. Ontem de manh a atualizao foi instalada. Desinstalei, reiniciei o servidor e a atualizao j estava sendo baixada novamente. Deixei o servio do Windows Update desativado, pelo menos at ter certeza que uma atualizao nova seja capaz de resolver esses problemas.
Hi
Uninstalling KB5005573 on all the computers has resolved the problem.
All computers are now printing on my Wife's Network Computer
But what will happen on the next update. And would like to see an official repair from windows
Check workstations and make sure they are FULLY up-to-date to Windows10 21H1 feature update. After reboot of station, printing returns to normal without removing the major security update from the server.
removing all those updates? VERY bad call unless you like viruses and ransomware. Removing these will open a number of holes and make your systems vulnerable to attack.
look for options that don't roll back to the past. Updates are used to move forward and improve the devices. I will get off my soapbox now. LOL
Yes, you are right, removing any fthe update is not a good idea unless you don't have any other options. However, if people can wait for an official fix for this then I would really recommend that instead of messing more with their Windows files.
We had a similar problem in the domain environment, MS Windows 2012 R2 print server, after the KB5005613 package one of the stations with windows 7.0 simply not, it was no longer possible to print to the shared printer on that server. Removed the package, fixed the problem, thanks for the tip, regards!
I recently started getting this error on both of my Windows 11 Pro machines while trying to connect to a shared printers on the machines. Both machines have all updates installed. I am able to connect to files but not the printers. None of the solutions posted have worked included the registry changes. The only updates I can uninstall are show in the attached file. None of them are the ones suggested to uninstall. Both printers are HP. One is a Lasrjet and one is a Photosmart. Both are attached to USB ports on their respective machines. When I click on them from the desktop network I can I can see the printer but cannot connect to it without getting the 11b error. I can install each of them on the other machine locally so the print drivers appear to be correct. File sharing works but not printer sharing. Suggests please as i have run out of options
Buna ziua,
Acelasi lucru am patit si eu intr-o retea de calculatoare... dezinstalatii ultimele update de securitate, sunt doar 2 ... mai exact, de pe data de 16 ian 2022 si pana astazi 19 ian 2022 si apoi va functiona sigur...
Those updates do not appear either on Win 10 host or Win 11 pro client computer. I have tried all the group edit and registry hacks on the internet to no avail. Cannot install a printer wired to a host computer to a Win 11 client computer?
When the Registry DWORD is set to RpcAuthnLevelPrivacyEnabled=1, Windows encrypts RPC communication with network printers and/or print servers. Performing the above is much faster than uninstalling the KB that was applied.
This was causing us serious headache. This resolved our issue. FYI for others for us I only had to make changes the reg changes on the Print Server, on the client side the reg changes didn't make a difference. Client printing worked back to normal once the server reg changes were made to "0" and restarted Print Spooler Service.
Fixed the issue for me. Domain joined computers with Print servers were W10 with KB5005565 applied. Clients were W7Pro. Adding DWORD reg value RpcAuthnLevelPrivacyEnabled=0 as described and restarting the print spooler fixed the issue immediately.
Thank you, this registry key restored printer install and the spooler for existing connections. I was then able to 'Add a printer' on a Windows 7 client, also in a common workgroup.
The printer is attached to a Windows 10 Home machine, acts as the server for the Shared print device. I added this registry key ONLY to the windows 10 host.
Other Windows 10 and Windows 7 machines inside the private LAN attaching to the shared printer/scanner did not require the registry change.
That is not an accurate assessment. Setting the registry key RpcAuthnLevelPrivacyEnabled to 0 only disables the encryption of RPC communications between the print server and the client which was enabled by default by a Windows Server update by way of creating this registry key and setting its value to 1 if it did not exist (thus causing all the issues with printing that people experienced if the administrator of the print server didn't happen to preemptively create this registry key and set its value to to 0 instead).
The encryption was only set in place as a workaround to address CVE-2021-1678 (see -guide/vulnerability/CVE-2021-1678 ) which was only a proof concept vulnerability that involved Windows Print Spooler Spoofing. The only risk you face by disabling this feature is that someone might figure out the undisclosed details as to how this vulnerability works and use it to spoof a shared printer on a print server on your network to either block people's access to the real printer or to surreptitiously spy on and copy data sent to those same printers.
4a15465005