I installed systemd-boot instead of grub

I screwed up the new installation of EOS and instead of having it install grub, because I still have a partition with Windows, I chose systemd-boot (don’t ask me why).

The result is that when it tries to start Windows I get a blue error screen.

Now I’d like to install grub to get dual boot working properly, but I’m looking around and assuming no one has ever made this mistake.

Could you help me?

As far as I know (I haven’t had Windows on my systems for ages now) it should work
Maybe look here to see if there is a solution

Systemd works fine with Win11 Pro for me in dual boot. Infact it works better than Grub for me…

1 Like

Ok, then I didn’t understand this error where come from

Have you looked at the link I sent to see if there are any answers? (I’m not going to read it for you)

1 Like

Could be a corrupt Windows boot loader.

Have you tried hitting F8 on boot to get a boot drive selection menu, and booting from the Windows boot manager directly? If that BSOD’s then it’s a Windows issue IMO.

If you can’t hit F8 to get a list of drives to boot from, it may be available in your BIOS/UEFI as well.

I do hit F8 but no recovery.
I switch the boot list and point at Windows first but nothing, blue screen again.
Wondering if a Windows installation could fix it

I agree with @Sar.

It you have tried to boot your Windows, putting Windows Boot Manager first in boot order and your still getting the blue screen, then most probably it is kaput.

I don’t do much Windows nowadays so I can’t be of much help to you but I guess there are plenty of tutorials on the World Wild Web on the subject of repairing Window’s bootloader.

Please do some research.

Yep, corrupt Windows boot loader by the looks of it.

I’d boot into Linux, backup any files from your Windows install you want to keep onto a completely separate partition, then re-install Windows. It’s usually the quickest method to get past this issue, and will likely be the best option for you.

And just pray that the Windows installer doesn’t kill your systemd boot loader, otherwise you might have to re-install Linux as well :smiley:


it’s crazy… but in desperation I reinstalled EndeavourOS with Grub2 and totally deleted the Windows partition. Maybe in the future I’ll reinstall it, with the hope that it won’t destroy everything…

1 Like

If you are doing a reinstall with dual boot, I would recommend installing windows first and increase the EFI partition size of windows during installation. During the installation of EOS, you can specifically say not to wipe the EFI partition and install systemd-boot/grub on top. I use that very setup with systemd-boot without problems. Systemd-Boot also automatically searches for windows installations and lets me boot it.

Also, if the Windows bootloader is found and executed (and then shows a blue screen of death), then any linux installation shouldn’t interfere anymore, if you didn’t delete any windows files under /<efi-partition>/EFI/Microsoft. You might get problems with bitlocker though if you don’t enable secure boot and sign the linux bootloader and kernel but by your description that is not the case.

It should be mentioned that it is also possible to install both systems separately on different EFI partitions; however, then you might need to specify a temporary bootloader with the UEFI if you want to use a different OS.