{"id":21432,"date":"2021-09-18T19:20:23","date_gmt":"2021-09-18T17:20:23","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=21432"},"modified":"2021-09-18T19:20:23","modified_gmt":"2021-09-18T17:20:23","slug":"windows-printnightmare-microsoft-besttigt-probleme-nach-sept-2021-update","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2021\/09\/18\/windows-printnightmare-microsoft-besttigt-probleme-nach-sept-2021-update\/","title":{"rendered":"Windows PrintNightmare: Microsoft confirms printing problems after Sept. 2021 update"},"content":{"rendered":"

\"Windows\"[German<\/a>]For months, a number of vulnerabilities in the Windows Print Spooler service have existed in all versions of Windows, collectively known as PrintNightmare. Microsoft has been trying in vain to close the vulnerabilities completely since July 2021, but is having problems. The updates released for patchday on September 14, 2021 also cause problems, which Microsoft has now partially acknowledged. There is the advice to update the printer driver to be able to print again.<\/p>\n

<\/p>\n

The PrintNightmare vulnerabilities<\/h2>\n

\"\"Since early July 2021, vulnerabilities in the Windows Print Spooler have been public, allowing remote code execution (RCE) (seePoC for Windows print spooler vulnerability public, high RCE risk<\/a>). An attacker could execute arbitrary code with SYSTEM privileges. This includes installing programs, viewing, modifying or deleting data, or creating new accounts with full user privileges.<\/p>\n

As of patchday on September 14, 2021, there was another PrintNightmare fix, but it poses problems again. For example, printers on terminal servers or print servers can no longer print. I had already reported about the issue in the blog post Patchday Sept. 2021 Review: New PrintNightmare fix, new issues, new desaster?<\/a> <\/p>\n

Microsoft confirms the issues<\/h2>\n

As of September 17, 2021, Microsoft then acknowledged problems with printing in the Windows 10 status area<\/a> in the known issues section. The entry Administrator credentials required every time apps attempt to print<\/a> addresses the issue that the printer installation requires administrator credentials when printing. It states:<\/p>\n

\n

After installing KB5005033<\/a>  or a subsequent update, certain printers in some environments that use Point and Print may display the \"Trust this printer\" prompt. In addition, when an application attempts to print to a print server or a print client connects to a print server, administrator credentials are required for installation.<\/p>\n

This is caused by a printer driver on the print client and the print server using the same file name, but the server has a newer version of the file. When the print client connects to the print server, it finds a newer driver file and is prompted to update the drivers on the print client, but the file in the package it is offered for installation does not contain the newer file version.<\/p>\n<\/blockquote>\n

The following Windows clients and server variants are affected by this behavior – that is, all Windows versions that are still supported. <\/p>\n