Yeah, it's not specifically the Catalina update. It's something that happened in the last 48 hours or so. Thousands of people, including corporations and school distracts are suffering this problem. I've scoured both Apple and HP forums, and this is the best explanation (if not the most helpful remedy) I have found.
In the HP printer driver support forum, user "StevePSplusB209" wrote in [ https://h30434.www3.hp.com/t5/Printer-Setup-Software-Drivers/HP-Utility-fails-with-Code-Signature-Invalid-MacOS-10-15-7/m-p/7824870/highlight/true#M200138 ]:
This is an HP software signing issue that cannot be fixed or worked-around by users.
An HP developer must
- re-sign the HP Utility code using a valid certificate authority
- re-create the installer package and sign it
- post the updated installer package on HP Support
An experienced developer could do this in a hour or two. I know, I used to do this (retired driver writer)
This may take a week or so for HP to fix ... unless everyone screams REALLY LOUDLY since all of our perfectly functional printers are now just warm electric bricks.
And...
Here's part of a crash dump that points the finger at HP Utility and says exactly why it crashed.
----------------------------------------------
Process: HP Utility [11752]
Path: /Library/Printers/hp/Utilities/HP Utility.app/Contents/MacOS/HP Utility
Identifier: com.hp.printerutility
Version: ???
Build Info: Unknown-1789~1789
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: HP Utility [11752]
User ID: 501
Date/Time: 2020-10-23 16:00:44.641 -0400
OS Version: Mac OS X 10.15.7 (19H2)
Report Version: 12
Anonymous UUID: 4CCE0568-C260-E54D-FF90-435455AB2592
Time Awake Since Boot: 4000 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_CRASH (Code Signature Invalid)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace CODESIGNING, Code 0x1
