Server 2022 Update KB5122882 Reportedly Breaks Type 3 Printing

If your staff print through a Windows "terminal server," the shared server everyone logs into with Remote Desktop, and printing fell apart sometime after September 8, the printers themselves may not be the problem. Windows news sites are reporting that Microsoft's September security update for Windows Server 2022 breaks a group of older printer drivers on exactly those servers.

Here's what's known as of September 21, how to tell whether it's what you're seeing, and why the one quick workaround reported so far is a bad idea.

What broke after the September Windows Server 2022 update?

Several Type 3 printer drivers stopped working on Windows Server 2022 Remote Desktop Session Host servers after the September update, according to reports covered by Neowin, Windows Report and Born's Tech and Windows World. Printer-sharing problems were reported too.

The update in question is KB5122882, the September 8, 2026 cumulative security update for Windows Server 2022 (OS Build 20348.5622), as listed on Microsoft's support page and in its Windows Server release information.

Type 3 (or v3) drivers are an older Windows printer-driver model, and third-party v3 drivers are among those Microsoft is phasing out (more on that below). If your server was set up years ago with the printer maker's standard driver, it may well be using them.

One caution on evidence: Neowin traces the report to a single administrator's post on Reddit, and Microsoft hasn't confirmed the problem. Treat it as "reported," and match your own symptoms before acting.

Which printer drivers are affected?

Three drivers are named in the reports, all Type 3 user-mode drivers, according to Neowin, Windows Report and Born's Tech:

• HP Universal Printing PCL 6
• Adobe PDF Converter
• DYMO LabelWriter 450 Turbo

That's an awkward trio for a small office: an HP driver, the PDF "printer" and a label printer. If all three can fail together, the cause is probably not any one brand.

Why does this look like a Windows problem rather than an HP, Adobe or DYMO one?

Because the failure points to shared Windows files, not to one manufacturer's code. The September update replaced five shared Windows print-driver framework files: PS5UI.DLL, PSCRIPT5.DLL, UNIDRV.DLL, UNIDRVUI.DLL and UNIRES.DLL, which live in C:\Windows\System32\spool\DRIVERS\x64\3\, according to Neowin, Windows Report and Born's Tech.

That's why reinstalling the HP driver or buying a new label printer is unlikely to help while the shared Windows files are the issue.

How can you tell if your server is affected?

Look for two specific errors. Reports from Neowin, Windows Report and Born City describe these symptoms:

If your errors look different, you may be dealing with something else. Last month's .NET Framework update that broke printing and PDF export in some business apps is one example of a failure that looks like a printer problem but isn't, and our printer driver management guide covers the general troubleshooting steps.

Did the September 14 out-of-band update fix printing?

No. On September 14, Microsoft released out-of-band update KB5129237 (OS Build 20348.5631) for Windows Server 2022. According to Microsoft, it fixed the acknowledged Remote Desktop Services instability and a multichannel USB-audio problem, not printing. Neowin, Windows Report and Born's Tech all report that servers with both updates installed are still affected.

There's a catch worth knowing: Microsoft's KB page says KB5129237 is available only from the Microsoft Update Catalog, not through Windows Update or WSUS. An office that relies on automatic updates may not have it at all, which matters if you're also seeing Remote Desktop sessions stop responding.

As of the September 18 reports, Microsoft hadn't listed printing among the known issues for either update, according to Neowin and Windows Report.

Is there a safe workaround?

Not an official one, and the only workaround reported so far is one we'd steer you away from. According to Neowin, Windows Report and Born's Tech, the administrator behind the report replaced three of the updated Windows files with older, pre-update copies from a backup, which brought back HP Universal PCL 6 printing on that server. Neowin called it a preliminary observation.

Don't try that yourself. Hand-swapping Windows system files can break future updates, and copying back older files can reopen security holes the update closed. It's the kind of fix that works on a Friday and bites you on the next Patch Tuesday.

Safer options to ask your IT provider to test, one server at a time (none has been confirmed by Microsoft for this bug):

• Printing through a Type 4 or Windows class driver instead of the Type 3 driver, where the printer supports it.
• The printer maker's newest driver package, if it isn't Type 3.
• Remote Desktop Easy Print for users connecting from their own PCs.

Avoid uninstalling KB5122882 as a shortcut, too: it's September's security update, and our September 2026 Patch Tuesday rundown covers the kinds of flaws that month's updates fixed. If your IT provider does roll it back, they should document the trade-off and a date to reinstall.

Why is this a good moment to plan beyond Windows Server 2022?

Because Server 2022 is about to change status, and the legacy driver model involved here is being phased out on newer Windows versions. Windows Server 2022 reaches the end of mainstream support on October 13, 2026, and the October security update will be its last mainstream-support update, according to Microsoft's release health page and The Register. Security updates continue through October 14, 2031, so this is a planning milestone, not a cliff.

Meanwhile, Microsoft is phasing out legacy third-party v3 and v4 printer drivers in favor of its built-in IPP (Mopria) class driver. Under the timeline on Microsoft Learn, which applies to Windows 11 and Windows Server 2025 and later, no new printer drivers are published to Windows Update from January 15, 2026; from July 1, 2026, Windows' driver ranking prefers the inbox IPP class driver; and from July 1, 2027, third-party driver updates will be allowed only for security fixes. Windows Latest and Windows Central covered the phase-out, and we explained what it means for older printers in our Canon and Windows driver changes post.

What this means for San Fernando Valley offices

We haven't found any reports specific to Los Angeles or the Valley, but the setups at risk are familiar ones. For example, a medical or dental practice whose front desk prints patient labels on a DYMO through a terminal server, a law or accounting office that saves to Adobe PDF from a hosted practice-management app, or a shipping station printing labels from a shared server could depend on the same kinds of drivers named in these reports.

When all printing funnels through one server, one bad update stops the whole office at once. The upside is that one careful test server can protect everyone. If your practice handles patient data, our medical office printer guide covers printer setup with privacy in mind.

What to do now

1. Match the symptoms. Look for "Entry Point Not Found" naming UNIDRVUI.DLL, or failures connecting to a DYMO label printer shared from a print server, on the Server 2022 Remote Desktop host or print server.
2. Check the update history. Note whether KB5122882 (September 8) and KB5129237 (September 14) are installed; remember KB5129237 comes only from the Microsoft Update Catalog.
3. List your Type 3 drivers. Your IT provider can check each shared printer's driver type in Windows' Print Management console.
4. Don't copy DLLs from old backups or download "fixed" driver files from forums.
5. Test one alternative at a time on one server or one printer before changing everything.
6. Test the next update before rolling it out. Microsoft's next scheduled Server 2022 security update is due on Patch Tuesday, October 13.
7. Plan your next printers around class drivers. When you replace devices, favor models that work with Windows' built-in IPP class driver; our recommended printers page is a good starting point.

If your office prints through a shared Windows server and you'd like a second opinion before anyone touches system files, book a free virtual consultation.

Update (September 30, 2026)

As of September 30, Microsoft still hasn't acknowledged the printing problem. Its Windows Server 2022 release health page, last updated September 29, lists only a USB audio issue (mitigated), the Remote Desktop issue (resolved) and a resolved Defender notification issue, and the support pages for KB5122882 and KB5129237 don't mention printing either. Neowin and Windows Report had noted the same absence when the reports first surfaced. In short, there's no official fix or workaround yet.

The next scheduled update is the October security update on October 13, which Microsoft says is also Windows Server 2022's last mainstream-support update. Test it on one server before assuming it fixes printing.