[German]Since the release of the October 12, 2021 security updates, administrators have been complaining about network printing issues. Administrative permissions are required for every print operation – I had reported. Now Microsoft has confirmed this issue, but released the whole thing for Windows 11, although it affects Windows 7 through Windows 11 and the server counterparts.
Confirmation of printing issues
It's the statment Receiving a prompt for administrative credentials every time you attempt to print, that Microsoft has posted in the Windows 11 status area under Known Issues. There Microsoft writes:
You might receive a prompt for administrative credentials every time you attempt to print in environments in which the print server and print client are in different times zones.
Microsoft points out that this only affects network environments with print servers, not consumer systems with directly connected printers. The print environments affected by this problem are more likely to be found in businesses and organizations, it says. The problem affects the following systems:
- Client: Windows 11, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1.
- Server: Windows Server 2022; Windows Server, version 20H2; Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2.
The issue is confirmed with a date of October 15, 2021. Microsoft writes that they are working on a solution and assume that a solution will be available by the end of October.
Yesterday I wrote an article for German site heise about printing issues in network environments. In this context, I was confronted by my editor about the fact that Microsoft says the printing problem is solved. On the status page for Windows 10 21H1, there is the post here that deals with the requested administrator permissions when printing. Following screenshot shows that there the issue is listed as "Resolved with KB5006670". But the case was opened on October 15, 2021, which is after the updates were released on October 12, 2021 (see screenshot below).
Either this is an error in the documentation, or the left hand at Microsoft no longer knows what the right hand is writing. However, the stated solution This issue was resolved in KB5006670 contradicts the above statement and what administrators in the field experience on a daily basis.
Note: German blog reader Wolfgang S. just posted in this comment an interesting observation about the behavior of Windows print jobs when the October Update is installed. Since the October update, spoolsv.exe apparently wants NTLM authentications again, which are rejected. Something has obviously changed.
Workarounds here in the blog
I had already outlined the problem on October 14, 2021 in the blog post Windows October 2021 Updates: PrintNightmare Status and Network Printing Issues. In this context, it turned out – also based on user feedback – that the workarounds described in the article Windows PrintNightmare: Status, issues and workarounds (Sept. 22, 2021) can help to disable the restrictions. In particular, the comments by German readers Andreas H and Marco are enlightening:
we have our group policies set up as in this post (also linked here on the blog before) and no more problems with admin credentials on a network printer installation.
Article by Mark Heitbrink: PrintNightmare – 3 Richtlinien werden benötigt (German)
By the way, if the admin credentials are requested during the installation, the installation does not fail at all, the printer is already installed successfully, but unfortunately only in the admin profile :-)
Goth readers state that Mark Heitbrink's three policies addressed within the above linked German post PrintNightmare – 3 Richtlinien werden benötigt would have solved the printing problem with network printers (I had touched on it in the post Windows: PrintNightmare wrap-up and status (August 28, 2021)). Maybe it will help.
PoC for Windows print spooler vulnerability public, high RCE risk
Windows Print Spooler Vulnerability (CVE-2021-1675, PrintNightmare) Confirmed by MS; CISA Warns
0Patch Micropatches for PrintNightmare Vulnerability (CVE-2021-34527)
Out-of-Band Update closes Windows PrintNightmare Vulnerability (July 6, 2021)
PrintNightmare out-of-band update also for Windows Server 2012 and 2016 (July 7, 2021)
The Chaos PrintNightmare Emergency Update (July 6/7, 2021)
Windows 10: Microsoft fixes Zebra & Dymo printer issues caused by update (e.g. KB5004945) via KIR
Microsoft on PrintNightmare vulnerability CVE-2021-34527: Windows is secure after patch
Patchday: Windows 10-Updates (July 13, 2021)
Patchday: Windows 8.1/Server 2012-Updates (July 13, 2021)
Patchday: Updates für Windows 7/Server 2008 R2 (July 13, 2021)
Windows vulnerability PrintNightmare: It's not over yet (July 15, 2021)
Microsoft Defender for Identity can detect PrintNightmare attacks
PrintNightmare: Point-and-Print allows installation of arbitrary files
0patch fix for new Windows PrintNightmare 0-day vulnerability (Aug. 5, 2021)
Windows PrintNightmare, next round with CVE-2021-36958
Ransomware gang uses PrintNightmare to attack Windows servers
Vice Society: 2. Ransomware gang uses Windows PrintNightmare vulnerability for attacks
Microsoft shows a "slim foot" with PrintNightmare
Windows: PrintNightmare wrap-up and status (August 28, 2021)
Patchday Sept. 2021 Review: New PrintNightmare fix, new issues, new desaster?
Windows PrintNightmare: Microsoft confirms printing problems after Sept. 2021 update
Windows September 2021 Update: Workaround for some printing issues
Windows PrintNightmare: Status, issues and workarounds (Sept. 22, 2021)
Tip: Windows PrintNightmare test tools for administrators
Windows October 2021 Updates: PrintNightmare Status and Network Printing Issues
Cookies helps to fund this blog: Cookie settings