After installation of SUSE no more boot to Windows 10

I am still a newbie to Linux although I already had several attempts to get aqainted to this great system.
I have an notebook with EFI-bios support.
Windows 10 created a EFI boot partition in /dev/sda3.
When I start the computer I get the Linux boot options screen. If I then choose the Windows bootloader, I get an error message that something (i.e. boot/bsd) is corrupt and I am advised to use the Windows 10 boot disk to repair the Windows installation - that did not work.
Reading the thread about dual boot problems with Tumbleweed that I learnt that I should mount the Windows EFI partion to /boot/efi.
To automate the mounting process I should edit /etc/fstab that I once did and nearly crashed my Leap 42.1 installation. Only after I deleted my manually added lines in fstab my installation would boot again.
So please could anyone send me the correct syntax to be added to fstab.
I also read the advise to create an EFI partion for Leap 42.1 which I did not do, because at the time of installation I did not no about this fact/possibility.

Could anyone advise how to change my setup (in language for dummies) to have both systems boot correctly.
If you need any further information do not hesitate to ask for it, as I presently do not know what information I shoud send beforehand.


First: get your W10 up and running again. Restart W10 from DVD and open a repair console:
> bootrec /fixmbr
> bootrec /fixboot
(if you don’t know how to do this, Google is your friend…)

Second: note your partition layout, reinstall Suse BUT do NOT install grub into the MBR but into the / Partition (or /boot Partition if you have it separated).
After that your PC will reboot into W10

Third: download and install EasyBCD in W10 and set up a dual boot load menu for W10 and Suse to start from the Suse Partition (select “old” grub, it is faster)
After that your PC will reboot into the new W10 boot menu. Selecting the menu entry for Suse starts Suse’s Grub2 (from where you could also hop back to W10) and only then you’ll finish the SUSE installation and log into your first user session.

After a while you can decide which is your first OS of choice and set its boot partition active. This scheme had been working well for me since years.

Sorry if the install is EFI and it should be you must have an efi boot partition formatted as FAT. DO not mix boot modes ie do not install one OS as EFI and the other as legacy. That just leads to problems.

If installing in EFI mode then you should boot the install media in EFI mode NOT legacy

The EFI boot partition should be mounted as /boot/efi. That is where the boot code will go. The installer should do this by default if it is booted in EFI mode. YOu can tell what mode by the installer boot menu if there are selections along the bottom you have booted in legacy mode. If nothing along the bottom in EFI mode

In EFI mode there is no putting grub anywhere that is a legacy mode thing not an EFI mode thing

Did you create second EFI partition as part of Linux install? Could you paste output of “fdisk -l” as root in Linux?

It seems that you installed opensuse for legacy booting, while windows is setup for UEFI booting. The two don’t mix.

The install DVD should be bootable both in legacy mode and in UEFI mode. How your installed system boots will depend on how you booted the installer.

I suggest you experiment with booting the installer in UEFI mode. If you are able to do that, then perhaps reinstall. Or maybe mount the EFI partition at “/boot/efi” (do that with Yast partitioner so that it automatically mounts). Then boot the installer in UEFI mode and do an upgrade install, where you should be able to switch booting to using “grub2-efi”.