How does this Advance Windows Security Updates Break Network Printing?

Windows administrators report wide-scale network printing problems after installing this week’s September 2021 Patch Tuesday security updates. On Tuesday, Microsoft released sixty security updates and fixes for numerous flaws as part of their monthly Patch Tuesday updates, which consist up of a fix for the last remaining PrintNightmare vulnerability addressed as CVE-2021-36958.

This vulnerability is sensitive to fix as it is utilized by different ransomware groups and threat actors to urgently gain the SYSTEM privileges on vulnerable devices. Although, multiple Windows systems administrators are now reporting that their systems can no longer print to network printers after installing the PrintNightmare fixes on their print servers.

How-this-Advance-Windows-Security-Updates-Break-Network-Printing-image1

In the discussion with multiple Windows admin handling these issues, they all told our experts that the updates are breaking their network printing, and they can only fix them by removing the updates. “The problem has happened for us on numerous of sites. The print servers were 2012R2 and 2016. All function fine before the updates,” one administrator told our experts.

More Network Printing Problems  

“After yesterday’s Windows release, none of the network systems can print to Windows 10 computer we use as a print server,” another admin told our experts.

“As far as we know, this concerned both printers with v3 and v4 drivers, but I’m not 100% sure (this issue was different from the issue emerged with the previous update which broke v3 printers). After uninstalling the patch on the server everything got back to normal,” another admin told us yesterday. While all users are experiencing problems with network printing, they do not see the same errors.

For example, one person told us that their devices are displaying a 4098 Warning in the Application event logs. This error states, “The user” preference item in the” Group Policy Object did not apply because it failed with error code ‘0x8007011b’ this error was suppressed.”

Another admin told us that their Printer ports tab was blank, while another said they received “Access Denied” errors.

These issues also appear to be affecting all network printers, including HP, Canon, Konica Minolta, and label printers, and for both Type 3 and Type 4 printer drivers. Those with USB printers connected directly to their computers are not having any issues.

The updates associated with the new PrintNightmare security update and the subsequent network printing problems are:

  • KB5005568 (Windows Server 2019)
  • KB5005613 (Windows Server 2012 R2)
  • KB5005627 (Windows Server 2012 R2)
  • KB5005623 (Windows Server 2012)
  • KB5005607 (Windows Server 2012)
  • KB5005606 (Windows Server 2008)
  • KB5005618 (Windows Server 2008)
  • KB5005565 (Windows 10 2004, 20H2, and 21H1)
  • KB5005566 (Windows 10 1909)
  • KB5005615 (Windows 7 Windows Server 2008 R2)

PrintNightmare Fixes Causing Significant Problems

Unfortunately, to fix the PrintNightmare vulnerabilities, Microsoft has had to make significant changes over the past two months to the Windows Point and Print feature and how the drivers can be installed from a print server.

These differences involve needing administrator rights to establish a printer driver through the Point and Print feature.

Once Microsoft executed these changes, Windows users started receiving errors when attempting to print, or Windows would inspire for an administrative identification to modernize printer drivers. While Microsoft has established new registry settings that enable you to control these changes, disabling them will once again make a Windows device vulnerable.

According to security researcher Benjamin Delpy, this week’s PrintNightmare fix also introduced new changes that automatically block the CopyFiles directive print driver feature. 

Admins can configure this change via the Windows Registry CopyFilesPolicy value under the HKLM\Software\Policies\Microsoft\Windows NT\Printers key. When set to ‘1’, CopyFiles will be enabled again.

If another printer drivers are used in your organization that uses the CopyFiles directive, they will no longer work, leading to further conflicts.

Leave a Reply