[Bug 2078307] Re: Grub 2.12 in Oracular is unable to boot Windows using chainloader

Mate Kukri 2078307 at bugs.launchpad.net
Wed Oct 9 21:50:59 UTC 2024


Hmm that looks extremely weird. It seems like GRUB is deciding to
enforce NX policy on your machine despite it clearly booting from the
shim that is requesting it not to...

One hunch I have is that maybe shim doesn't export MokPolicy with UEFI
Secure Boot disabled, and we accidentally always enforce NX when UEFI
Secure Boot is off.

Maybe can you try enabling UEFI Secure Boot in your UEFI configuration?
(it's sometimes called Secure Boot mode "Windows UEFI mode" instead of
"other os")

-- 
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/2078307

Title:
  Grub 2.12 in Oracular is unable to boot Windows using chainloader

Status in cd-boot-images-amd64 package in Ubuntu:
  Fix Released
Status in cd-boot-images-arm64 package in Ubuntu:
  Fix Released
Status in cd-boot-images-ppc64el package in Ubuntu:
  Fix Released
Status in cd-boot-images-riscv64 package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  Fix Released

Bug description:
  I am using Shim 15.8 in combination with GRUB2.12. One of the GRUB
  menu items, chainloader /efi/Microsoft/Boot/bootmgfw.efi, fails to
  boot, while it works correctly with GRUB2.06. Below is a screenshot of
  the error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cd-boot-images-amd64/+bug/2078307/+subscriptions




More information about the foundations-bugs mailing list