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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078307 Title: Grub 2.12 in Oracular is unable to boot Windows using chainloader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cd-boot-images-amd64/+bug/2078307/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
