Hi,
Thank you for sharing your question. I understand how concerning it is when your PC enters a BIOS loop immediately after enabling Secure Boot, especially when you need both Secure Boot and TPM 2.0 to run certain games. It’s definitely frustrating to feel stuck at startup, and I’m here to help you work through this.
This issue usually happens when Windows isn’t configured to boot in a Secure Boot–compatible mode, even if your BIOS is set to UEFI and your disk is already using GPT. Secure Boot requires that Windows use trusted boot files, and if the bootloader, drivers, or system configuration are not aligned with Secure Boot requirements, the firmware may fail to hand off control to Windows, causing it to return to the BIOS repeatedly.
To resolve this, ensure that Secure Boot is set to Standard rather than Custom so the system uses the default Microsoft keys. Confirm that CSM or Legacy Boot is completely disabled, because Secure Boot cannot run alongside those settings. If the bootloader was installed in a non‑Secure Boot state, running a startup repair or rebuilding the boot files from Windows Recovery can allow the system to load properly with Secure Boot enabled. In some cases, clearing Secure Boot keys and reloading factory defaults in BIOS fixes trust‑related issues that cause looping behavior. TPM 2.0 does not normally cause boot loops, so once Secure Boot is fully aligned with your Windows installation, both features should work without conflict.
To help narrow this down, may I know if you installed Windows before or after enabling UEFI and GPT, or if you recently changed any BIOS security settings besides Secure Boot?
Feel free to follow up with any details or questions I’m here to help you get your system booting normally with Secure Boot and TPM 2.0 enabled.
I hope this helps.
Best Regards,
Noel