Printer problems: Even with Windows 11, there’s still an end in sight

Microsoft’s problems printing under Windows in the local network has now been going on for more than two years and there is still an end in sight under Windows 11. As the company has just confirmed, two cumulative updates for Windows 10 and Windows 11 are now causing crashes again.

Repeatedly errors when printing in the local network

As Microsoft confirms in a couple of its support documents, cumulative updates take care of KB5006674 For Windows 11 and KB5006670 For Windows 10 again for printer problems in local networks. So already known printing issues always occur when the printer client tries to establish a connection to a shared remote printer on a print server. The following error messages appear:

According to Microsoft, print environments affected by this issue can usually be found in businesses and organizations, while private users are less likely to be affected. In October 2019, KB4517211 cumulative update caused corresponding printer problems under Windows 10 for the first time.

Microsoft does not control the problem

After Microsoft managed to fix the issue with update KB4568831 in August 2020, update KB50000802 paralyzed many printers again for Microsoft Patchday in March of this year. Just a few weeks ago, there were also new issues with Brother printers connected to the USB port under Windows 11.

Once again, Microsoft now offers a solution to printer problems in Windows 11 and Windows 10.

• Print clients must have installed a Windows Update released on or after January 2021 before the print server can install the respective October Update.
• Ensure that network and VPN security solutions allow print clients to perform RPC over TCP connections to the print server using the following range of ports:
  • Standard- Startport: 49152
  • Standard – Endport: 65535
  • Port range: 16,384 ports

Microsoft

Windows 7, 8.1, 10 and 11 were affected as well as servers from 2008

In addition to Windows 11 (“21H2”) and Windows 10 (from 1607), according to Microsoft, there are also Windows 8.1, Windows 7 SP1, Windows Server 2022, Server 2019, Server 2016, Server 2012 R2, Server 2012, and Server 2008 R2 affected. SP1 and Server 2008 SP2 have issues.

For more information, go to docs.microsoft for Windows 10 and docs.microsoft For Windows 11. The website drew attention to the renewed issue for the first time sleeping computer.