[SOLVED] Why does debian 10 try to access mmx64.efi with Secure Boot enabled when no such file exists

Tried to boot debian live from a USB flash drive that was made with Rufus. It produced this error:

Failed to open /EFI/BOOT/mmx64.efi - Not found

Tried to copy /EFI/boot/grubx64 to mmx64.efi in the same directory and it showed a grub menu but when you chose anything it produced this error:

Error /live/vmlinuz-4.19.0-6-amd64 has invalid signature 
Error you need to load the kernel first

Tried to install shim-signed with apt in a VM booting from the debian live ISO image in order to get a mmx64.efi and copy it to the USB flash drive. It produced this error:

Verification failed (0x1A) security violation

Why on earth would they make debian so hard to start with Secure Boot enabled?

By the way, with MX and AntiX it was easy as breeze. So it was with Peppermint but that is Ubuntu based. Debian derivatives, they all seem to lack Secure Boot support except MX and AntiX, and I tried lots! How can this be?

Solved by copying mmx64.efi from /EFI/boot/ in a LUbuntu USB flash drive to the same directory in a Debian one, both created with Rufus.

Why on earth would they make debian so hard to start with Secure Boot enabled?

I think the link below explains it and it is not the people at Debian that cause the problem, AFAIK Secure Boot is basically only used to protect windows bootloader. It is necessary to pay a fee to microsoft to get a key and I imagine Debian developers chose not to do so.

https://www.howtogeek.com/175641/how...h-secure-boot/

Secure Boot now works even without that mmx64.efi file! It appears that the first time is was accessed something was changed in the EFI settings to make it unnecessary. It is as if the manufacturer has put obstacles to discourage installation of fully open source debian and derivatives but allow partly closed source ubuntu and derivatives.