Hey! I finally got around to trying out what you said. I got it running and played around for a bit, and decided to dual boot at least for now. I powered off, ejected the usb, went back to windows to clear up some disc space and went to boot up Mint again, and got greeted with this:
Failed to open \EFI\B00T\mmx64.efi - Not Found
Failed to load image ??: Not Found
Failed to start MokManager: Not Found
Something has gone seriously wrong: import mok-state() failed: Not Found
I disabled secure boot but it’s still giving me this. It shows it for a few seconds and then turns off. Any suggestions? I’m not sure why it was working before and isn’t now. It’s a bit frustrating.
Leads me to believe that this is indeed something Secure Boot related (or rather, the system looking for files related to secure boot that aren’t being found). Given that you were able to boot it initially, and then it stopped after booting back into Windows, I suspect some shenanigans here possibly from Windows. When you were freeing up disk space, did you use Windows’ partition manager (I think its just called “Disk Management”) at all and modify any partitions?
Just to confirm, is it just Mint that doesn’t boot, or does Windows also not boot? One of the nicer things about UEFI is how you can have multiple boot loaders installed, where as back in the (regular) BIOS days with MBR, only one boot loader could be installed.
That is all to say, try entering your PC’s boot menu (so the same menu you initially used to boot the Mint USB), you should have multiple boot options from your PC’s drive - though Windows’ boot loader usually identifies itself as “Windows Boot Manager”. If you choose that option (or if its not “clickable”, you should be able to switch the order so that its first - then reboot normally), does it at least boot back into Windows?
I ended up getting it to work. I’m still not sure what the issue was, but I wiped the USB and tried using Ventoy to flash instead and that seemed to work. No idea why.
Hey! I finally got around to trying out what you said. I got it running and played around for a bit, and decided to dual boot at least for now. I powered off, ejected the usb, went back to windows to clear up some disc space and went to boot up Mint again, and got greeted with this:
Failed to open \EFI\B00T\mmx64.efi - Not Found Failed to load image ??: Not Found Failed to start MokManager: Not Found Something has gone seriously wrong: import mok-state() failed: Not FoundI disabled secure boot but it’s still giving me this. It shows it for a few seconds and then turns off. Any suggestions? I’m not sure why it was working before and isn’t now. It’s a bit frustrating.
Hmm, that’s quite an interesting one. The:
Leads me to believe that this is indeed something Secure Boot related (or rather, the system looking for files related to secure boot that aren’t being found). Given that you were able to boot it initially, and then it stopped after booting back into Windows, I suspect some shenanigans here possibly from Windows. When you were freeing up disk space, did you use Windows’ partition manager (I think its just called “Disk Management”) at all and modify any partitions?
Just to confirm, is it just Mint that doesn’t boot, or does Windows also not boot? One of the nicer things about UEFI is how you can have multiple boot loaders installed, where as back in the (regular) BIOS days with MBR, only one boot loader could be installed.
That is all to say, try entering your PC’s boot menu (so the same menu you initially used to boot the Mint USB), you should have multiple boot options from your PC’s drive - though Windows’ boot loader usually identifies itself as “Windows Boot Manager”. If you choose that option (or if its not “clickable”, you should be able to switch the order so that its first - then reboot normally), does it at least boot back into Windows?
I ended up getting it to work. I’m still not sure what the issue was, but I wiped the USB and tried using Ventoy to flash instead and that seemed to work. No idea why.