[ad_1]
Home windows 10 customers and directors report widescale community printing points after putting in the KB5006670 cumulative replace and different updates launched this week.
On Tuesday, Microsoft launched Home windows updates to repair bugs and safety vulnerabilities as a part of the October 2021 Patch Tuesday.
These updates embody KB5006674 for Home windows 11, KB5006670 for Home windows 10 2004, 20H1, and 21H1, KB5006667 for Home windows 10 1909, and KB5006714 for Home windows 8.
Since putting in the KB5006670 replace, customers are reporting that they can not print to community print servers, with some customers receiving 0x00000709 or ‘Ingredient not discovered’ errors when trying to print.
In an eight-page discussion board subject at BleepingComputer, Home windows directors recounted their frustration with the printing bugs and got here to the identical conclusion — uninstalling this week’s updates resolves the issue.
Since July, Microsoft has been releasing a continuing stream of safety updates to repair the PrintNightmare vulnerabilities within the Home windows Print Spooler.
As menace actors, together with ransomware gangs, actively exploit these vulnerabilities, Microsoft has modified its Level and Print printing characteristic drastically. Sadly, whereas these modifications repair the vulnerabilities, additionally they result in issues printing to community print servers.
This week, Microsoft launched additional safety updates for Home windows printing vulnerabilities tracked as CVE-2021-41332 and CVE-2021-36970, seemingly inflicting the brand new community printing points.
Whereas many of the reported issues are associated to Home windows 10’s KB5006670 replace, that is seemingly as a result of it’s the most generally used model of Home windows at the moment.
The identical safety fixes have been additionally launched for Home windows 10 1909 and Home windows 11 and can seemingly trigger related points on these Home windows variations.
Find out how to repair KB5006670 community printing points
When the September cumulative updates precipitated printing points, it was doable to repair them by permitting non-Admins to put in printer drivers or disabling the ‘RpcAuthnLevelPrivacyEnabled’ Registry worth.
Nevertheless, this Registry key’s now not working for the issues brought on by the October updates, and customers are required to repair it utilizing different strategies.
The BleepingComputer discussion board subject consists of quite a few recommendations from Home windows admins on find out how to resolve the networking printing points brought on by the Home windows 10 KB5006670 replace. Sadly, as these recommendations both take away safety updates or do not at all times work, they don’t seem to be best for resolving the problems.
What makes these printing points so irritating is Microsoft’s lack of clear steerage and the quite a few modifications that occur every month to the Home windows printing characteristic.
As these modifications all resolve totally different susceptible points of the Home windows Print Spooler, they create a multitude of particular person fixes that Home windows admins want to determine whether or not they’ll repair their printing issues.
BleepingComputer has reached out to Microsoft for official steerage on resolving all of those points however has not heard again at the moment.
Methodology 1: Uninstall the KB5006670 replace
The commonest suggestion is to easily uninstall the KB5006670 replace, which could be performed utilizing the next command in an elevated command immediate:
wusa /uninstall /kb:5006670
Nevertheless, uninstalling the replace will take away the safety fixes for 74 vulnerabilities, together with one actively exploited, making this a harmful technique.
Methodology 2: Exchange C:WindowsSystem32Win32spl.dll
Others have discovered that changing the Win32spl.dll DLL file with the model from the September 2021 updates will repair the community printing downside.
“KB5006670 replaces C:WindowsSystem32Win32spl.dll with model 10.0.19041.1288 which halts printing
We exchange this dll with model 10.0.19041.1237 that was put in September’s Cumulative replace
The hooked up batch script will copy your “good” dll file to every pc this runs on from a server location and rename the “unhealthy” dll. I run it as a startup script for ease”
As this DLL was seemingly modified as a part of a safety replace, this too will trigger your pc to develop into much less shielded from doable future vulnerability exploits.
Methodology 3: Recreating printer queues on print servers
Some customers have additionally reported that eradicating and reinstalling their printers on the print server resolved their downside.
If you take away the printer and set up it once more as an admin, the queues can be rebuilt, probably permitting printing to work once more.
Nevertheless, workstations could should be reconfigured to make use of the brand new printer queue, which can be a really time-consuming process for some organizations.
Methodology 4: Allow CopyFiles characteristic once more
Lastly, some HP printer drivers require the CopyFiles characteristic, which Microsoft disabled in September by default.
For customers who nonetheless want this characteristic, Microsoft launched a hidden Group Coverage that means that you can allow it once more.
To allow the CopyFiles characteristic, create a Home windows Registry worth below the HKLMSoftwarePoliciesMicrosoftWindows NTPrinters key named CopyFilesPolicy. When set to ‘1’, CopyFiles can be enabled once more.
[ad_2]