You are here
0x0000011b
![](http://bet.whitemiceconsulting.com/sites/whitemiceconsulting.com/files/styles/large/public/field/image/Screenshot%20from%202021-10-05%2008-28-32.png?itok=FBEemzwA)
KB5005573 broke our M$-Windows due to Windows' broken printing subsystem and Microsoft's refusal to migrate to Open solutions such as IPP & cupsd. Suddenly M$-Windows clients were failing to connect to printers with an extremely helpful and illuminating error code of 0x0000011b.
This relates to a fix Microsoft released in yet another attempt to close cavernous security holes in SPOOLSS (the Windows printing subsystem - since they don't use cupsd); this week the security issue in question is the aptly named "PrintNightmare"
Setting a registry key on our M$-Windows print server allowed clients to print again. Importantly it does this by disabling the fix related to "PrintNightmare"; on the other hand it allows Windows printing to work.
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print]
"RpcAuthnLevelPrivacyEnabled"=dword:00000000
See also: How to fix the Windows 0x0000011b network printing error