Printer issues: Even in Windows 11, the view is still not over

Microsoft’s problems with printing under Windows on the local network have been dragging on for more than two years now, and the view under Windows 11 is not over yet. As the company has now confirmed, two overall updates under Windows 10 and Windows 11 are now causing repeated failures.

Repeated errors when printing on local network

As Microsoft confirms in its two support documents, the overall updates are taken care of KB5006674 Windows 11 and KB5006670 Back to Windows 10 for problems with printers on local networks. When a printer client tries to connect to a shared remote printer on a print server, there are always problems with printing. The following error messages appear:

According to Microsoft, printing environments affected by this problem are more common in companies and organizations, while individual users are less likely to be affected. In October 2019, the overall update KB4517211 caused printer issues under Windows 10 for the first time.

Microsoft did not bring the issue under control

After Microsoft fixed an issue with the KB4568831 update in August 2020, the KB50000802 update disabled many printers again in March of this year for the Microsoft patch. Just a few weeks ago there were new issues with the brother printers that were connected to the USB port under Windows 11.

Again, Microsoft now offers a solution to printer issues under Windows 11 and Windows 10.

• Print clients must have Windows Update released on or after January 2021 installed before the Print Server can install the respective October update.
• Ensure that network security and VPN solutions allow print clients to create RPC for the print server using TCP connections using the following ports:
  • Standard-Startford: 49152
  • Standard-Endport: 65535
  • Port Limit: 16384 ports

Microsoft

Servers have been affected since Windows 7, 8.1, 10 and 11 and 2008

In addition to Windows 11 (“21H2”) and Windows 10 (from 1607) according to Microsoft, Windows 8.1, Windows 7 SP1 and Windows Server 2022, Server 2019, Server 2016, Server 2012 R2, Server 2012, Server 2008 R2 SP1 and Server 2008 SP2 Were affected by complications.

For more information, go to docs.microsoft Windows 10 and docs.microsoft For Windows 11. The website caught the attention of the updated problem for the first time Bleeping Computer.