I faced, as many users in the world, the corruption of the dual boot Linux-Windows 11 after Microsoft launched update 23H2.
I was able lo boot Fedora Linux from a live USB in a limited way but want to regain full command on my system.
Is there already a solution to this issue?
Can you verify that your EFI system partition still contains a folder EFI/fedora ?
If so, you should be able to re-register Fedora’s GRUB in the UEFI NVRAM with a command like:
efibootmgr --create --disk /dev/sda --part 1 --label Fedora --loader \\EFI\\Fedora\\shim.efi
(That assumes your EFI system partition is at /dev/sda1. Change the --disk and --part options appropriately if not.)
You likely have the same problem as the poster of this thread: Unable to boot fedora 41 after installing windows 10 to different hard drive - #16 by pg-tips
Hi, @pg-tips .
Thank you very much for your reply.
Well, seems to be there is no /EFI or /boot/efi folder.
I setup my system the follwing way.
A 500 GB NvME disk for both Windows and Linux system and program files.
Each operating system has its own partition.
Besides, a 1 TB SSD for data. Also two partitions for each Windows and Linux.
Here are two screenshots showing the Linux main folder and the boot folder.
Didn’t find any efi folder.
It’s possible to have a Fedora install without an EFI system partition (by using MBR instead). However if Windows 11 is installed, there should be an EFI system partition somewhere. It probably just isn’t shown in the file manager GUI (I know mine isn’t shown in Dolphin).
In your installed Fedora it would be mounted as /boot/efi, but when running from a live USB it likely isn’t auto-mounted.
From a terminal can you run lsblk -f ? Hopefully that’s going to show us a small (100 - 1000 MB) FAT32 partition, which we can then mount and look at the contents of.
Hi again, @pg-tips .
I finally found my GParte Live USB stick.
The system carries a 500 GB NvMe drive for both Windows and Fedora operating systems system files and an SSD drive for also both Windows and Fedora data files.
Here are the results
As can be seen, there are two partitions affected one at each drive.
OK, so it looks like /dev/nvme0n1p1 is your EFI system partition.
Can you mount that partition, and check that it still has a directory EFI/Fedora containing the shim.efi file (among other .efi files)?
If so, then the Fedora bootloader should still be present, and it can be re-registered in the NVRAM of the UEFI using:
efibootmgr --create --disk /dev/nvme0n1 --part 1 --label Fedora --loader \\EFI\\Fedora\\shim.efi
Then on reboot, your Fedora install should be available as a boot option.
For now, don’t worry about the warnings on that “Microsoft Reserved Partition”. That shouldn’t cause any issues in Linux and it most likely doesn’t cause any in Windows either - it’s a legacy thing that doesn’t seem to be necessary for Windows 11.
This article may help provide a fix for the situation you’re finding yourself in.
Good luck!
You can’t imagine what a burden this has been, @jrredho .
