Issues when installing/using PrinterDrivers (CLJ MFP3302) on Win 11 24H2 ARM64

[GuidoW]

--- This related to Windows 11 Arm64 version !!  for a CLJ MFP3302 - it might be the same for other HP models ---

Hi,

I just want leave this here to document my experience with the current state of the HP printer/scanner drivers (in my case for a CLJ MFP3302swdg) used with Win 11 ARM64 Stable and 2H24. First of all, there is NO Scanner driver for ARM64. The x64 Scanner drver will not install due to the absence of thePlugPlay service in Win11 ARM64 which is currently essential for HP drivers to install / work correctly. I'm not here to judge if it is HPs or Microsofts faut, but nevertheless, HP should have released ARM64native drivers month/years ago as Win on Arm is something that is around for at least 4 years, Anyway - no Scanner on Win Arm64. The x64 or x32 scanner drivers will not even run even if you try instal them manually - if you want to try, the ...webpack.exe the the basic drivers is just a .zip fie.

At least for my 3302 printer there is an ARM64 Version avaiable - which is also installed via the direct device installation from within Windows (slightly different version). If you use this version it will dtetect that you have a scanner but due to the lack of working drivers, the scanner will not work. The current pribterdriver however will not work either. This is due to an heap error in printfilterpipelinesvc.exe - allegedly ;-)- caused by Hp printer filter driver (see https://learn.microsoft.com/en-us/windows-hardware/drivers/print/attaching-a-debugger-to-the-print-f...) - ErrorCode 0xc0000374.

It results in the print job being put into the queue and the gets deleted when the print filter pipeline service (printfilterpipelinesvc.exe) crashes. 

Using the ARM64 printer drivers from HP support page - after cleaning everything (btw. I'm using the Windows 11 sandbox for my tests, so no old driver version get stuck somewhere) - the same thing happen BUT the message in the printer queue is not "Deleted" it changes to "Printed" - but there will be no printout 🙂 App crash is the same  - of course it uses the same filter.

Current workaround: Printing 

Use the standard "Microsoft IPP Class Driver"  as recommended here (https://learn.microsoft.com/en-us/windows-hardware/drivers/print/microsoft-universal-printer-driver)... It will work just fine without the hassle.  Just install the printer "manually" 

Select you connection method and use "IPP Device" as device type. 

This works like a charm, even with multiple trays and duplex printouts. 

Current workaround:  Scan

Use the scan funtions on the printer itself or use https://www.naps2.com/ (OSS) to use the scanner via eSCL - a free client for windows/linux/mac, that works perfectly fine! Or you can use the HP Smart App from the Microsoft App Store but this needs an registration/login to scan.

I'll try to update this as time progresses. Maybe HP will write ARM64 drivers that work and/or some that will not require the PnP service and the XPS driver filter pipeline. And of course, if I could wish for something: Make it Open Source. So we can just debug and maybe fix it directly  🙂 

Spoiler

In case someone @HP reads this: The "nice" person I had on the phone when opening a support case before I figured all out by myself,  should read this article and maybe takes some learnings, on how things can be debugged and alternatives can be found and not telling me for 30 min. that this a Windows update error 🙂

[Bill_Bailey]

My experience has been nearly identical to yours. The only way I can get a brand-new HP Color LaserJet 3201 to print using Windows 11 on a Microsoft Surface Laptop 7 (CoPilot + with Snapdragon X) is to use the MS IPP driver. It works well but there are frequent "paper out" errors when the paper tray is full. Despite what HP service techs claim on this website, the HP SUPD driver for ARM64 DOES NOT WORK on my Surface Laptop 7. The driver installs and can be selected from the driver list for the printer, but nothing EVER prints with the driver selected. I don't have any HP scanner products or MFP's so I can't test the claim that HP doesn't provide working drivers. But the situation is identical with Epson scanners: NO ARM64 drivers are available. Very frustrating!!! Please get with it, HP!