Today my Fedora Silverblue won’t boot on my Dell Precision 4580, it says
Verification Failed: (0x1A) Security Violation
I can successfully boot Fedora Workstation from a USB drive.
How can I verify that my boot configuration or files have not been tampered with?
workstation entfernt
Strange, I had the same issue a few days ago with Ventoy.
Can you boot into the older deployment?
GRUB should be shown either with shift or with F8.
I suppose you already did that?
Added secure-boot, shim
Hi @boredsquirrel , and thanks for your reply.
Unfortunately, your linked discussion sounds different to me, as it is about a signed kernel with a newer certificate than the one provided in the f39 boot loader environment, so simply selecting an older kernel would allow you to boot your system and reinstall a newer boot environment.
But that doesn’t seem to be my problem, as it won’t even load the GRUB boot loader, so I can’t select a different kernel. But the workaround shows me a possible solution - I booted fedora workstation from a USB stick, mounted my encrypted disk, compared the contents of /usr/lib/ostree-boot/efi with /boot/efi and found different EFI binaries, so I cpied them over.
Now it is booting again. 
aaah and it seems the command
cp -rp /usr/lib/ostree-boot/efi/EFI /boot/efi
described on the fedoras magazine article is not correct, this leads to an extra EFI subfolder on my system, ending up in /boot/efi/EFI/EFI/*
But one question remains. Why don’t they update the UEFI binaries? …
Interesting, another issue that will be fixed soon. Afaik bootupd is now in Fedora 41, and may be backported to F40.
Bootupd handles updating grub so this shouldnt happen anymore.
@siosm Hi, do you think this is yet another manifestation of this issue, and we should add the Verification Failed: (0x1A) Security Violation error message to the description here?
Or is it a different problem, not to be mixed up with it?
@siosm Can you please verify whether the command is correct or not? Thanks!
The command worked when I had tested it for the bootloader update. I don’t know what’s happening with this issue.