On Thu, Sep 14, 2017 at 3:20 AM, Peter Humphrey <pe...@prh.myzen.co.uk> wrote: > On Thursday, 14 September 2017 05:09:14 BST R0b0t1 wrote: > >> The trickiest part is still the same - going from GRUB or, now, your >> EFI shell, to Window's bootloader. See here: >> https://wiki.archlinux.org/index.php/GRUB#Chainloading_Windows.2FLinux_ins >> talled_in_UEFI_mode. > > That advice, though helpful, is about Grub, which isn't installed on this > box. I did try at first to get it to work here, but failed, so I removed it > and went for bootctl. It's a fiddle to keep up to date with kernel upgrades, > but at least it works. >
In that case it seems like systemd-boot will check for the Windows loader and add it to its menu automatically (https://wiki.archlinux.org/index.php/systemd-boot#Adding_boot_entries). As above, you may need to reinstall it if the Windows bootloader installs itself on top of systemd-boot. I originally thought you were just booting an EFI stub kernel, in which case you would have needed some kind of boot manager.
