Watch the video:
0:00 - Explanation
1:03 - Check Secure Boot/UEFI in Windows
1:30 - What we need to check in BIOS
2:08 - Navigating your BIOS
3:35 - Save and restart
4:11 - Verify settings in Windows
What’s wrong
If you’re seeing an error message in Vanguard (Valorant anti-cheat software) that says “Vanguard is out of compliance with the current system settings” or “VAN9003,” it’s likely due to a problem with your computer’s Secure Boot or UEFI settings. This error is particularly common on Windows 11, but the solution is generally the same for any version of Windows.
Secure Boot
The first step is to check that Secure Boot is enabled. You can do this by pressing Start+R
, and then typing in msinfo32
, then hitting “Enter”. This will bring up the “System Information” window, where you should see a section called “BIOS Mode” that should say “UEFI”.
You should also see a section called “Secure Boot State” that should say “On”.
Bios
If Secure Boot is not enabled, you’ll need to enter your computer’s BIOS settings to change this. The key to enter BIOS settings will vary depending on your motherboard or BIOS software, but it’s generally one of the F1-F11 or Delete keys. Once you’re in the BIOS settings, you’ll need to navigate to the Secure Boot option and enable it. You may also need to disable Compatibility Support Module (CSM) and set your boot mode to UEFI.
Another setting that may be causing issues is the TPM (Trusted Platform Module) chip. Make sure it’s enabled and set to TPM version 2.
After making these changes, save them and restart your computer. You should now be able to run Vanguard without seeing the “Out of compliance” error message.
TPM Enabled:
CSM (Disabled):
Secure Boot (Enabled):
Please note that enabling Secure Boot may cause issues with dual booting. Also, please note that your specific steps may vary based on your motherboard or BIOS software, it is recommended to check the manual or do a quick search to find the specific steps for your system.
Verify
Re-open msinfo32
and double-check that things are set up properly.
At this point, the error should be fixed. Nice and simple, assuming your hardware is compatible.
If you can’t use TPM at all, and settings alike your only option may be downgrading to Windows 10 - Where this isn’t a requirement, for some reason…