Microsoft has warned that starting with optional preview updates last week, a year-old workaround that fixed Windows Server printing issues on non-compatible devices will no longer work. Therefore, there may be problems with printing.
Let me remind you that we wrote that Microsoft is trying to fix printing problems in Windows 10, and also that Brother printers may not work in Windows 11.Last year, the developers explained that in some versions of Windows Server after installing the July 2021 security updates, various print and scan failures may occur due to a known issue. This bug affects printers, scanners, and MFPs that are not compliant with security changes for CVE-2021-33764 and use PIV smart card authentication.
As Microsoft now states, in Windows Server 2019, the interim fix for this issue has been disabled with the release of optional preview updates. As a result, this can lead to printing and scanning failures when working with incompatible devices.
Temporary mitigation will also be removed from all affected versions of Windows Server (Windows Server 2019, 2016, 2012, and 2008) through scheduled security updates that will be released on August 9, 2022.
To find devices that do not comply with the new requirements and fail to authenticate after the updates are installed, administrators are advised to check the logs of their Active Directory domain controllers for audit events that identify non-RFC-4456 (Section 3.2.1) non-compliant devices added after the updates were deployed. Windows Server February 2022.
In addition, Microsoft says that Windows updates released on June 28 and later (KB5014666) also cause printing problems on devices, but this time connected via USB. In this case, the issue affects both client (Windows 10, versions 20H2, 21H1, and 21H2) and server (Windows Server, versions 20H2) platforms.
It turned out that users complain that applications that refer to a printer using a specific name cannot work with printing, and Windows creates duplicate installed printers with similar names and the “Copy1” prefix.
Microsoft assured that they are already studying this problem and will publish additional information as soon as something clears up.
