Windows 10 dual boot gives unknown file system

[retnug]

@cactux

I guess I was a bit unclear before.

My saying that it won’t help was meant for the ability of having a dualboot system where both of the systems (EOS and Windows) would be bootable from the same bootmenu.

By turning on Secure Boot, you are impeding EOS to boot via its EFI boot entry in BIOS. That is why the next EFI boot entry (Windows’) is tried and that one boots.

My comment was a bit misleading. I think we are both on the same page. I was just happy I was able to boot Windows “somehow” in the moment.

@cactux

For now, just disable Secure Boot and make sure Linux Boot Manager is the first boot option in BIOS. Reboot and test.

This is the exact setup, which caused the issue in the first place and brought me here. Anyway, I tried it again and got the same result: “unknown file system” and “grub rescue”.

When digging through my BIOS searching the secure boot option, I noticed that the boot loaders were listed there: “Linux Boot Manager”, “Manjaro” and “Windows Boot Manager”. Given your comment that grub should never show up when booting systemd and the plan to get rid of the Manjaro boot loader, I deactivated it in the BIOS. I figured that maybe the automatic detection process you mentioned (which works for me, because I do have a Windows 10 entry in the systemd boot menu without a config in /efi/loader/entries) picks up the Manjaro boot loader by accident. And indeed, after disabling the Manjaro thingy in BIOS Windows boots when I select the entry in the systemd boot menu. And after restarting and selecting EOS, I am back here in EOS.

Thanks a lot for standing me by.

EDIT:

I just double checked with bootctl. Manjaro is still listed there. How would I get rid of the EFI entry to avoid any confusions once and for all?