After investigating this issue thoroughly, it turns out that the issue is occurring due to a series of security patches that Microsoft pushed in order to protect Windows 10 and Windows 11 users from a vulnerability involving the Windows Print Spooler Spoofing. However, when Microsoft released the final patch to put a nail in the coffin of this vulnerability (on September 14th), it also produced a different issue by interfering with the TPC authentication level for network printers. As of now, affected users have been able to get to the root of this issue. It’s actually a registry value called RpcAuthnLevelPrivacyEnabled that will be found in the following location: After this change has been enforced as the default behavior for every Windows device, this printing error started affected mainly small businesses and home networks that are not set up to use a Kerberos setup on a Windows domain. If you or your organization are affected by the 0x0000011b error, there are several different ways that you can use to deal with the issue: Now that you are familiar with the cause and the fixes for the 0x0000011b, let’s get our hands dirty and apply them in order to resolve the issue for good. Note: All the fixes below will work for both Windows 10 and Windows 11.
Install every pending update
If there are still pending updates on your Windows 10 or Windows 11 computer that are waiting to get installed, our recommendation is to start by making sure that you’re taking advantage of the latest hotfixes. Microsoft has already confirmed that they’re working on a hotfix that will put a stop to the 0x0000011b, but that fix has not arrived yet for Windows 10 or Windows 11. But when it comes, it will likely arrive through a WU Cumulative update. And in their usual fashion, Microsoft will likely start deploying it unannounced to certain segments of Windows users – when this happens, we’ll likely not be able to update this article fast enough. With this in mind, follow the instructions below to install every pending update in order to install the hotfix for the 0x0000011b: If the problem is still not fixed or the Microsoft fix has still not arrived, move down to the next potential fix below.
Install the local printer driver for the local port
Once you’ve ensured that you’re running on the latest Windows Updates available for your Windows version, the most efficient way of avoiding the 0x0000011b error while remaining protected against the PrintNightmare and MSHTML vulnerabilities is to add the printer that’s giving you issues to the local port. This method was confirmed to work by a lot of users facing this error while attempting to connect their low-end network printer. You can enforce this fix by accessing the classic control panel interface and add a new printer (using local port drivers) from the Device and Printers screen. For step by step instructions on how to do this, follow the instructions below: In case the issue is still not yet fixed, move down to the next potential fix below.
Disable CVE-2021-1678 mitigation
As of now (assuming that Microsoft has not yet rectified the issue via a hotfix) is to disable the CVE-2021-1678 mitigation, reverting the change that produced the 0x0000011b error in the first place. This method is the best of both worlds since it will fix the issue when attempting to use a network-connected printer and it will also ensure that you are not left exposed to the PrintNightmare and MSHTML vulnerabilities. What you’ll need to do is use the Registry Editor (present on Windows 10 and Windows 11) to create a new 32-bit DWORD named RpcAuthnLevelPrivacyEnabled and set its value to 0 (this will completely disable the CVE-2021-1678 mitigation). If you’re looking for specific step by step instructions on how to do this, follow the instructions below: Note: The instructions below are identical regardless if you’re on Windows 10 or Windows 11. If the problem is still not fixed, move down to the final potential fix below.
Uninstall the problematic update (KB5005565)
If you want to cut the root of the issue, the only way to do it is by uninstalling the problematic update that brought the issue in the first place KB5005565. However, our recommendation is to avoid this resolution (if possible), since uninstalling the KB5005565 will also mean that your PC will still be vulnerable to the two vulnerabilities that this security update was meant to protect you from (PrintNightmare and MSHTML). If you decide to go for this method, think of this fix as transitory – most likely, the issue will be rectified by a cumulative update for Windows 10 or Windows 11. But until then, you can ensure that the 0x0000011b error stops occurring when you attempt to use your home or network printer by accessing the Windows Update history and uninstall the Security Update for Microsoft Windows (KB5005565) for the entire workgroup. Follow the instructions below for step by step instructions on how to do so: Note: The instructions below are universal and will work regardless if you’re using Windows 10 and Windows 11.
How to Connect MG3620 wirelessly using Printers Control PanelHow to Fix ‘Error Code 0xf1’ on Epson PrintersHow to Fix “Error Code 0xC4EB827F” on HP Printers?How to Fix Error Code: B200 on Canon Printers?
