Recently, I installed Windows 10 on my main machine - later discovered it demolished my whole Linux boot partition:

├─sdb1 ext4   Root        07a703e4-173a-4e54-b425-baa69a220a64 /
├─sdb2 vfat               2C45-FE61                            /boot
├─sdb3 ext4   Home        00477b16-d04d-4cc7-bb56-32138146b74d /home
├─sdb4 swap   Swap        578c2f2d-1a07-4bae-a235-dbf52dae300f [SWAP]
└─sdb6 ntfs   Win_OS      9292422592420E63                     /media/Win_OS

I got Syslinux and my Arch working, but now I can't find a way to succesfully make a Syslinux entry to boot into the Windows. Though, If I choose "Windows Boot Manager" from the MB boot menu, it boots just fine.

My current syslinux.cfg: (well, part of it)

    MENU LABEL Arch_64
    LINUX ../vmlinuz-linux
    APPEND root=UUID=07a703e4-173a-4e54-b425-baa69a220a64 rw
    INITRD ../initramfs-linux.img

    MENU LABEL Windows_10
    COM32 chain.c32
    APPEND hd1

Edit 1#:

I forgot to mention, I also installed a UEFI syslinux in the /EFI/ folder, alongside windows' Microsoft and Boot folders, which, again, works for Linux, but not for Windows - no matter if I use UUID, Label, disk and partition number...

  • The last I checked (which was admittedly quite a while ago), the EFI version of SYSLINUX could not chain-load other EFI-mode boot loaders, and therefore could not be used to dual-boot with Windows. Unless this has changed, you'll need to use the EFI's built-in boot manager or switch to another boot manager, such as rEFInd, gummiboot/systemd-boot, or GRUB, to dual-boot Windows and Linux. – Rod Smith May 14 '17 at 1:59
  • 1
    @RodSmith Yes, indeed. I actually found out a few hours ago on my own when reading the ArchLinux wiki: "UEFI Syslinux does not support chainloading other EFI applications like UEFI Shell or Windows Boot Manager" wiki.archlinux.org/index.php/… – niraami May 14 '17 at 16:54

After some more digging, I found a small paragraph on the ArchLinux Wiki stating:

UEFI Syslinux does not support chainloading other EFI applications like UEFI Shell or Windows Boot Manager

And indeed, even after a feature request in 2013, they still haven't implemented this very important feature.

Solution was to install a different EFI-chainload-capable bootloader, such as GRUB. Installation guide for Arch here.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.