Microsoft says Home windows clients are experiencing points with community printing after putting in the Home windows 11 KB5006674 and Home windows 10 KB5006670 updates issued with this month’s Patch Tuesday, on October 12.
Customers making an attempt to connect with printers shared on Home windows print servers would possibly encounter a number of errors stopping them from printing over the community.
The errors Home windows print shoppers will encounter after deploying KB5006674 embrace:
0x000006e4 (RPC_S_CANNOT_SUPPORT)
0x0000007c (ERROR_INVALID_LEVEL)
0x00000709 (ERROR_INVALID_PRINTER_NAME)
The entire listing of Home windows platforms impacted by this challenge contains:
Consumer: Home windows 11, model 21H2; Home windows 10, model 21H1; Home windows 10, model 20H2; Home windows 10, model 2004; Home windows 10, model 1909; Home windows 10, model 1809; Home windows 10 Enterprise LTSC 2019; Home windows 10, model 1607; Home windows 8.1; Home windows 7 SP1
Server: Home windows Server 2022; Home windows Server, model 20H2; Home windows Server, model 2004; Home windows Server, model 1909; Home windows Server, model 1809; Home windows Server 2008 SP2
As Redmond explains, this recognized challenge affecting printing on each consumer and server Home windows platforms is restricted to printer servers that are extra generally present in enterprise environments.
Microsoft mentioned it is engaged on discovering an answer to permit print shoppers to ascertain RPC packet privateness connections to Home windows print servers utilizing RPC over SMB.
Customers tormented by printing issues the final two weeks
Home windows 10 admins and customers have been reporting widescale community printing points in a 14-page discussion board matter at BleepingComputerfor for the final two weeks for the reason that October Patch Tuesday updates have been launched.
Whereas recounting their frustration and makes an attempt to take care of the printing bugs, they got here to the identical conclusion: uninstalling the October cumulative updates resolves the printing downside.
Since then, the problems have gotten so dangerous that Home windows admins have resorted to changing Home windows DLLs with older variations to re-enable printing.
The DLLs that admins are changing to repair printing are localspl.dll, win32spl.dll, and spoolsv.exe.
Whereas this method removes fixes for Print Spooler vulnerabilities, it does keep away from uninstalling the cumulative updates, which might eliminate all October safety updates within the course of.
Microsoft gives a workaround
Prospects impacted by these printing issues can now use an official workaround supplied by Microsoft to repair the problem.
The steps ought to ONLY be taken on affected print servers that meet the next prerequisite: “print shoppers should have put in a Home windows replace launched on or after January 2021 earlier than the print server has put in” the October 2021 updates.
If the workaround necessities are met, Microsoft asks clients to “make sure that community safety and VPN options permit print shoppers to ascertain RPC over TCP connections to print server over the next port vary:”
Default begin port: 49152
Default finish port: 65535
Port Vary: 16384 ports
Redmond additionally gives the next articles for extra steering:
Earlier than disclosing this new challenge, Microsoft mentioned it fastened different Home windows 11 recognized points inflicting printer set up fails and prompts for admin credentials earlier than each try and print in enterprise environments.