Rufus developer here. I am indeed seeing sporadic reports from users running into the bug above after they created installation media from the Ubuntu ISO (NB: For most UEFI bootable media generation, what Rufus does is simply copy the ISO content to a FAT32 file system on the USB), and the root of the appears to be be that, even if a Ubuntu GRUB installation does generate mmx64.efi on system install, there is no trace of any mmx64.efi anywhere in the ISO for the initial boot (even in /boot/grub/efi.img).
So I think you guys should make sure that you do include mmx64.efi in /efi/boot/ on the installation ISOs you generate.
Also note that I am seeing similar reports from people who aren't using Rufus at all and are simply copying content to a FAT32 media they created themselves.
Rufus developer here. I am indeed seeing sporadic reports from users running into the bug above after they created installation media from the Ubuntu ISO (NB: For most UEFI bootable media generation, what Rufus does is simply copy the ISO content to a FAT32 file system on the USB), and the root of the appears to be be that, even if a Ubuntu GRUB installation does generate mmx64.efi on system install, there is no trace of any mmx64.efi anywhere in the ISO for the initial boot (even in /boot/grub/ efi.img) .
So I think you guys should make sure that you do include mmx64.efi in /efi/boot/ on the installation ISOs you generate.
Also note that I am seeing similar reports from people who aren't using Rufus at all and are simply copying content to a FAT32 media they created themselves.