Indeed, this is wrong. grub is not an image we get signed with the
Microsoft keys, and so is not going to be recognized as a valid
signature by firmware unless you re-sign it yourself and add the key you
used to the firmware.
With things as they are, it doesn't look like you'd be able to
successfully boot Windows anyway (since you'd likely be missing extra
options normally passed to the Windows Boot Manager). What I see here is
that the ubuntu entry exists (so it should be possible to pick what to
boot via F12 or some other keyboard shortcut appropriate to your
system), but it's been mangled by the firmware. There isn't much we can
do if firmware breaks the boot entries, except tricking it into doing
the right thing by putting files in a different location.
The correct file to use as a BootEntry binary is shimx64.efi, not
grubx64.efi. You may try the same bcdedit command with that file.
Otherwise, please try to fix Windows using the recovery options if you
can (repair boot, etc. as per the AskUbuntu question or Windows
documentation). From that point, you would be able to reinstall Ubuntu
or boot from an Ubuntu CD/USB and reinstall grub, which will create the
right boot entry (which is what Boot0000 should be in this bug's
description).
** Changed in: shim (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641793
Title:
Invalid Signature detected -- must uncheck secure boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1641793/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
