Report: Windows Server 2022 Users Hit by Printing Issues After September 2026 Update

By now, you may have come across multiple reports about the September 2026 Patch Tuesday update triggering several issues. In case you are unaware, the latest Patch Tuesday update has reportedly caused RDS failures, USB audio problems, Remote Desktop issues, VPN and Hyper-V Linux folder-sharing failures, among other problems. In fact, Microsoft has already released emergency out-of-band updates to address some of these issues. But it seems Windows Server 2022 admins are also being affected by printing issues following the September 2026 updates.

September updates are reportedly breaking Type 3 printer drivers

Admins are facing printing issues with several Type 3 printer drivers reportedly failing on Remote Desktop Session Host systems. The issue appears to involve shared Windows printing framework files rather than a specific printer manufacturer. The report, posted on r/sysadmin by Reddit user OBJRoyal13, suggests that the problem appeared after installing the September 8 security update KB5122882 and remained after Microsoft released the September 14 out-of-band update KB5129237.

According to the administrator, the affected environment consists of Windows Server 2022 machines running the Remote Desktop Session Host role. The printer problems involve HP Universal Printing PCL 6, Adobe PDF Converter and the DYMO LabelWriter 450 Turbo, all using Type 3 user-mode drivers.

The reported failure points to five files inside the Type 3 printer-driver directory: PS5UI.DLL, PSCRIPT5.DLL, UNIDRV.DLL, UNIDRVUI.DLL and UNIRES.DLL. One of the reported errors says that RtlLogUnexpectedCodepath could not be found in UNIDRVUI.DLL, while DYMO installations can fail with error 0x00000006.

Rolling back shared files reportedly restores printing

The administrator says restoring older copies of UNIDRV.DLL, UNIDRVUI.DLL and UNIRES.DLL from a July backup restored HP Universal Printing PCL 6 printing. Another sysadmin in the Reddit comments said they were able to reproduce the fix when installing a shared DYMO printer from a patched Windows 11 PC to a Windows 10 machine.

That also suggests the problem is not limited to one printer model. One administrator reported seeing similar DYMO behavior when Windows 10 clients accessed printers shared from fully patched Windows 11 PCs, although the exact scope of the regression remains unclear.

All that said, Microsoft has not currently acknowledged this specific printer-driver problem in its known issues section. We’ll update you with a separate article if we hear anything official from Microsoft.

Via: Neowin