Hi guys, I have a extremely annoying issue with grub2, or more precisely grub2-once. I have two systems that both run a dual boot setup between Leap 15.0 and Windows 10. Both boot from UEFI with secure boot turned OFF. One of them i can choose what to boot next from the command line with grub2-once <number>, and it works just fine: I do "sudo grub2-once 3; sudo systemctl reboot" and I end up in windows, and on next reboot I get my grub menu again The other one, whenever I do the same sequence of "sudo grub2-once 3 ; sudo systemctl reboot" I bot into windows, but then I keep booting into windows - grub2 is not working anymore so the boot sequence defaults to the original windows bootloader... The only differences between the two systems that I can think of are: the working system has one harddisk, the nonworking one has two harddisks (but none of the actual OS installed on the second disk, in both windows and linux) the working system has windows 10 home, the broken one has windows 10 pro any ideas/hints? Cheers MH -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org