Disabling Secure Boot temporarily in order to finish the installation (mmx64.efi is supposed to be installed on disk at the end of the install), or editing an installation image on USB to copy
grubx64.efi in a new file called mmx64.efi Should be good workarounds for this. Please don't run a system-rescue-cd or such custom "rescue" images to manually remove files from /sys/firmware/efi/efivars -- it *can* be done, but it's quite dangerous, likely to brick you system in a way that *can't* be recovered. As per the above, the right fix is to finish the installation and run the real mmx64.efi either by disabling Secure Boot in your firmware (but NOT switching to Legacy boot) or making the mmx64.efi available as a copy of grub. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798171 Title: System fails to boot with \EFI\BOOT\mmx64.efi - Not Found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1798171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
