Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

"System BootOrder not found. Initializing defaults" is a message from the shim fallback mechanism.

When the system boots the file /BOOT/BOOTX64.EFI (chich is a copy of the shim) it goes into fall-back mode and loads /BOOT/fallback.efi . This will try to install /fedora/grubx64.efi in the uefi configuration.

So, In Fedora run efibootmgr -v and check the contents, especially if it has the entry for windows. Also, check the contents of /boot/efi/EFI and check if the windows loaders are intact.

"System BootOrder not found. Initializing defaults" is a message from the shim fallback mechanism.

When the system boots the file /BOOT/BOOTX64.EFI (chich is a copy of the shim) it goes into fall-back mode and loads /BOOT/fallback.efi . This will try to install /fedora/grubx64.efi/fedora/shimx64.efi in the uefi configuration.

shimx64.efi is a pre-loader signed by MS so you can boot in secure mode. It then checks if grubx64.efi is properly signed by a Fedora key, and then loads it.

So, In Fedora run efibootmgr -v and check the contents, especially if it has the entry for windows. Also, check the contents of /boot/efi/EFI and check if the windows loaders are intact.