# \#secureboot

**URL:** https://discussion.fedoraproject.org/tag/secureboot/1313.md

[Latest](https://discussion.fedoraproject.org/latest.md) · [Categories](https://discussion.fedoraproject.org/categories.md) · [Tags](https://discussion.fedoraproject.org/tags.md)

---

## [Issues with secure boot and nvidia signing](https://discussion.fedoraproject.org/t/issues-with-secure-boot-and-nvidia-signing/206433)

<div class="topic-metadata">

**Author:** [@simon-k](https://discussion.fedoraproject.org/u/simon-k)\
**Replies:** 6\
**Last updated:** [November 1, 2026, 1:48pm UTC](https://discussion.fedoraproject.org/t/issues-with-secure-boot-and-nvidia-signing/206433 "2026-11-01T13:48:13Z")

</div>

Hello, I know it is an older thread but this is the only I stumbled upon. I tried to install the nvidia drivers, and since I have secure boot enabled I tried to sign them, using the help of the Software App. It automatically detected that I tried to install the drivers and prompted me. However, s…

---

## [\[UEFI dbx\] does not currently allow updates: Not enough efivarfs space](https://discussion.fedoraproject.org/t/uefi-dbx-does-not-currently-allow-updates-not-enough-efivarfs-space/195038)

<div class="topic-metadata">

**Author:** [@hellotalk87](https://discussion.fedoraproject.org/u/hellotalk87)\
**Replies:** 4\
**Last updated:** [June 30, 2026, 6:21pm UTC](https://discussion.fedoraproject.org/t/uefi-dbx-does-not-currently-allow-updates-not-enough-efivarfs-space/195038 "2026-06-30T18:21:30Z")

</div>

Hello! Just trying to update my system but it fails with this error. I searched in different forums but I wasn’t able to actually have a valid solution (hopefully there is one). Can you please help? Thanks

---

## [Does Microsoft return multi-signed shim?](https://discussion.fedoraproject.org/t/does-microsoft-return-multi-signed-shim/181486)

<div class="topic-metadata">

**Author:** [@tronde](https://discussion.fedoraproject.org/u/tronde)\
**Replies:** 2\
**Last updated:** [March 31, 2026, 8:15am UTC](https://discussion.fedoraproject.org/t/does-microsoft-return-multi-signed-shim/181486 "2026-03-31T08:15:56Z")

</div>

Dear Community, I found the discussion regarding Test Day: Multi-signed shims and the wiki page Test Day:2026-01-12 Multi-signed shim. On the latter this sentence caught my eye: …shim is currently being signed with both the 2011 and the 2023 keys. This is contrary to my knowledge that Microsoft…

---

## [Can't update 'Secure Boot dbx Configuration Update'](https://discussion.fedoraproject.org/t/cant-update-secure-boot-dbx-configuration-update/135566)

<div class="topic-metadata">

**Author:** [@scotttrakker](https://discussion.fedoraproject.org/u/scotttrakker)\
**Replies:** 18\
**Last updated:** [February 10, 2026, 10:34am UTC](https://discussion.fedoraproject.org/t/cant-update-secure-boot-dbx-configuration-update/135566 "2026-02-10T10:34:03Z")

</div>

Hello Fedora Administrators! For almost a year I get the following message in GNOME Software: In the past I read somewhere that this would be solved in Fedora 41 Silverblue (can’t remember where). However, I upgraded my laptop to Fedora 41 Silverblue and I still get this message. Toda…

---

## [No Fedora boot entry in uefi boot loader](https://discussion.fedoraproject.org/t/no-fedora-boot-entry-in-uefi-boot-loader/172952)

<div class="topic-metadata">

**Author:** [@dastivi](https://discussion.fedoraproject.org/u/dastivi)\
**Replies:** 2\
**Last updated:** [November 18, 2025, 2:46pm UTC](https://discussion.fedoraproject.org/t/no-fedora-boot-entry-in-uefi-boot-loader/172952 "2025-11-18T14:46:03Z")

</div>

Hello there, i just try to install Fedora 43 alongside windows as dual boot on a HP zBook, but after install and reboot there is no Grub/Fedora Boot entry available, its just the windows boot loader, that of course directly boots into Windows. i’ve disabled Fast Boot in Bios, reinstalled Fedora did…

---

## [BootC: How can I sign shim and kernel with own keys?](https://discussion.fedoraproject.org/t/bootc-how-can-i-sign-shim-and-kernel-with-own-keys/169474)

<div class="topic-metadata">

**Author:** [@dirk1980ac](https://discussion.fedoraproject.org/u/dirk1980ac)\
**Replies:** 1\
**Last updated:** [November 4, 2025, 3:18pm UTC](https://discussion.fedoraproject.org/t/bootc-how-can-i-sign-shim-and-kernel-with-own-keys/169474 "2025-11-04T15:18:47Z")

</div>

Hello. I made some bootc images for embedded systems and want to sign kernel and shim with my own keys. Consider the keys existing and the enrollment in UEFI as done. This works with a concentional system, only shim/kernel signed by me boot. Now: How can I sign shim and kernel during a bootc conta…

---

## [Fedora mysteriously fails to boot few days after installation](https://discussion.fedoraproject.org/t/fedora-mysteriously-fails-to-boot-few-days-after-installation/163516)

<div class="topic-metadata">

**Author:** [@twohot](https://discussion.fedoraproject.org/u/twohot)\
**Replies:** 6\
**Last updated:** [November 1, 2025, 11:19pm UTC](https://discussion.fedoraproject.org/t/fedora-mysteriously-fails-to-boot-few-days-after-installation/163516 "2025-11-01T23:19:12Z")

</div>

This has happened twice in a row. The Box: HP Pro 3500 MT (G2) Fedora Version: Server Edition (Minimal) with Sway -- Rawhide (please hear me out) I understand the rants and restrictions around future release versions. I am only looking for a pointer (redirection) to help relevant parties track…

---

## [HowTo: Upgrade a very outdated Fedora Atomic install](https://discussion.fedoraproject.org/t/howto-upgrade-a-very-outdated-fedora-atomic-install/133330)

<div class="topic-metadata">

**Author:** [@boredsquirrel](https://discussion.fedoraproject.org/u/boredsquirrel)\
**Replies:** 2\
**Last updated:** [October 10, 2024, 10:30am UTC](https://discussion.fedoraproject.org/t/howto-upgrade-a-very-outdated-fedora-atomic-install/133330 "2024-10-10T10:30:17Z")

</div>

:warning: Warning :warning: This is experimental and not the recommended way. Doing so will skip migration scripts between versions, that change files not contained in the immutable image. It can cause unexpected breakages. Recommended and supported is this: For documentation purposes, here ar…
