Windows 10/11: USB printers print random texts after January 2025 update

Windows[German]Microsoft has disclosed a new problem that affects both Windows 10 and Windows 11 and is caused for the first time by the January 2025 preview update. Some USB printers may then "possibly" print random text. The problem has already been fixed by rolling back a fix via the built-in KIR feature.


Advertising

USB printing problem after update KB5050081 / KB5050092

Microsoft released the preview update KB5050081 for Windows 10 22H2 and KB5050092 for Windows 11 23H2 on January 28. The fixes from these updates are usually also included in the subsequent updates, i.e. the February 2025 and March 2025 security updates and the February 2025 preview update.

In the Known Issues section of the Windows 11 23H2 Release Health dashboard and the Windows 10 22H2 counterpart, the support article USB printers might print random text with the January 2025 preview update was published on March 11, 2025. Microsoft informs about an issue with printers. This issue occurs with USB dual-mode printers that support both the USB print and IPP over USB protocols.

For Windows 11 23H2, it is stated that after installing the Windows Preview Update (KB5050092) dated January 29, 2025 (or later updates), you may experience issues with USB-connected dual-mode printers if they support both USB printing and IPP over USB protocols.

For Windows 10 22H2, the installation of the Windows preview update KB5050081 from January 28, 2025 (or a subsequent update) is named as the cause. The problem caused: Users observe that the printer unexpectedly prints random text and data. This may include network commands and unusual characters.

As a result of this problem, according to Microsoft, the printed text often begins with the header "POST /ipp/print HTTP/1.1", followed by other IPP (Internet Printing Protocol) related headers. This problem occurs more frequently when the printer is either switched on or reconnected to the device after a disconnection.


Advertising

This problem has now been fixed by Microsoft with a Known Issue Rollback (KIR). Since the support article was published on March 11, 2025 and it can take 48 hours for the KIR fix to take effect, those affected should wait or try restarting their Windows 10/11.

Administrators in corporate environments have the option of rolling out the KIR fix via Group Policy (see How to use Group Policy to deploy a Known Issue Rollback). Here are the relevant downloads:

Similar articles:
Patchday: Windows 10/11 Updates (February 11, 2025)
Patchday: Windows 10/11 Updates (March 11, 2025)
Windows 10/11: Preview Updates Jan. 2025
Windows 11 23H2 Preview-Update KB5050092 (Jan. 29, 2025)
Windows 10/11: Preview Updates Feb. 2025


Advertising

This entry was posted in issue, Update, Windows and tagged , , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

Note: Please note the rules for commenting on the blog (first comments and linked posts end up in moderation, I release them every few hours, I rigorously delete SEO posts/SPAM).