Windows 11 and Arch Linux both boot with Secure Boot enabled using sbctl and systemd-boot, but Valorant stopped launching after an update. Vanguard's precheck passes. Restoring the firmware's factory Secure Boot settings lets the game run, but then Linux won't boot. What should I check?
Valorant stopped launching after an update on my Linux dual boot. Is it the Secure Boot keys?
Answers
The factory reset result points toward the enrolled Secure Boot keys or related firmware settings, but it doesn't prove exactly what Vanguard is checking. Passing the precheck doesn't necessarily mean the game will accept every part of the configuration when it launches.
Compare the firmware settings and enrolled keys before and after restoring defaults. Save a record of your current configuration first, and make sure you have a recovery route for Linux before changing keys again. The exact Vanguard error text would also help narrow this down.
Reply to this answer
I'd avoid assuming the recent Linux initramfs or TPM changes caused it just because the timing is close. The useful clue here is that changing firmware Secure Boot settings affects Valorant, even though both operating systems boot.
Check whether the firmware offers a way to retain the factory keys alongside the keys needed for your Linux boot setup. The available options vary by machine, and changing them can leave Linux unbootable, so have recovery media ready.
Reply to this answer
This may be a compatibility issue that needs a Vanguard support answer rather than another round of key rotation. Send support the exact error, Windows version, firmware Secure Boot configuration, and the fact that factory defaults change the result. Don't include private signing keys or other sensitive key material.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions