After installing Fedora, Windows won't boot
5 Attachment(s)
Hello. I had dual boot Windows 10 + Linux Ubuntu 18.04 LTS. I installed Fedora on an empty partition using Legacy Support. Now when I try to set UEFI as default in BIOS, I am getting an error afterwards. I can run Ubuntu, but not Windows 10. I opened GPARTED in Ubuntu and the Windwos partition isn't deleted, but it still won't boot. I uploaded screenshots
|
2 Attachment(s)
2 more screenshots
|
Your Legacy install of Fedora Grub will not boot an EFI install of windows but will boot an EFI install of Linux. If you want Grub to boot all systems, they must match (all UEFI or all Legacy). You show both a BIOS_grub partition which is used only on GPT drives for Legacy install as well as an EFI partition. With that setup, you will need to access the BIOS to make changes needed to boot windows.
Have you tried setting the Grub boot entry for Ubuntu in your BIOS to first priority? AFAIK, the windows default bootloader won't boot either Linux in either mode without user intervention or 3rd party software. |
Unless you are a true expert, you must have all operating systems installed in the same boot mode, either UEFI, or legacy. Windows installed in UEFI mode cannot be booted in legacy mode. Installing Fedora "using legacy support" sounds like it was installed in legacy mode.
I'm not a Gparted user, so can only surmise that the red exclamations in the screenshot are informing you of partitions that will not be bootable using the current configuration. You're probably going to need to revert to the partitioning in place before installing Fedora to get Windows to boot again, then install Fedora in UEFI mode. But before doing anything else, boot Ubuntu, open a terminal, and paste here using code tags ( [ # ] above the input window) input and output from: Code:
sudo parted -l |
Quote:
Code:
user@Lenovo-ideapad-110-17IKB:~$ sudo parted -l |
Quote:
|
Quote:
Quote:
Code:
parted /dev/sda See if you now have the option to set ubuntu as first in boot option. Running "sudo update-grub" in ubuntu should give you options to boot fedora. |
Quote:
Code:
user@Lenovo-ideapad-110-17IKB:~$ sudo update-grub |
Code:
p.s. I restored an earlier version of Windows using a Windows 10 installation CD. This could have something to do with Windows not booting to get fedora boot menu add a menuentry in /etc/grub.d/40_custom something like this Code:
menuentry 'fedora config file'{ Then rerun update-grub |
Quote:
|
More info seems to be called for, to learn where Ubuntu is, and what Fedora did and may be trying to do:
Code:
mount | grep sda |
Quote:
I am going by memory from reading the discussion and was unable to find the post on askfedora that discussed it but will keep searching. UPDATE: Apparently the issue was related to secure boot, and it already affected F32 so they decided that F33 could be released. There is a fedora magazine article that discusses the secure boot issue here. On some machines turning off secure boot will allow fedora to boot, but it may also interfere with windows and/or Ubuntu since the change apparently forces secure boot on for those systems. Ubuntu has apparently removed the dbx update that triggered the problem but that won't help already existing installs. The full details of the fedora release meeting and about the bug can be found here for those who are interested. The gist of it is that fedora may not install or boot with secure boot on and other OSes may not boot with secure boot off. UPDATE2 Here is the actual bug related to secure boot with fedora. |
Quote:
Code:
user@Lenovo-ideapad-110-17IKB:~$ sudo |
One more, to see if it suggests what's on /dev/sda5:
Code:
cat /etc/fstab I've never seen efibootmgr produce network entries before. Do you have any sense as to why they are there? Unless you are PXE booting, I have to guess they could and should be removed using efibootmgr -B. |
Quote:
Quote:
|
All times are GMT -5. The time now is 12:22 PM. |