[Bug 1839317] Re: Grub fails to chainload the Windows Boot Manager
Dmitry-a-durnev
1839317 at bugs.launchpad.net
Sat Sep 21 09:51:22 UTC 2019
Tried with
set debug=chain
got the following messages (grub 2.04-1ubuntu5, AMD64 arch, ubuntu
19.10):
loader/efi/chainloader.c:1057: linuxefi_secure_validate: 1
loader/efi/chainloader.c:262: No shimlock protocol loader/efi/chainloader.c:537: Secure boot is not enabled
alloc magic is broken at 0x7bf9b340: 0
Aborted. Press any key to exit.
Press any key - returns to grub menu. But once I pressed <return> and it
successfully booted win 10! At other times there was no 'alloc magic'
error and no pause to press any key: just returned to boot menu
instantly.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1839317
Title:
Grub fails to chainload the Windows Boot Manager
Status in grub2 package in Ubuntu:
Confirmed
Bug description:
After an update to 2.04 Grub fails to chainload into Windows.
When selecting the menu item to boot into the Windows Boot Manager,
the menu flashes and returns.
When trying to chainload/boot via the Grub command line, nothing
happens and the prompt reappears.
When using the same commands in an earlier version (on a bootable USB
stick) Windows sparks into life.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1839317/+subscriptions
More information about the foundations-bugs
mailing list