You are here


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.


See also: How to fix the Windows 0x0000011b network printing error

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer