Aorus 16X 9SG (2024) – Rolled back to BIOS F9, how did you get CA2023 keys working?
Rolled back from FF2 to F9 on my Aorus 16X 9SG (2024) because FF2 is unstable (constant CRITICAL_PROCESS_DIED, INACCESSIBLE_BOOT_DEVICE, VMD issues) and removes undervolt/OC options.
Now I’m stuck: Windows 11 bootloader is signed with CA2023, but BIOS F9 only has CA2011.
Trying to boot with Secure Boot enabled gives signature violation.
The only options in BIOS are “Delete keys” (Setup Mode) or “Enroll factory default keys” (which just puts the old CA2011 keys back).
How did you guys manage to get CA2023 certificates into F9?
Any working method without staying on the broken FF2?
Currently forced to run Windows 11 with Secure Boot disabled.
Update:
Got a reply from GIGABYTE eSupport (#2051503).
They completely ignored everything I wrote and just sent me the link to BIOS FF2 again.
Bravo GIGABYTE, excellent support work.
So, conclusion for everyone:
It is not possible to properly update CA2023 certificates on BIOS F9 on the Aorus 16X.
The only way to enable Secure Boot is “Enroll factory default keys”, which always overwrites everything with the old CA2011 keys.
BIOS FF2 is unstable on my system (and probably not only on mine). Common issues many of us are seeing:
- Frequent CRITICAL_PROCESS_DIED (0xEF)
- Severe performance drop caused by Intel VMD (poor throughput + high latency)
- Frequent INACCESSIBLE_BOOT_DEVICE
- CLOCK_WATCHDOG_TIMEOUT
If Secure Boot is not critical for you — just roll back to F9.
It is significantly more stable than FF2 and still has the advanced undervolt/OC menu that was removed in FF2.