I have the same problem, after installing Fedora 34 I cannot start Windows 10. Even after adding the path to the boot loader in the BIOS it doesn’t start. On Youtube I saw that you are able to update grub and then it tries to Fix the bootloader but it was not on Fedora.
Please be noted that the path of the grub.cfg is change on EFI systems.
It is /boot/grub2/grub.cfg
I have been successful installing Fedora 34 using Anaconda installer and maintaining dual boot with Windows 10 Pro that was pre-installed. The key is to maintain the ESP (EFI System Partition) unchanged from how Windows 10 configured it. The only change to ESP is to add the Fedora linux mount point designation “?boot/efi” to the partion identification. then for fedora adding another ext4 formated partition named /boot. It does NOT need to be wihtin the first few cylinders of the disk.
For UEFI booting there can be one and only one ESP partition upon a disk. Consult a WIndows 10 expert to learn if it is possible to ‘slot in’ just the ESP partition and preserving other information on the disk. My personal action would be to simply completely wipe the disk and start over installing Windows 10 then adding fedora using Anaconda installer. If you added an mbr, obliterate it. It is not needed for UEFI booting.
What’s the output from
sudo parted --list? And are there
.efi files in
Thanks, Johnathan! There are not efi files in Microsoft/Boot only in Windows. It’s strange because at some point I was able to dualboot but made a fresh reinstall of Fedora which caused Windows to disappear. The files are all still on my drive so probably the efi files are deleted during the reinstallation?
The way you wrote that, it sounds like you’re saying that there are
.efi files directly in
/boot/efi/EFI/Windows, just not in the
/boot/efi/EFI/Microsoft/Boot subdirectory? Is that correct, or does
/boot/efi/EFI/Windows not exist or not contain
.efi files under it at all?
Seeing the output from
sudo parted --list would be very helpful before speculating on what happened.
Kinda. It’s still
/boot/efi/EFI/fedora/grub.cfg on EFI systems, it’s just that since Fedora 34 that file now defers to
The Microsoft subfolder doesn’t include any efi files but the windows subdirectory contains bootmgfw.efi and bootmgr.efi
What does tho output of the following command say?
It should list all found boot entries, adding an Asterisk * to all enabled ones.
BootCurrent: 0001 Timeout: 1 seconds BootOrder: 0001,0002,0000 Boot0000* Windows 10 Boot0001* Fedora Boot0002* Fedora
Do you have two Fedora installations?
Usually there should be one instead of two.
Mine looks like this:
BootCurrent: 0002 Timeout: 1 seconds BootOrder: 0002,0000,0003,000F,0010,0009 Boot0000* Windows Boot Manager Boot0002* Fedora Boot0003* UEFI: Built-in EFI Shell Boot0009 Hard Drive Boot000F UEFI OS Boot0010 Network Card
I reinstalled Fedora (Wifi and Audio weren’t working and I thought a reinstall would help) and maybe this fucked up everything. There should be only one Fedora. Is there a way to see which one is the active I use?
Look up fix master boot record MBR for windows 10 or repair EFI bootloader. You will need a usb drive with Windows 10. You could also try the auto repair in advanced options.
it worked thanks a lot!! Now I need to find a way to get grub started again so I can dual boot again wihtout using BIOS
Boot into fedora and in the terminal type “sudo os-prober” , “sudo nano /etc/default/grub” to change timeout from 5 to 10 save and exit. Then to apply changes type “sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg”. Restart and grub menu should come up.
thanks a lot! getting closer and closer The Grub menu appears when I boot Fedora in Bios but if I turn on the laptop it will start windows directly. Is it something I need to configure in Windows so it recognizes a dual boot?
In your bios change the boot order to fedora first then windows second, that might help.
thank you this is it! Everything working well for me now!
no problem glad i could help.