Windows PrintNightmare status Nov. 1, 2021 (KB5006674, KB5006670)

Windows[German]It's November 1, 2021, and the question arises about the status of printing problems in Windows. After all, Microsoft has been patching the PrintNightmare vulnerability since summer, but keeps creating new problems. Even in early Nov. 2021, the printing problems have not been fixed.


Advertising

I blogged already on the printing issues associated with PrintNightmare here in the blog. Private users and business users who operate their printers on the USB port of a client are not affected by the problems. But administrators running Internet and network printers are panting after the printing problems caused by security updates.

Microsoft had indeed released preview updates in October 2021 to fix printing issues (see, for example, the Windows 10 V2004-21H1 Preview Update (2021/10/26) blog post). But feedback from readers revealed a mixed picture. EP left the following comment:

Unfortunately guenni, some network printing issues still persist even with KB5006738 installed – saw one of the recent comments from this recent bleepingcomputer article, that points to this reddit thread.

just recently installed KB5006738 to a Toshiba laptop running Win10 home 21H1 – can't reliably print to my HP envy photo 7858 printer thru a wireless network connection but prints fine thru a local usb cable connection. not a good outlook for MS

Also coincides with comments from German users, who still reported problems. And the colleagues from Bleeping Computer have come across that Microsoft confirms printing problems with the updates KB5006674 and KB5006670.

Microsoft confirms printing issues

Microsoft has confirmed the printing issues due to the October 12, 2021 updates for Windows 11 KB5006674 and Windows 10 KB5006670. The support posts say that some of the printing issues have been fixed by further updates. But the following problem remains:

After installing this update Windows may experience the following errors when connecting to a remote printer that is shared on a Windows server:

  • 0x000006e4 (RPC_S_CANNOT_SUPPORT)
  • 0x0000007c (ERROR_INVALID_LEVEL)
  • 0x00000709 (ERROR_INVALID_PRINTER_NAME)

Microsoft is investigating the issues. This affects the following systems:


Advertising

  • 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, version 1607; 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 2008 SP2

In the status area of Windows 11 also four printing problems with date 21 Oct 2021 are described. The colleagues from Deskmodder have posted another workaround, where I don't know if it's helpful. Details can be found in the KB articles, but it seems that PrintNightmare remains an issue in November 2021. 

Similar article
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

Patchday: Windows 10-Updates (October 12, 2021)
Patchday: Windows 8.1/Server 2012 Updates (October 12, 2021)
Patchday: Updates for Windows 7/Server 2008 R2 (October 12, 2021)
Windows 10 V1809 Preview Update (2021/10/19)
Windows 10 V2004-21H1 Preview Update (2021/10/26)


Cookies helps to fund this blog: Cookie settings
Advertising


This entry was posted in issue, Update, Windows and tagged , , , . Bookmark the permalink.

3 Responses to Windows PrintNightmare status Nov. 1, 2021 (KB5006674, KB5006670)

  1. Maskoa says:

    We have more than 300 laptops which cannot print. When connecting to network Windows displays 0x0000007c and "Windows cannot connect to printer". The only way to get the printing work is to uninstall update KB5006670.

    • Bulldogs says:

      When I try doing that, it simply reinstalls. How do we use MS software and live at this point?

  2. Bulldogs says:

    It is really too bad the Microsoft is leaving most of us with no choice but to move to Unix based solutions. We can't just shut down our business whenever MS chooses.

Leave a Reply

Your email address will not be published.