Windows 11 boot broken after installing Fedora 40

Hey all!

A linux noob here. I just installed Fedora 40 Workstation next to my Windows 11 install (wanted to dual boot). I choose a to install Fedora 40 on another drive as i wanted them on separate drives.

After installing Fedora it works perfect, but my Windows 11 install refuses to boot. With an error (Secure boot signature not found). Also it shows up as “UEFI OS”. But i can still see and transfer files from my Windows 11 installation.

What i tried already;

  • Booting with secure boot off and on
  • Make a w11 bootable to restore boot. (it could not fix itself)

I don’t want to reinstall Windows 11. So if anyone can help with my problem that would be great :smiley:

Added f40

It doesn’t sound right that it would error with “secure boot signature not found” if secure boot is turned off. Are you sure it is turned off?

Edit: Oh, I see, if you encrypted your drive with Bitlocker, then MS Windows won’t boot if you try to turn off secure boot. You have to turn off Bitlocker first (or never turn it on) if you want to disable secure boot.

If i turn off Secure Boot in the BIOS and boot into windows (UEFI OS) i get this error;

error; no such device: CE3B-9209
error: File /efi/Microsoft/boot/bootmgfw.efi not found

That device identifier looks like a FAT32 UUID. I guess the whole drive is encrypted so that it cannot even read the partition table or filesystem UUIDs.

You’ll have to get it to work with secure boot turned on.

I thought Windows 11 installed and enabled Bitlocker automatically. But when i enable it again i still get the error as described earlier (Secure boot signature not found). I know W11 needs secure boot and TPM to boot up.

To give a more context. Before installing Fedora my W11 install worked fine. There was no problem at all. After the installation i didn’t work anymore. I’m clueless why it doesn’t boot anymore, and of course how to fix it…

Did you disable W11 bitlocker before installing Fedorq?

I think there is a key in the TPM. If you reset the TPM, that key might be removed. There appears to be some documentation here: Disabling Secure Boot | Microsoft Learn

Among other things, it says “On some PCs, select Custom , and then load the Secure Boot keys that are built into the PC.” Did you try that?

I don’t know. I don’t have a lock on my :C disk. So i don’t think so.

Just tried to follow one tutorial on how to do it. I set it to custom and reset factory keys. What is “Install the Default Secure Boot Keys”? Option Appeared After Resetting Bios Still having the same error.

I don’t know how to work with MS Windows anymore. I switched to using Linux long before secure boot existed. I just hope Linux never starts encrypting people’s files without their knowledge. I’d want to be sure I know how to recover things before I ever turned something like that on. Maybe someone else will be able to help, but this forum might not be the best place to find answers about MS Windows problems. :slight_smile:

Please provide details of the current disk layout and EFI boot configuration from running sudo fdisk -lx | cat and efibootmgr in a terminal. Post the output as pre-formatted text (use the </> button from the top line of the text entry panel). The |cat will wrap the overly long lines that might otherwise be truncated when you paste terminal output.

I dual boot Windows 11 and Fedora, but rarely use W11. W11 updates have often caused problems booting Fedora. We can hope W11 has improved . If not, the above requested details may help you recover Fedora after a W11 update. You should review manual pages for fdisk and efibootmgr so you understant the output you are posting.

Have you tried booting your PC with the second hard drive disconnected? I think changes in the hardware configuration can affect the TPM measurements; especially if the added drive is earlier in the boot sequence.

Edit: Found this just now with a search for information about secure boot and hardware changes (I don’t know if it is true or under what circumstances it might apply):

UPDATE: i spoke with many AMD and Microsoft’s technicians and it appears that one’s got to disable secure boot before any hardware change and re-enable it after the upgrade to not incur in issues like inability to boot the OS… lol

From sudo fdisk -lx | cat;

Disk /dev/sda: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: GIGABYTE GP-GSTF
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 9071D30B-D43C-45EA-AB88-ED9AD4348B16
First usable LBA: 34
Last usable LBA: 937703054
Alternative LBA: 937703087
Partition entries starting LBA: 2
Allocated partition entries: 128
Partition entries ending LBA: 33

Device       Start       End   Sectors Type-UUID                            UUID                                 Name                 Attrs
/dev/sda1     2048   1230847   1228800 C12A7328-F81F-11D2-BA4B-00A0C93EC93B BA995A81-98A3-4E4A-A064-FF82F7E48015 EFI System Partition 
/dev/sda2  1230848   3327999   2097152 BC13C2FF-59E6-4262-A352-B275FD6F7172 5A72FD85-C055-4920-AA9E-1D5A1475B0B0                      
/dev/sda3  3328000 937701375 934373376 0FC63DAF-8483-4772-8E79-3D69D8477DE4 8580B842-D6A6-4221-84FF-76C97AD43B14                      


Disk /dev/sdb: 111.79 GiB, 120034123776 bytes, 234441648 sectors
Disk model: GIGABYTE GP-GSTF
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 963ABA76-0D98-CF4E-9654-CCADDBB81D9E
First usable LBA: 2048
Last usable LBA: 234441614
Alternative LBA: 234441647
Partition entries starting LBA: 2
Allocated partition entries: 128
Partition entries ending LBA: 33

Device      Start       End   Sectors Type-UUID                            UUID                                 Name Attrs
/dev/sdb1    4096    618495    614400 C12A7328-F81F-11D2-BA4B-00A0C93EC93B FDA28A92-103F-014C-9B07-03DAA46141C9      
/dev/sdb2  618496 234436544 233818049 0FC63DAF-8483-4772-8E79-3D69D8477DE4 D15B2196-B1D7-ED4C-931A-71B6597B8710      


Disk /dev/sdc: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000DM008-2FR1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: A29CB1F9-58F6-432E-A981-025E8162C7BC
First usable LBA: 34
Last usable LBA: 3907029134
Alternative LBA: 3907029167
Partition entries starting LBA: 2
Allocated partition entries: 128
Partition entries ending LBA: 33

Device     Start        End    Sectors Type-UUID                            UUID                                 Name                         Attrs
/dev/sdc1     34      32767      32734 E3C9E316-0B5C-4DB8-817D-F92DF00215AE 70F4591D-3F17-41B5-BFA8-A68ADA7AFCCE Microsoft reserved partition 
/dev/sdc2  32768 3907026943 3906994176 EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 353528BC-6D01-4F3B-9C09-433894798A2A Basic data partition         

Partition 1 does not start on physical sector boundary.


Disk /dev/sdd: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: HDS721010KLA33R 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x10fb0eef

Device     Boot Start        End    Sectors Id Type Start-C/H/S   End-C/H/S Attrs
/dev/sdd1          63 1953523119 1953523057 42 SFS        0/1/1 1023/254/63 


Disk /dev/nvme1n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: CT2000P3SSD8                            
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 7782BCB8-9913-4EAC-9BAE-1D07083B1125
First usable LBA: 34
Last usable LBA: 3907029134
Alternative LBA: 3907029167
Partition entries starting LBA: 2
Allocated partition entries: 128
Partition entries ending LBA: 33

Device         Start        End    Sectors Type-UUID                            UUID                                 Name                         Attrs
/dev/nvme1n1p1    34      32767      32734 E3C9E316-0B5C-4DB8-817D-F92DF00215AE FE96BE67-E9AB-464E-94AD-4D7FC3C5E9C1 Microsoft reserved partition 
/dev/nvme1n1p2 32768 3907026943 3906994176 EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 1530409D-C670-4B01-9A39-A347D07F38CE Basic data partition         


Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: Lexar 1TB SSD                           
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 0D93EFF1-6AFA-4BFD-8570-5ADECEE5510A
First usable LBA: 34
Last usable LBA: 2000409230
Alternative LBA: 2000409263
Partition entries starting LBA: 2
Allocated partition entries: 128
Partition entries ending LBA: 33

Device         Start        End    Sectors Type-UUID                            UUID                                 Name                         Attrs
/dev/nvme0n1p1  2048      34815      32768 E3C9E316-0B5C-4DB8-817D-F92DF00215AE 6CF13A26-8DCF-4C59-B565-9D97A18643BF Microsoft reserved partition GUID:63
/dev/nvme0n1p2 34816 2000408575 2000373760 EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 FD3C6C1F-3850-47E6-8156-A59EB9F07B63 Basic data partition         


Disk /dev/zram0: 8 GiB, 8589934592 bytes, 2097152 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

And from efibootmgr;

BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 000C,0001,0002,000D
Boot0001* Fedora	HD(1,GPT,ba995a81-98a3-4e4a-a064-ff82f7e48015,0x800,0x12c000)/\EFI\FEDORA\SHIMX64.EFI
Boot0002* Manjaro	HD(1,GPT,fda28a92-103f-014c-9b07-03daa46141c9,0x1000,0x96000)/\EFI\MANJARO\GRUBX64.EFI
Boot000C* UEFI OS	HD(1,GPT,fda28a92-103f-014c-9b07-03daa46141c9,0x1000,0x96000)/\EFI\BOOT\BOOTX64.EFI0000424f
Boot000D* Fedora	HD(1,GPT,ba995a81-98a3-4e4a-a064-ff82f7e48015,0x800,0x12c000)/\EFI\FEDORA\SHIM.EFI0000424f

Will try. Letting know when i know more.

Tried it. No result. :frowning: Meanwhile i also tried to run the Bootrec / fixmbr, Bootrec / fixboot, Bootrec /rebuildbcd in the CMD on the w11 installation media. Only get Access denied at /fixboot… Am really at my wit’s end.

I’ve never done it, but it looks like it is possible to use a Windows PE recovery disk to access a Bitlocker encrypted Windows installation: How to Unlock Bitlocker Drives in WinPE | LazyExchangeAdmin