New install won't boot on its own and requests recovery key every time it does boot.

[dbfhvsfvdg]

Describe the bug
I have an Acer A715-76G-54LL with BIOS version 1.56. I've created a boot drive using Rufus and enabled both Secure Boot and TPM. This is a single boot system and the pc has had its M.2 wiped, so I can start from scratch. I have never done dual boot on it.
I plug the USB stick and use F12 to boot from it.
The GRUB menu shows up with three options. "Aeon 20251204", "EFI Default Loader" and "Reboot Into Firmware Interface" (a.k.a. BIOS).
I select "Aeon 20251204" and the installer proceeds as normal, up to the screen with the QR code and the recovery key. I click ok, it tells me the installation is complete (it doesn't matter if I now remove the USB or not) the system reboots and then, one of two things happens.

1. If I let it boot into "EFI Default Loader", it freezes on either a fully black screen, or a black screen with the Acer logo and nothing more will ever happen.
2. If I manually bring up the GRUB menu again and select "Aeon 20251204", then it'll ask me for the recovery key. I enter the key and I can then continue configuring Aeon as normal. But every time I reboot, I have to manually select "Aeon 20251204" (or it'll try to boot into "EFI Default Loader" and freeze on the black screen) and it will always ask me for the recovery key.
   If I re-measure boot integrity, it'll fail.
   If I reenroll the TPM key, I get a lot of error messages about "garbage data" but eventually it'll tell me it's succeeded.
   If I reboot though, the GRUB menu will gain a duplicate entry of "Aeon 20251204" with the suffix "0.X" on the end, where "X" will be the number of times I've reenrolled the TPM key.
   Selecting the duplicate entry, will again ask me for the recovery key, while selecting "Aeon 20251204" will either ask for the recovery key or give a "PCR 15" error and shutdown.
   If I go to the BIOS and check the boot device order, I have two options. "Aeon Boot Manager" and "HDD0".
   If I set Aeon Boot Manager as the default boot device, then the pc will get to the black (or Acer logo) screen and freeze.
   If I set HDD0 as the default boot device, then it'll give the following error messages:
   "Could not create SbaLlevIRT: Volume Full", "Could not create MokListTrustedRT: Volume Full" and "Something has gone seriously wrong: Import_mok_state() failed: Volume Full"

To Reproduce
Steps to reproduce the behavior:
Attempt to install a fresh version of Aeon 20251204 on an Acer A715-76G-54LL

Expected behavior
The installation should complete and it should be able to boot into Aeon, on its own, without any other user input or error messages.

tik log
None of the error messages say anything about a "tik.log" and I could not check anyway, since the entire stick is formatted with Linux only partitions, that can't be read on Windows or Android, leaving me no way to check its contents.

/etc/os-release
Please provide the output of cat /etc/os-release

Additional context
Add any other context about the problem here.
The system has a single M.2 drive and has never been dual booted. The system has used Windows 11 before.

[kevin-sakemaer]

Is there a way to improve that the recovery key is very long and not super friendly to enter every time we are booting?
I don't have problem to boot but it ask me for the key on every boot.