This issue has me stumped for hours, and I can't figure out WHY this is happening.

So, here's the thing: I want to use Secure Boot, but I don't care about the "securityness" of Secure Boot, I only care about having it working to please Windows, and I don't want to do the whole dance of "go into BIOS, enable/disable Secure Boot, change boot order, save and reboot".

My solution that worked was to use shim-signed + mokutil --disable-validation like this:

sudo grub-install --target=x86_64-efi --efi-directory=/efi --bootloader-id=ArchLinuxGRUB --modules="tpm" --sbat /usr/share/grub/sbat.csv --no-nvram sudo cp /usr/share/shim-signed/shimx64.efi /efi/EFI/ArchLinuxGRUB/bootx64.efi sudo cp /usr/share/shim-signed/mmx64.efi /efi/EFI/ArchLinuxGRUB/ sudo mokutil --disable-validation sudo efibootmgr --create --disk /dev/nvme0n1 --part 1 --label "ArchLinuxGRUB" --loader '\EFI\ARCHLINUXGRUB\BOOTX64.efi' 

And this has worked for me in the past (last time was around ~August), but for some REASON this is not working for me anymore?!

Here's what happens:

1. I do all of the commands above
2. I boot into the BIOS
3. Enable secure boot
4. Reboot
5. Boot into the ArchLinuxGRUB
6. It boots into the MOK Manager, I select to "Change Secure Boot Status"
7. It asks for three random pieces of the configured password
8. It asks if I want to disable secure boot verification, I select yes
9. I select to Reboot
10. The system reboots, it boots into GRUB, but when selecting to boot into Arch Linux, it goes up until "Loading initial ramdisk" and then it "bootloops" back into the GRUB boot menu again.

If I disable secure boot, it boots correctly, even if I'm booting through the shim.

The weird part is that it has worked before, but now I can't figure out what I'm doing wrong, which is why I'm here :)