How to Fix Windows Error 0x0000011B

Some users of Windows are experiencing the error 0x0000011b every time they try to print something using a network shared printer. This problem started occurring after Microsoft released the latest security update. The problem continues in Windows 10 and Windows 11.

After investigating this issue further, it turns out that the problem is due to a series of security patches that Microsoft implemented to protect Windows 10 and Windows 11 users from a vulnerability involving Windows Print Queue spoofing.

However, when Microsoft released the final patch to put a nail in the coffin for this vulnerability (on September 14), it also produced a different problem 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 problem. It is actually a registry value called RpcAuthnLevelPrivacyEnabled which will be located in the following location: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print

After this change was applied as the default behavior for all Windows devices, this printing error started affecting primarily small businesses and home networks that are not configured to use a Kerberos configuration in a Windows domain.

If you or your organization are affected by the error 0x0000011b, there are different methods you can try to fix it:

• Install the hotfix provided by Microsoft: While there is currently no suitable solution available, by the time you read this article, Microsoft may release a hotfix that patches these two vulnerabilities without causing any unintended consequences. With this in mind, we recommend that you start by installing all pending updates.
• Uninstall the problematic security update:Uninstalling the Windows security update that caused the problem in the first place will fix the 0x0000011b error, but it is not the ideal way to fix the problem because your network will still be vulnerable to PrintNightmare and MSHTML, the two vulnerabilities that Microsoft wants you to protect against.
• Disable migration for CVE-2021-1678: The best method to deal with this particular issue (at least until Microsoft fixes the effects of the security patch) is to disable migration for CVE-2021-1678. This will ensure that your network is not exposed to the two vulnerabilities while resolving the 0x0000011b error.

How to fix error 0x0000011b

Now that you are familiar with the cause and fixes for the 0x0000011b, Let's get our hands a little dirty and apply ourselves to solving the problem once and for all.

Install all pending updates

If there are still pending updates on your Windows 10 or Windows 11 PC that are waiting to be installed, our recommendation is to start by making sure you're taking advantage of the latest fixes.

Microsoft has already confirmed that they are working on a patch that will stop the 0x0000011b, but that solution has not yet arrived for Windows 10 or Windows 11.

But when it does arrive, it will likely arrive via a WU cumulative update. And in its usual fashion, Microsoft will likely start rolling it out unannounced to certain segments of Windows users; when that happens, we likely won't be able to update this article fast enough.

With this in mind, please follow the instructions below to install all pending updates in order to install the hotfix for the 0x0000011b:

• Press the Windows key + R to open the dialog box Run. Inside the text box, type 'ms-settings: windowsupdate' and press Log in to open the page Windows Update from the Settings menu.

Nota: This command works on Windows 10 and Windows 11.

• Once you are inside the Windows Update screen, go to the right side menu and click on download now if new updates are available.

Nota: If there are no pending updates to install, click Search for updates to trigger an analysis.

• Wait until all pending updates are installed, then restart your PC and wait until the next startup is complete.
• After your Windows 10 or Windows 11 computer restarts, simply repeat the action that was previously causing the 0x0000011b.

If the issue is still not resolved or the Microsoft fix has not arrived yet, continue to the next potential fix below.

Disable CVE-2021-1678 mitigation

As of now (assuming Microsoft hasn't already 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 as it will fix the issue when trying to use a network connected printer and will also ensure that you are not exposed to any network vulnerabilities. PrintNightmare y MSHTML.

What you will need to do is use the Registry Editor (present in Windows 10 and Windows 11) to create a new 32-bit DWORD called RpcAuthnLevelPrivacyEnabled and set its value to 0 (this will completely disable CVE-2021-1678 mitigation).

If you are looking for specific step-by-step instructions on how to do this, please follow the steps below:

Nota: The instructions below are identical regardless of whether you are using Windows 10 or Windows 11.

• Press the Windows key + R to open a dialog box Run Then write 'regedit' inside the text box and press Ctrl + Shift + Enter to open the Editor of the Register with administrative privileges.
• Once you are prompted for the message, User account control, click Yes to grant administrative privileges.

Once you are finally inside the Registry Editor, use the menu on the left to navigate to the following location:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print

Nota: You can navigate to this location manually (by clicking each key) or you can paste the full path into the navigation bar at the top and press Enter to get there instantly.

• After you manage to enter the correct location, make sure that the key Print is selected, then move to the right section, right-click on an empty space and select New > 32-bit DWORD Value.

• Next, name the newly created registry value as RpcAuthnLevelPrivacyEnabled and press Log in To save the changes.
• Finally, double-click on the value RpcAuthnLevelPrivacyEnabled newly created.
• Once you are inside the menu Edit, establishes the Base en Hexadecimal and  Facts & figures of the value en 0 before clicking Accept To save the changes.

• After this modification is complete, restart your PC and repeat the action that was previously causing the 0x0000011b.

If the problem is still not solved, try the next solution below.

Uninstall the problematic update (KB5005565)

If you want to remove the root of the problem, the only way to do so is by uninstalling the problematic update that caused the problem in the first place KB5005565.

However, our recommendation is to avoid this resolution (if possible), as uninstalling KB5005565 will also mean that your PC will remain vulnerable to the two vulnerabilities that this security update was intended to protect it from. (PrintNightmare y MSHTML).

If you decide to go with this method, think of this solution as temporary—the problem will most likely be fixed with a cumulative update for Windows 10 or Windows 11.

But until then, you can rest assured that the error 0x0000011b stop happening when you try to use your home or network printer by accessing the Windows Update history and uninstalling the Security Update for Microsoft Windows (KB5005565) for the entire working group.

Follow the instructions below for step-by-step instructions on how to do it:

Nota: The instructions below are universal and will work regardless of the operating system you are using.

• Press the key Windows + R to open a dialog box Run. Then type 'appwiz.cpl' inside the text box and press Log in to open the menu Programs and features.

Nota: If the message of User account control If it asks you, click on Yes to grant administrative privileges.

• Once you are inside the menu Programs and features, you have to click on View installed updates in the menu on the left.

• If you are prompted to grant administrative privileges once again, do so by clicking the button Yes.
• After you manage to enter the Installed Updates tab, review all the installed updates and look for the update KB5005565.
• After you manage to locate it, right click on it and select uninstall in the context menu that just appeared.

• In the next message, click Yes to confirm the uninstallation of the problematic security update.
• Once the uninstallation is complete, restart your PC and see if the problem is resolved once the next startup is complete.

This way, you will be able to put an end to this error. I hope that our guide will be very useful for you. See you in a future post, until then.