Dual booting Leap 15 and Windows using EasyBCD

I’ve been building dual boot systems for many years,
most recently with 42.3
However Leap 15.1 with Grub2 EFI basically “hijacks” the boot loader
and I can find no way to build a native boot menu using EastBCD.

Leap 15.1 is not seeing the installation of Windows 7 or Windows 10
and I can no longer boot to Windows after I install Leap 15.1
Before installing SUSE, Windows 7 and 10 dual boot fine with
EasyBCD, but when I install SUSE Leap15, I can lo longer boot to
Windows and the installer does not see the two operating systems.
How do I install Leap 15 so it sees Windows and permits me to build
a native boot menu with EasyBCD ?

My partition setup is this:
150gig Windows-7
150gig Windows-10
150gig OpenSUSE 15.1

Extended Partition

Logical:500meg /boot
Logical:12gig swap
Logical: [The balance as NTFS]

If grub efi is running then you have booted/installed openSUSE in UEFI mode? But your setup appears to be Legacy boot… since you have a /boot and logical partitions.

The short answer, as indicated by Malcolm, is that you made a mistake during install. You booted the installer in UEFI mode. You should have boot for legacy booting (MBR/BIOS booting).

The long answer, is that you can reinstall grub to boot in legacy mode anyway.

Use Yast bootloader. It will show the boot loader as “GRUB2 for EFI”. You will need to change that to “GRUB2”. Then you will need to set where the boot code is to be installed. The safest choice is probably to boot from the MBR. So check the box “Boot from Master Boot Record”. All other boxes on that screen should be unchecked.

Hmm, before you try that, make sure that your disk was not repartitioned. Maybe post the output from:

fdisk -l

and wait for us to respond before you go ahead with the bootloader change.

Thanks both.

I used Clonezilla and cloned my Win-7 / Win10 dual boot system with the extra partitions to another drive and the did a test install based on your recommendations.
It is now running fine with Grub2 and booting from MBR. However it does not see the two Windows partitions.
My goal would be to rebuild the MBR back to windows-compliant and use EasyBCD to create the three-item menu
Windows 7 Professional
Windows 10 Professional
OpenSUSE Leap v15.1

Attached and below are my build

Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: TOSHIBA HDWD105
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xaba9c1e4

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 63 307210994 307210932 146.5G 7 HPFS/NTFS/exFAT
/dev/sda2 307210995 614421989 307210995 146.5G 7 HPFS/NTFS/exFAT
/dev/sda3 614421990 921632984 307210995 146.5G 83 Linux
/dev/sda4 921632985 976768064 55135080 26.3G f W95 Ext’d (LBA)
/dev/sda5 921633048 922661144 1028097 502M 83 Linux
/dev/sda6 922661208 947240594 24579387 11.7G 82 Linux swap / Solaris
/dev/sda7 947240658 976768064 29527407 14.1G b W95 FAT32

/dev/sda1 on /windows_7
/dev/sda2 on /windows_10
/dev/sda3 on /
/dev/sda5 on /boot
/dev/sda7 on /storage

My boot selections are
Boot from partition
Boot from MBR

From openSUSE as root user if you run the command;


Does it detect the two windows installs?

If it wasn’t already clear,
You shouldn’t use EasyBCD at all.
EacyBCD is a recommended tool to modify the Windows BCD, and is not the same as BCD.

When you install a Linux distro, it will use a compeltely different bootloader (grub2).
When your machine initially boots, it will load one or the other bootloader, as you’ve found what you did loads grub2 and not BCD as your first bootloader.
You’re setting up what is called “chainloading” when one bootloader will have entries to boot its native OS (openSUSE in this case) and then another entry will point to the second bootloader (BCD in your case).
The second bootloader (BCD in your case) will never be altered, so put away your EasyBCD tool, you won’t use that at all.

Ordinarily, the openSUSE install will run os-prober to discover the existing Windows OS installation and create a grub2 entry for chainloading, if that failed for some reason then you may need to create that entry manually.

AFAIK no alterations to MBR or EFI should be required.