Microsoft patches patch that broke USB printing in Windows 11
- Reference: 1743000313
- News link: https://www.theregister.co.uk/2025/03/26/microsoft_deborks_usb_printers/
- Source link:
The patch, [1]KB5053657 for Windows 11 22H2 and 23H2, came out on March 25 and, according to Microsoft, repairs what it broke in [2]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."
[3]
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 [4]certain printer manufacturers would be delighted to see users wasting ink, thanks to the problem. Every little counts and all that.
[5]
[6]
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 [7]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 [8]removed Copilot from some devices, or, as Microsoft put it, "The app is unintentionally uninstalled and unpinned from the taskbar."
[9]Printers start speaking in tongues after Windows 11 update
[10]Windows Patch Tuesday update might send a user to the BitLocker recovery screen
[11]Microsoft warns Windows 10 patch broke printing for some
[12]Microsoft puts the 'why?' in Wi-Fi with latest Windows patch
[13]Microsoft struggles to wake from PrintNightmare: Latest print spooler patch can be bypassed, researchers say
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.
[14]
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 [15]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." ®
Get our [16]Tech Resources
[1] https://support.microsoft.com/en-gb/topic/march-25-2025-kb5053657-os-builds-22621-5126-and-22631-5126-preview-87a95447-6e12-4cd6-a7cf-ef525b8a489f
[2] https://support.microsoft.com/en-gb/topic/january-29-2025-kb5050092-os-builds-22621-4830-and-22631-4830-preview-fc9d13d6-09c6-412e-aab5-939e2c13a768
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2Z-QysWbFpHz7u5rqzY-WmwAAAEk&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[4] https://www.theregister.com/2024/03/07/hp_ink_addicts/
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Z-QysWbFpHz7u5rqzY-WmwAAAEk&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33Z-QysWbFpHz7u5rqzY-WmwAAAEk&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[7] https://support.microsoft.com/en-gb/topic/march-11-2025-kb5053602-os-builds-22621-5039-and-22631-5039-19284fef-ba57-440b-a027-2d5eeecb73fa
[8] https://www.theregister.com/2025/03/17/copilot_windows_update/
[9] https://www.theregister.com/2025/03/12/printer_bug_windows_11/
[10] https://www.theregister.com/2024/07/24/windows_update_bitlocker/
[11] https://www.theregister.com/2022/07/26/windows_10_printer_bork/
[12] https://www.theregister.com/2023/12/18/windows_patch_wifi_broken/
[13] https://www.theregister.com/2021/07/07/printnightmare_fix_fail/
[14] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Z-QysWbFpHz7u5rqzY-WmwAAAEk&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[15] https://www.theregister.com/2025/01/15/windows_patch_tuesday_citrix/
[16] https://whitepapers.theregister.com/
"First we need a patch to patch our patch. Then we need to patch the patch's patchy patch..."
"Someone make him Overlord of Quality Assurance, STAT!"
Nearest I could do......
Quis sarcio ipsos sarcios?
Speedy!
" The patch, [...] came out on March 25 and, according to Microsoft, repairs what it broke in January "
So it took almost two months to fix a bug that disabled a critical business workload function. Well done M$, who seem to have forgotten that vast numbers of businesses rely on them for technology that works reliably in order to stay in business. Welcome to the toyshop!
Re: Speedy!
So it took almost two months to fix a bug that disabled a critical business workload function.
Imagine how long it would have taken them to fix it if it wasn't business critical. I mean, there's pagination bugs still in Word that have been there since Word 2.0c for Windows 3.1. Well, I say Word 2.0c, that's just the earliest place I remember finding them.
Re: Speedy!
Would that be the 'Widows & Orphans' 'feature' or is it something else? Pagination problems with Widows & Orphans continue, except where I kill the 'feature' with extreme prejudice. I can think of a few other long-standing problems..
Note that the Widows & Orphans problem also affects Word for Mac, and may indeed have originated in Word for Mac and been migrated over when MS ported Word for Mac to Windows. (Yes, the original version of Word for Windows was a port from Word for Mac. Note that this is no longer the case, Word for Mac is usually a port from Word for Windows. God help us all.)
In Microsoft's defense...
HP printers were used to print a single smiley face, then spit the sheet out, then do it again on the next sheet, ever since imemmorial time.
The first model I had was a B/W one, Deskjet 520, adorably beige frame and it could ruin a whole stack of 50 A4 sheets in under 10 minutes. It was pretty fast when it came to ruining your supplies.
This was... in 1994, dear lord. 31 years of CRAPPINESS by HP.
How Bad Do You Have To Be
to fuck up printer drivers.....
Then I remembered it's Microsoft that we are discussing here.
I see no difference
The marketing department, which insisted on their direct USB printers, still prints nonsense.