https://bugzilla.novell.com/show_bug.cgi?id=809038
https://bugzilla.novell.com/show_bug.cgi?id=809038#c17
--- Comment #17 from Neil Rickert 2013-03-14 14:19:59 UTC ---
This is partly guessing. I think I can surmise what is happening.
In my case, there are two hard drives - call the Drive-0 and Drive-1. Window 8
is on Drive-0, and opensuse is on Drive-1.
What seems to be happening, is that the Windows boot is looking for its BCD on
Drive-1 rather than on Drive-0. Presumably, when the UEFI BIOS boots the
grub2-efi bootloader, it is somehow setting Drive-1 to be the default drive,
and Windows is picking that up.
If I do:
efibootmgr -n 04 # set next boot to be Windows
reboot
Windows does boot correctly. It seems to be only when UEFI has started
grub2-efi on Disk1 and grub2-efi has then started Windows, that this goes
wrong. Presumably, if I had use the EFI partition from Disk0, I would not have
this problem.
If my surmise is correct, then I see this as really a Microsoft bug. It's
perhaps even a security bug. When using secure-boot, Windows should be
insisting on getting the correct BCD, and that would be the one on Disk-0.
The only sensible work-around I can suggest, would be for grub2-efi to have an
option to specify what is to be booted next, then reset the system so that the
UEFI BIOS starts the boot to Windows. Perhaps you can pass that upstream as a
suggestion to the grub2-efi maintainers.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.