I've been helping a user on IRC #ubuntu reporting this problem using the 18.10 ISO installer. In this case during the (first) installer run the PC crashed and rebooted before completing the install.
From then on trying to boot the installer is failing with these error messages:
Failed to open \EFI\BOOT\mmx64.efi - Not Found
Failed to load image \EFI\BOOT\mmx64.efi - Not Found
Failed to start MokManager: Not Found
Something has gone seriously wrong: import_mok_state() failed
"Failed to start MokManager" is reported by the shim's shim.c::check_mok_request().
The cause is the system's EFI NVRAM contains variable names starting "Mok*" - added by the failed installer run.
As a result of theses variables being present shimx64.efi tries to load "mmx64.efi" and due to it not being in the installer's EFI system partition it fails with this report.
The problem now is that there is no easy way to remove these stray variables.
I've been helping a user on IRC #ubuntu reporting this problem using the 18.10 ISO installer. In this case during the (first) installer run the PC crashed and rebooted before completing the install.
From then on trying to boot the installer is failing with these error messages:
Failed to open \EFI\BOOT\mmx64.efi - Not Found
Failed to load image \EFI\BOOT\mmx64.efi - Not Found
Failed to start MokManager: Not Found
Something has gone seriously wrong: import_mok_state() failed
"Failed to start MokManager" is reported by the shim's shim.c: :check_ mok_request( ).
The cause is the system's EFI NVRAM contains variable names starting "Mok*" - added by the failed installer run.
As a result of theses variables being present shimx64.efi tries to load "mmx64.efi" and due to it not being in the installer's EFI system partition it fails with this report.
The problem now is that there is no easy way to remove these stray variables.