HP Utility fails with Code Signature Invalid MacOS 10.15.7

[blackoak1]

Any chance of an official reply from HP?

[bhihifi]

According to a posted article at theregister.com, HP is aware of the issue they caused. The article even quotes some posts on this thread.

Edit: link to article added below

https://www.theregister.com/2020/10/23/hp_printer_macos/

[StevePSplusB209]

WooHoo!!!  Thank you SSC_UK, your response set me on the path to the workaround that works for me!!  

(Note: I'm having trouble getting this message to display images ... I hope the descriptions help if you can't see them)

My printer is an HP Photosmart Plus B209a-m inkjet that connects over WiFi.

It shows up in Finder as 'Network > hp002481dc9fe0' 

It has a web control panel at 'hpdc9fe0.local./'   As viewed in Chrome ...

To add the printer (System Preferences > Printers and Scanners > +)

- select the 'IP' tab

- enter the Address (in my case it's 'hpdc9fe0.local')

- select the Protocol 'HP Jetdirect - Socket'

- select the Use 'Generic PCL Printer'

- Click Add

...

(Note: I determined the correct 'Protocol' and 'Use' settings combination by trial and error ... nothing exploded although at one point I did waste paper by sending it PostScript 🙂 )

... and it's good to go!

(Note that the printer is an inkjet in spite of Apple thinking that PCL is only for laser printers)

Thanks again SSC_UK!  Good luck everyone!

[cathealer]

I an using several HP LaserJet 2300 printers none of which were working since yesterday on Mac running Mac OS Mojave and Catalina.  These printers WILL run using Mac OS High Sierra. The workaround that allows my printers to work with Mojave and Catalina is to reinstall the printers using the "Generic PCL Printer option and Bonjour. Do not attempt to use the IP address method and HP software until a new certificate is hopefully issued soon!

[cathealer]

[ALGChicago]

I just Tweeted to HP. I find sometimes companies are responsive when the issues go more public.

[kevink707]

I've tweeted @HP also.

Has anyone tried setting the system time back to Sept. to see if the printer starts working -- ugly, but might be an emergency fix.

[Osplo]

In my case the scan function was dead, using the Embedded Web Server (EWS) I was able to scan as a workaround. Using the HP Easy app I am able to scan too.

Here's hoping for a renewed certificate soon.

[readwriterepeat]

What's frustrating is when I talked to their support, they just kept on giving me the link to the drivers/installers even if I told them numerous times that those don't work. I gave them the screenshots of the expired security prompt and the error prompt as well but it seems like they're in denial about it or something. Smh.

[Tbecker · Accepted solution]

I encountered this problem on my iMac 2019 running Catalina 10.15.7 with a JetDirect-networked HP Laserjet 2055dn. It seems that the HP drivers' code signing certificate for older print/scan drivers expired, and since HP has not updated the drivers since 2017, there is no solution to be had from HP.

The symptom is that you submit a print job, any print job, and it never prints. It never shows up as a failed job, the printer is not paused, etc. I knew that it wasn't the printer itself because I could print to it from other machines over the network.

I was able to identify the specific components that had the code signing issue by

1. looking in the MacOS Console app
2. set it to show only errors and faults
3. Select Reports > Crash Reports at left.

Look for errors like this:

Crashed Thread: Unknown

Exception Type: EXC_CRASH (Code Signature Invalid)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace CODESIGNING, Code 0x1

For me, this identified two items: /Library/Printers/hp/Fax/fax.backend/Contents/MacOS/fax and /Library/Printers/hp/filter/hpPostProcessing.bundle/Contents/MacOS/hpPostProcessing were both crashing every time I submitted a print job.

I was able to resolve the issue by doing the following in the Terminal:

sudo codesign -f -s - /Library/Printers/hp/Fax/fax.backend/Contents/MacOS/fax

sudo codesign -f -s -/Library/Printers/hp/filter/hpPostProcessing.bundle/Contents/MacOS/hpPostProcessing

By issuing these commands, you are setting a new, fresh code signature on those binaries and they will now run successfully. I was able to print after that.