I understand, but I'm just saying that the fix had more to do with Linux Mint being based on Ubuntu 24.04 than it did with their developers. That's how I'm looking at it for now until otherwise corrected and/or proven wrong. Feel free to try. 
From what I understand, it is closer to 21 core developers and 61 people total:
https://www.datanyze.com/companies/linux-mint/346952036
3 Likes
I have just seen this post in another thread, which may be of interest here, but involves a clear-out of keys which may concern some. See this: Error configuration update to secure boot dbx - #15 by LiveShortAndStruggle
Also.
Note datanyze treats LibreWolf as unsuppored browser and suggests chrome only. So that link may be limited use.
In the same Thread is mentioned to switch to the Snap Version of fwupd:
Glad I'm not affected. Snap is a security isdue in itself.
Hello:
I have read about this situation.
Beyond the possible solution (I have followed all suggestions and none have worked), it can be frustrating for a newcomer, with basic knowledge, who chooses this distro that is promoted as an alternative to Windows.
As many have pointed out, and I have checked, this does not happen in the latest version of Linux Mint.
It seems to me that, again, it is a wake-up call for the Zorin Group to take too long to release a new version (Zorin 18).
Regards.
3 Likes
Yeah. You're not wrong.
This shouldn't even need Zorin 18. Don't get me wrong; I agree that it should be fixed on Zorin's side, but a fix like this SHOULDN'T even need 17.4, I wouldn't think. This is patch territory, or should be.
2 Likes
Ubuntu 24.04 may ship with a newer shim and fwupd, which include support for more recent dbx updates.
If the system updates its dbx to revoke an old bootloader (an old grub or shim), it must have a newer bootloader ready, or the system will not boot.
Therefore, older distros may not push dbx updates unless they are known-safe for that distro's bootloader version.
A new update may need to be backported if the later distros do carry a newer fwupd or shim package. I think, based on my interaction with @zoran in another thread, that this is likely the case, though I have not combed through all of the package versions to verify each one of each.
3 Likes
Totally agree.
The Zorin group should send an update that fixes this problem, or a new version 17.3.1 that would accomplish the same purpose.
Waiting until Zorin Os 18 is too long.
Regards.
2 Likes
Would tag Artyom and Kyrill here, but ... nah. I'd rather they be proactive on their own and communicate next steps or the current situation to us end users. The problem is resolved for me because I updated my BIOS, but regardless, it still bothers me a bit to see that the issue is still going on, and nothing's been heard from the Zorin Group lately. That translates into a lot of affected users.
As such, I have to ask: What if? What if a future problem like this occurs again? Will I not be so fortunate next time? Will I have to wait interminably for a resolution or an update from the Zorin Group? That'd really grind my gears then. I want to be able to depend on a company that has our backs, 24/7. Especially one that I paid. It's a reasonable expectation. Not much more I can say. It speaks for itself.
Or as they say in Latin, "res ipsa loquitur." Fun times ... not. 
2 Likes
waiting to see a fix. if not, well...
2 Likes
Yup. I know what you mean. Take it from someone who's given Zorin OS chance after chance.
2 Likes
Is there some sort of a page that has important broadcasts re. changes/fixes/current developmental focus (in general, but would include this issue) that I can follow?
I'm not concerned, but I'm a bit interested to see how this develops.
To date, I've just been lurking in the forums.
1 Like
Go HERE. EDIT: That's just a pinned thread @Aravisian did, but no, nothing "official" by the Zorin Group that's meant to address everything regarding all this.
3 Likes
For what it's worth, Artyom hasn't posted since 6/17/25. That's been over a week now despite multiple people posting about this. Kyrill hasn't posted since 9/2/24. Mmm. Gonna leave it at that. I hope for other users, they come up with a fix soon.
That is a fair comment IMO. Another hurdle to be overcome for some Windows to ZorinOS migrants.
There should not be a need to install a later version of fwupd from Snap, to help fix persistent cases of this problem. As mentioned here: Secure Boot dbx Failed to build error issue - #28 by Ziga88
I fortunately do not see the problem on my old laptop. I also do not use Snap or Flatpak.
3 Likes
I agree completely with you. I do NOT like snap. Flatpaks are OK-ish, but no. All this stuff hitting the fan really highlights why the Zorin Group should switch to Debian for its code base. Having an update that fixes this issue for others in snap format only is limiting and forces users to adapt a file format they do not want on their systems, and that's anti-Linux. Not good at all. The Zorin Group needs to release an emergency fix as a .DEB file (to make it accessible for all), and push it ASAP.
2 Likes
Howdy- I would like to bypass, delete, disable secure boot. Or how can I stop the updates to secure boot. I want to bypass the whole secure boot to where I never have to see its shadow again. I cringe when this subject comes up, having been waylayed in the past. Please help!
You mean I paid for the pro version and mint is maintained better than zorin. Is there a legitimate reason for this? I have used mint and I liked it (I just thought of Mikee, an old TV commercial). But seriously, my confidence in zorin has dropped a few notes. Is there a way to manually update to the latest core? Not really sure of the correct terminology.