This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I have a Canon MF643cdw printer as a local printer on a Windows 11 pro desktop connected by usb. A few days ago I upgraded the desktop to the Windows 24H2 level. When I now switch on the printer, the printer itself prints 4 pages. On the first page there are a few lines :
POST /ipp-print HTTP-1.1
Connection: keep alive
Content-type: application/ipp
User-agent: Windows internet print provider
Content-Length:626
host:local host"
I already uninstalled and re-installed the printer, unchecked the informative notifications. But no success. Before the upgrade everything worked well, the issue was introduces by the 24h2 upgrade.
What is the solution for this?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Yesterday I was forced to go to windows 11 24h2 again. I am running with it for 2 days now and the issue has disappeared. Printing and scanning both work. So it looks Microsoft did something in the latest build to solve it.
My configuration now is :
Windows 11 Pro 24H2, build 26100.3194
For the Canon MF643cdw I installed the newest driver GPlus UFRII version 3.12 released 2 weeks ago.
Same issues here with all USB connected printers. Uninstalling the KB resolved my issue. This isn't a viable solution in an org with over 1k PCs and half of them with usb connected printers.
Microsoft must have done something to fix this issue. It has been more than 2 weeks since the last time I experienced the unwanted printing.
I confirm, you are right, in my opinion printing in Windows 10 22h2 was broken by the KB5051974 patch.
Jonny,
the issue started with me when I migrated early january from Windows 11 23h2 to 24h2. I saw a lot off these messages on forums, all in combination with the 24h2 update.
I see very recently on the forums the same message on windows 11 23h2, 22h2 and windows 10. My guess is that it was introduced by the monthly patches from Microsoft in february.
Bernard77
