Plasma broken after reinstall & GRUB can’t boot into Windows (10)

[Ilovemyhouse]

@pebcak

I can’t for the life of me understand why Grub cannot boot up Windows even though it finds Windows Boot Manager.

I honestly don’t know who to blame, Windows or GRUB, because GRUB boots other distro’s just fine.

[pebcak]

Everybody is to blame!

[bigrand]

Did you update GRUB after enabling os-prober?

[Ilovemyhouse]

Yes, and actually I think many time’s after wards.

Plasma broken after reinstall & GRUB can’t boot into Windows (10)

Attention : le sondeur de systèmes d'exploitation sera exécuté pour détecter d'autres partitions amorçables. Sa sortie sera utilisée pour détecter les binaires amorçables qu'elles contiennent et créer de nouvelles entrées d'amorçage. Windows Boot Manager trouvé sur /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi Linux Mint 20.3 Una (20.3) trouvé sur /dev/sda2 Ajout de l'entrée du menu d'amorçage pour les paramètres du firmware UEFI … fait But, still the same issue (for both Windows entries), b…

[ricklinux]

I only have the one entry in Windows using Easy BCD.

There is one entry in the Windows bootloader.

Default: Windows 11
Timeout: 30 seconds
EasyBCD Boot Device: C:\

Entry #1
Name: Windows 11
BCD ID: {current}
Drive: C:
Bootloader Path: \WINDOWS\system32\winload.efi

[bigrand]

Then no idea why the issue was solved if copying Windows EFI files shouldn’t have an effect.

[Ilovemyhouse]

But hey, if it works, you don’t touch it anymore.

[ricklinux]

It is my understanding that grub gets installed and takes over as the boot loader and it has the entries for Windows to boot both. I don’t think it matters if you have a separate /efi on EOS or use the Windows /efi. It still is booting Windows from grub. The grub file that gets generated /boot/grub/grub.cfg

[bigrand]

Yeah, that’s why copying the files from one partition to the other shouldn’t make an effect. Maybe, GRUB does support it but doesn’t do it by default? No idea, but I’m glad the problem was solved.

[ricklinux]

This is what it creates from grub …

### BEGIN /etc/grub.d/45_eos_windows ###

menuentry 'Windows Boot Manager (on /dev/nvme0n1p1)' --class windows --class os $menuentry_id_option 'osprober-efi-A0B8-6414' {
        insmod part_gpt
        insmod fat
        search --no-floppy --fs-uuid --set=root A0B8-6414
        chainloader /efi/Microsoft/Boot/bootmgfw.efi
}
### END /etc/grub.d/45_eos_windows ###

Edit: This is the entry that boots Windows. Other entries are there for everything else. This is at the very bottom of the .conf file.

[bigrand]

@Ilovemyhouse

@Ilovemyhouse

Could the issue be that they have the same UUID?

[ricklinux]

It has to have the uuid of the partition that is used to boot from. In my case it’s the Windows efi on the drive that has Windows installed.

Edit:

As you can see the efi partition on Eos is different. Mine is using the Windows efi.

[ricklinux]

Not sure if that is the reason for the OP’s problem but just showing what i have.

[bigrand]

Even thought they are the same UUID, in the GRUB menu it was detecting the partition from /dev/nvme0n1 disk. This problem is really weird, I thought it was an old entry boot (I thought removing a boot entry using efibootmgr only affected an EFI Partition, but it’s not saved there), because OP has 3 different EFI Partitions.

[ricklinux]

I don’t know? I don’t usually have these issues. It’s odd to me also.

Edit: I’m with @pebcak I’m defeated…

Edit2: I guess this is why systemd-boot was added and grub is optional.