Microsoft patches patch that broke USB printing in Windows 11

Now the only nonsense printed out will come from the user

Months after releasing a patch that left some printers spouting gibberish, Microsoft is issuing another update to deal with it.

The patch, KB5053657 for Windows 11 22H2 and 23H2, came out on March 25 and, according to Microsoft, repairs what it broke in January.

The problem occurred when a printer driver was installed on a user's device. This could be as a result of powering up the device or plugging it in. Microsoft stated at the time, "You might observe that the printer unexpectedly prints random text and data, including network commands and unusual characters. Resulting from this issue, the printed text might often start with the header POST /ipp/print HTTP/1.1, followed by other IPP (Internet Printing Protocol) related headers."

It's an insight into the inner workings of IPP that Microsoft and its partners would prefer users not see. Then again, we're sure that certain printer manufacturers would be delighted to see users wasting ink, thanks to the problem. Every little counts and all that.

According to Microsoft, the error only affected USB-connected dual-mode printers that support both USB Print and IPP Over USB protocols.

The glitch persisted through February and was listed as a known issue in the March 11 update, which contained another notable whoopsie. Or an enhancement, depending on whether you're an end-user or a Microsoft shareholder. The update removed Copilot from some devices, or, as Microsoft put it, "The app is unintentionally uninstalled and unpinned from the taskbar."

Not to worry though. The Copilot fix didn't require a patch, and Microsoft stated, "This issue has been fixed, and the affected devices are being returned to their original state."

That original state was likely the one where Microsoft inflicted Copilot on a user rather than the halcyon days before it was added to most of the tech giant's products.

As for the USB printing fix, Microsoft reckons that KB5053657 will do the trick. Sadly, another known issue – a problem affecting users of version 2411 of the Citrix Session Recording Agent, persists, at least. The Windows maker continues to maintain: "Microsoft is working with Citrix to address this issue and will update this documentation once a resolution is available." ®