There are a few rather sudden threads to pop up lately on this:
As you are now the third to appear in a short time, I sent an alert to the ZorinGroup regarding this issue as a package check may be necessary.
There are several things that can cause that generic error.
Secure Boot being disabled is one. I prefer it disabled, so my solution would just be to put a hold on the package.
Or you can remove the package if not using Secure Boot:
sudo apt remove secureboot-db
If you are using secure boot - so far, our normal methods of getting the package through like sudo fwupdmgr refresh --force do not seem to be working for many users.
Ubuntu Snap may be responsible (unconfirmed).