Fedora 42 Disables Secure Boot After Upgrade and on New Installations - Claiming That The System Doesn't Support Secure Boot (Anymore?)

[graphizs (This User)]

As someone who uses Nvidia drivers and Secure Boot, it’s currently not possible to run Fedora with both things together.

The problem happens no matter if you freshly install F41 and upgrade to F42 directly (because you can’t finish the setup process on first boot in F42, see this thread to learn more) or if you install F42 directly. mokutil --sb-state claims that my system doesn’t support Secure Boot. And that can’t be true because if you install F41 first and ask mokutil for Secure Boot state, it says that Secure Boot is enabled. After the upgrade (or if you try to install it directly), it suddenly says that my system doesn’t support Secure Boot anymore.

This brings also the problem that systems with Nvidia drivers won’t be able to enroll their keys properly to run F42 with Nvidia drivers + Secure Boot together.

[computersavvy (Jeff V)]

Try running sudo fwupdmgr get-upudates to see what different updates may be availailable for your hardware. If it shows updates available then do the updates and reboot before attempting the system upgrade again.

[graphizs (This User)]

Thanks for the idea. fwupdmgr reports no new updates. Infact only UEFI dbx gets updates at all (already on the newest version). Everything else like my hard drives etc. don’t have available firmware updates. So this is not the solution unfortunately.

[graphizs (This User)]

I created a bug issue on RedHat’s Bugzilla plattform now, see 2361002.

[graphizs (This User)]

To show it better, here’s is what happens:

If I boot the Live ISO image, it works as expected:

If I install Fedora, then it gets deactivated and I can’t turn it back on:

It said it’s turned off even if it’s still activated in the BIOS settings.

[graphizs (This User)]

Found the solution: I had to reset mokutil with mokutil --reset. Now it works again as expected.