Hi,
unfortunately Fedora 43 does not boot anymore after a Win 11 update. Before that dual booting has worked fine, including updating both OSes.
It shows that grubx64.efi has not been found. Does the live ISO have a repair mechanism or is there another easy way to repair this?
Hello, I have Windows 11 Pro (BitLocker) in dual boot with Fedora 43 WS (LUKS2), and a simple sfc /scannow command disables GRUB and the Fedora entry.
The only way I found to bypass this problem was to create a second EFI partition. When installing Fedora 43 WS from the netinstall ISO, I made sure to use Blivet-GUI in manual mode and place /boot/efi in the dedicated second EFI partition. Since then, I havenāt had any more problems with GRUB.
From what little I understand, the second EFI partition doesnāt overwrite the first one. Instead, it provides an input to command/manage it without entirely disrupting the Windows boot process.
The key change is replacing the concept of āoverridingā with the more accurate āproviding an input to command/manage it.ā This clearly explains that GRUB (loaded from the second ESP) becomes the primary boot manager, which then calls the Windows Boot Manager (residing on the first ESP) as an option, rather than simply erasing or replacing the Windows boot files.
Cheers!
That might explain why I havenāt had a problem with Arch+UKI+LUKS and Win11+Bitlocker in dual boot for years. Dual booting is so common, Fedoraās installer should really take dual boot problems into account.
it would be great if someone could do a guide with screenshots on this. I have migrated 2 persons from 100% windows to dual boot W10/F43 and was not happy at all with the new installer, itās very confusing and not intuitive, especially when you have several drives and need to install to a particular partition.
For anyone having the same problem:
Still need to figure out how to modify the already installed system to prevent future problems.
My laptop with Windows 10 Pro (BitLocker) and Fedora 43 WS (luks2) does not have the same problem. On the laptop, I only have a single EFI partition , and I have never experienced issues in five months of use.
I have two SSDs because I was forced by the configuration to use NVMe + SATA3. To use both OSs, I tried installing Fedora 43 WS on the SATA3 drive, but Windows 11 Pro is very aggressive and overwrites the single EFI partition.
Now I have one 1TB NVMe drive, and both OSs are installed on the NVMe but with distinct EFI partitions. This is where my limited expertise ends. With the double EFI partition, I have never had any problemsā¦ At least, not until now. 
I also hadnāt had a problem for almost a year, until today.
The problem is only Windows 11 which is much more aggressive. Consider the 2nd EFI if you donāt already have it.
I donāt have unpartitioned free space left. So I might need to reinstall to get a second EFI partition. deep-drawn sigh.
I have never needed a second efi partition to dual boot with windows.
The critical thing has always been to install windows first since a new windows install seems to always wipe out whatever may already be in the efi partition.
When the situation occurs as in the OP above, the very first step is to boot into the bios setup and reset the boot order so fedora is first. A windows update does not appear to wipe out the fedora information in the esp but it does often change the boot order so windows seems the only one which will boot.
A second step, if the first fails, would be to boot a live media usb and mount the efi partition then look and verify that EFI/fedora still exists. If not then some other repair may be required, but if it exists then bios should be able to boot fedora for you.
Exactly what I did. It has worked find for quite some time.
Boot order was not the problem.
Windows update did damage Fedoraās boot chain, no doubt about it
This post is NOT intended to suggest that one should never allow Windows and Linux to share a common UEFI System Partition. Rather, it is to point out potential risks. Preventing a problem is usually much less of a hassle then dealing with the aftermath of one.
There have been a few posts on the Internet implying that a recent Windows 11 update destroyed Linux. My guest is that a Windows update takes complete control of the shared UEFI System Partition, perhaps deleting content and updating with Windows specific data.
Using a second SSD for data partitions, Linux and its associated UEFI System Partition would shield Linux in the event of a unintended Windows update behavior
My workstation has data partitions, multiple Fedora versions and associated UEFI System Partitions installed on the same SSD. Because I use a separate UEFI System partition for each installation, updates to any one of them will not affect the others.
Straight forward in performing.
rsync -av /boot/efi/ /mnt/ would work well)lsblk -f) and edit /etc/fstab to make that new partition your new /boot/efi. (make the old entry a comment and create a new entry with the new UUID just in case there are problems)sudo umount /boot/efi to unmount the old efi partition and sudo mount -a to mount the new partition.Ciao @computersavvy
Hi. As you know, Iām inexperienced and not very useful with configurations. I use the computer for work and have very little time for setting things up. I have everything encrypted with BitLocker/LUKS2, and both my systems boot with Secure Boot: I have a recent desktop PC with TPM 2.0 and an older laptop from 2013 without a TPM (BitLocker managed with a passphrase).
I bought the laptop secondhand 5 or 6 months ago, and after a complete format, I installed a clean Windows 10 Pro (OEM): a single 1GB EFI partition, 1GB /boot, 6GB swap, and a Btrfs volume (with @ and @home subvolumes for Timeshift snapshots). Fedora 43 WS works perfectly with the single EFI, and Windows 10 Pro doesnāt cause any issues.
On the Intel NUC 12 Pro, however, Iāve had many problems in the past: Windows would overlap and block GRUB. I fixed this by using a second EFI partition managed by blivet-gui so that GRUB controls both the first EFI (Windowsā) and its own. Both EFI partitions have the āESPā and āBOOTā flags in GParted. I just checked GParted to be certain. In blivet-gui, during installation from the netinstall ISO, I manually set the second EFI partition to /boot/efi to avoid any errors.
Cheers!
Thank you for the detailed instructions. My btrfs partition is luks2 encrypted. Can I still shrink it?
Not sure. Anyone with luks experience have an answer?
Can a luks encrypted partition be resized with gparted?
Thank you for the detailed instructions. My btrfs partition is luks2 encrypted. Can I still shrink it?
According to the following links (DDG is your friend!), yes. but there are, apparently, significant potential data loss risks. See the links below for details:
HTHAL
Iām just throwing this out there as an idea. I donāt know if itās possible to implement. Among so many partitions, perhaps you should resize an NTFS partition. Can you resize a C: or a D: using Windows Disk Management?
That could indeed be an option.
Another option I am thinking about is to switch to UKIs and transform the boot partition to an EFI partition. I have used UKI and secure boot successfully on Arch, but donāt know how well it is supported on Fedora.