After a Windows update, my laptop started automatically booting into Windows. I tried to use solutions found here and here. I was unable to fix the issue due to roadblocks like identifying partitions, as I am a new user. There is a Fedora entry in my UEFI boot menu, but using it just boots Windows.
Thanks in advance for any guidance
1 Like
Removed f39
Aha! That just happend to me as well.
The fix in my case was simple.
- reboot
- enter BIOS (press DEL or F2 usually as the system boots up)
- go to the boot menu in the BIOS and put Fedora first
- save changes
- reboot
The Windows update seemed to reorder to put itself as the first boot entry.
I donât recommmend dual boot when windows in one. Windows will eventually overwrite settings.
Instead, disconnect the windows drive, plug the new hard drive for linux and install linux, then replug the windows drive.
To switch OS, choose the boot select menu in the BIOS.
This method guarantees windows will never mess with the boot settings anymore.
relevant meme
6 Likes
Unfortunately, Fedora doesnât appear in the boot order list. I believe that this may be a problem with grub2, and I cannot figure out how to reinstall it.
This tool saved my system once when grub replaced lilo. Never used since but threâs a new version. Hope it helps find your Fedora boot and fix it.
I have been running Dual boot for a very long time Windows 8, Windows 10 and not Windows 11.
Yes Windows may rarely set itself to boot first, but that is trivia to fix.
There is no need to remove the Windows disk as you suggest.
I have never lost data becuase of dual boot.
If fedora is missing from the UEFI BIOS boot list that is not a grub2 issue.
Can you boot the Fedora USB install and run the efibootmgr tool to show what is setup in the EFI to confirm that Fedora is missing and post here?
efibootmgr -v shows a Fedora entry whose path is \EFI\fedora\shimx64.efi
However the boot entry is only available from Windows advanced startup, and using it just boots into windows.
Sorry to read that, there is another tool
Better luck with this one.
You fix this in the UEFI BIOS, not in Windows as you appear to be saying.
Considering the prevalence of dual-boot systems and the frequency of Windows updates, itâs reasonable to assume that thousands, if not tens of thousands, of users might encounter this issue annually. This estimate takes into account both new installations and existing setups where updates could lead to bootloader conflicts.
Youâve been lucky or youâre a tech savvy. My recommendation stands for the reason above.
I canât get rescatux to boot on my machine. Is there a way I can restore grub2 from a Fedora live usb? This seems to be how others solved the problem, but I was not able to replicate because I faced some issues in the steps.
For example, this guide, where I was not able to identify my root and boot partitions
Hi,
Unfortunatly, being unfamiiar with UEFI and secure boot and having 12-14 years old computers, I canât help with that and Iâm sorry I canât.
However I succeeded several times doing what you describe with traditional boot sectors (BIOS+MBR). Precisely using the Fedora live cd. On luks encrypted system.
I suggest you make copies or clones of your data partitions or the entire disk before attempting regenerating boot partitions.
To identify the partitions (root/boot), run âlsblkâ from the livedvd and recopy here. You seem to be on the right track so it worth taking extra steps to avoid any data loss.
liveuser@localhost-live:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 2G 1 loop
loop1 7:1 0 8G 1 loop
ââlive-rw 253:0 0 8G 0 dm /
ââlive-base 253:1 0 8G 1 dm
loop2 7:2 0 32G 0 loop
ââlive-rw 253:0 0 8G 0 dm /
sda 8:0 1 233.1G 0 disk
ââsda1 8:1 1 2.1G 0 part /run/initramfs/live
ââsda2 8:2 1 12.5M 0 part
ââsda3 8:3 1 300K 0 part
zram0 252:0 0 8G 0 disk [SWAP]
nvme0n1 259:0 0 953.9G 0 disk
âânvme0n1p1 259:1 0 100M 0 part
âânvme0n1p2 259:2 0 16M 0 part
âânvme0n1p3 259:3 0 201.1G 0 part
âânvme0n1p4 259:4 0 1G 0 part
âânvme0n1p5 259:5 0 730G 0 part
âânvme0n1p6 259:6 0 21G 0 part
âânvme0n1p7 259:7 0 674M 0 part
I suspect that nvme0np5 is my root partition?
Yes, it is. nvme0n1p5
nvme0n1p4 could be your boot. Youâll have to mount it and see if there is grub stuff inside e.g.
sudo mkdir /mnt/boot; sudo mount /dev/nvme0n1p4 /mnt/boot; sudo ls -lah /mnt/boot
if you see grub stuff, youâre in business, e.g.
dr-xr-xr-x 6 root root 4096 17 jun 10:41 .
dr-xr-xr-x 1 root root 210 24 avr 13:00 ..
-rw-r--r-- 1 root root 271840 16 avr 20:00 config-6.8.7-300.fc40.x86_64
drwx------ 4 root root 4096 24 avr 13:08 efi
drwx------ 5 root root 4096 5 aoĂ» 07:06 grub2
-rw------- 1 root root 88524202 24 avr 13:30 initramfs-0-rescue-c9b852c1fd8c44b8aaa12d3e5c7a3992.img
-rw------- 1 root root 22607886 23 mai 08:21 initramfs-6.8.7-300.fc40.x86_64.img
drwxr-xr-x 3 root root 4096 17 oct 2023 loader
drwx------ 2 root root 16384 17 oct 2023 lost+found
lrwxrwxrwx 1 root root 45 24 avr 13:13 symvers-6.8.7-300.fc40.x86_64.xz -> /lib/modules/6.8.7-300.fc40.x86_64/symvers.xz
-rw-r--r-- 1 root root 8899100 16 avr 20:00 System.map-6.8.7-300.fc40.x86_64
-rwxr-xr-x 1 root root 14966600 24 avr 13:29 vmlinuz-0-rescue-c9b852c1fd8c44b8aaa12d3e5c7a3992
-rwxr-xr-x 1 root root 14966600 16 avr 20:00 vmlinuz-6.8.7-300.fc40.x86_64
-rw-r--r-- 1 root root 160 16 avr 20:00 .vmlinuz-6.8.7-300.fc40.x86_64.hmac
I have seen this after installing Windows 11 updates. The problem is that even with fastboot disabled, Windows 11 hybernates after updating. I discovered that that âSettings/System/Recoveryâ gets the grub menu (set as the first UEFI entry on my dual-boot system).
Totally makes sense.
Maybe booting win, setting the power button action to âpower downâ and reboot, shutdown using the power button, and see what happens.