Ubuntu
grub2 package

  1. Bug #1845289
  2. Comment #13

Comment 13 for bug 1845289

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

This bug is *not* a duplicate of 1839317; since we're not looking at ARM-based systems here.

Could you please update your grub-efi-amd64 and grub-efi-amd64-signed packages (well, make sure your system is fully up to date), then run:

sudo grub-install -v

And include the output here.

Not all the failures here are for the same causes:

Joseph Maillardet (jokx), it looks like the packages are not all installed correctly, though I am not sure why (grub-install will tell); so you are booting GRUB directly, not through shim, so Secure Boot is being skipped in fun ways. This means chainloading Windows from GRUB is unlikely to work.

Ivan, it sounds like your Windows no longer has a bootloader -- otherwise you should still see "Windows Boot Manager" work to boot Windows. If you see GRUB again, then it means something went missing on disk, in which case, per my comment #6, we would need to see what is on disk under /boot/efi.