The problem affects all Windows clients from Windows 7 SP1 to Windows 10 21H1, as well as the respective server pedants. Additionally, clients can still be modified manually to adopt desired printer settings.
Workaround: IT administrators with admin privileges can still install printer drivers on the client through other means, such as copying packaged drivers from a known good package location. The printing environments affected by this issue are more commonly found in enterprises and organizations.
Note: The printer connection methods described in this issue are not commonly used by devices designed for home use. Servers which use default print settings and have no custom settings to provide to clients are unaffected. Clients who have previously received the settings package prior to the installation of KB5005611 are unaffected. Clients which receive this data file will not be able to use the file content and will instead proceed with default printing settings. This issue results from an improper building of the data file which contains the printer properties. This issue will not cause printing operations to fail, however, custom settings defined on the server – for example, duplex print settings – will not be applied automatically, and clients will print with default settings only. Note this issue is specific to print servers and does not impact standard network printing. The article Custom printing properties might not be correctly provided to print server clients states:Īfter installing KB5005611 on a print server, printing properties defined on that server might not be correctly provided to clients. Microsoft has just confirmed certain printing problems in the Windows status area in various Know-Issues sections. The registry entries listed in the blog post Windows PrintNightmare: Status, issues and workarounds (Sept. Maybe this helps someone – although the exchange of DLLs in enterprise environments is rather not so yellow of the egg. Note, that the initial script has been updates, see the whole forum thread linked above You have to adjust the "icacls" line in the script for a German Windows and use "administrators" instead of "builtin\administrators". In the Bleeping Computer forum you can find a script to easily replace the DLL.
So far the only workaround is to uninstall the update completely or to replace the win32spl.dll in the System32 folder with an older one (for example with the September version 1.1237. Blog reader Marco points out in this comment that according to his experience it currently only affects computers in workgroups without Actice Directory integration.
The problem is confirmed by other readers. Uninstalled the update and the connection worked immediately :) Has anyone had problems with network printers installed on a server after the KB5006670 update? Printers could not be reinstalled because they were asked for credentials. German reader Liam addressed the issue in this comment: Oktober 2021) (here is the English version: Patchday: Windows 10-Updates (October 12, 2021)), there were also a number of other feedbacks about printing problems. On my German blog post Patchday: Windows 10-Updates (12. Blog reader Christian addressed it in this comment: Kb5006670 installed on clients causes inability to print from a server.
Update KB5006670 for Windows 10 version 2004 through 21H1 breaks the ability to print from a client to a Windows server. Windows updates from Octolead to new printing problems for some users. Printing issues after October 2021 update