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

[Ilovemyhouse]

@bigrand

EDIT: I think the situation is like this, may be, it’s detecting an old Windows boot entry (from an old installation) since it was detected before os-prober was enabled. I had a similar problem in which the BIOS detected old boot entries that didn’t point to anything. Removing all Windows entries and reinstalling Windows and EOS could solve the problem, but obviously it’s not the ideal solution. The ideal solution would removing the entries and regenerating them both on Windows and EOS, so you don’t have reinstall Windows or EOS.

So deleting the entire /boot and let regenerate the files? ^^’

[ricklinux]

Why can’t you use a windows install disc and do a start up repair in order to fix the Windows bootloader first. Then boot on the live ISO and arch-chroot and install grub again and update grub.

[Ilovemyhouse]

Finally managed to get EasyBCD working, and I some a weird entry.

It’s Windows 10 version 22H2.

[ricklinux]

You can delete it in Easy BCD.

[Ilovemyhouse]

Alright, so to confirm, delete both with BCD, boot to EOS, and regenerate GRUB?
Or did I missed a step to do in between? ^^’

[ricklinux]

I’m not sure which is best. You could try that. I’m just not sure whether it recreates the Windows boot loader on Windows /efi?

[pebcak]

I wouldn’t delete anything for now. I would try adding EnOS’ bootloader and test.

[Ilovemyhouse]

If BCD would let me add it.
I also enabled Expert mode in case you were wondering.

[pebcak]

I feel defeated

[ricklinux]

That’s what happens when Windows breaks your grub.

[bigrand]

@ricklinux

I’m not sure which is best. You could try that. I’m just not sure whether it recreates the Windows boot loader on Windows /efi?

It shouldn’t. I think what GRUB does is detect the Window’s EFI Partition and then it does whatever process to add it to the EOS EFI Partition. I have two EFI Partitions (Windows and EOS) and GRUB only boots the boot entries in the EOS EFI partition not the Windows one.

[ricklinux]

I agree but i was thinking in terms of Windows if you were to remove Linux you would need the Windows /efi so it’s either fix it now or fix it later.

[Ilovemyhouse]

I managed to add EOS into the Windows boot manager (by pressing Shift+Reboot, then select the EOS entry), but… it doesn’t boot into it.

I’ll be trying to put this path into GRUB, though, it’s on the Windows/NTSF partition itself, so other partition UID, other FS… this will be fun…

[pebcak]

@ricklinux

That’s what happens when Windows breaks your grub.

I have solved the issue once and for all!

No Windows co-booting with my Linux distros

[ricklinux]

Can’t you edit it with Esay BCD?

[Ilovemyhouse]

Just the name afaik.

[bigrand]

You can still boot into EOS via BIOS?

[Ilovemyhouse]

Yes, EOS was untouched and still works (for now).

[ricklinux]

It’s very amusing to me because i never seem to have this issue. I don’t know how many times i have tested this dual boot installs. Either on the same disc as Windows or on a separate drive. I don’t understand how it happens. I have an idea? I think sometimes with UEFI the firmware doesn’t save an entry because it’s full. If users do a lot of new stuff more entries get saved. Soon it’s full.

[bigrand]

You are trying to do this, correct?

1. Fire up the EasyBCD application and click on the Add New Entry option.
2. Next, select Linux from under the Operating System tab.
3. Select GRUB2 in the Type field and type in the name of your Linux distro.
4. Under the Drive tab, select the Linux partition i.e. the drive where your Linux system resides. Proceed with caution because selecting the wrong drive will lead to unsolicited data loss.
5. Click on the Add (a plus sign) button to confirm your settings and add your Linux distro to the Windows Boot Manager.