The error indicates Secure Boot is enabled in firmware, but Windows Boot Manager is not trusted by the current Secure Boot configuration. The goal is to restore the default Secure Boot keys and then re‑enable Secure Boot so Windows can boot normally and Valorant’s anti‑cheat requirements are met.
Follow these steps in order:
- Reset Secure Boot keys to factory defaults
- Restart the device and enter the UEFI/BIOS setup (typically by pressing a key such as F1, F2, F12, Esc, or similar during power‑on; check the Lenovo documentation for the exact key).
- Go to the Secure Boot section.
- Use the option to Reset Secure Boot keys to factory defaults (or similar wording). If there are both Clear and Reset options, use Reset, not Clear. The goal is to restore the manufacturer’s default Secure Boot variables and keys.
- Save changes and exit.
- Test boot with Secure Boot temporarily off
- Go back into UEFI/BIOS.
- Set Secure Boot to Disabled.
- Save and boot into Windows.
- Once in Windows, verify it starts normally and that the system disk is still the primary boot device.
- Rebuild Windows boot files if needed
If the device still has trouble booting when Secure Boot is on, rebuild the EFI boot files:
- Boot into Windows with Secure Boot disabled.
- Open an elevated Command Prompt (Run as administrator).
- Run these commands one by one, pressing Enter after each:
mountvol s: /s del s:\*.*/f /s /q bcdboot %systemroot% /s S: - Confirm that
BCDBootreports “Boot files successfully created.” - Restart back into Windows (still with Secure Boot disabled) to confirm it boots.
- Re‑enable Secure Boot
- Restart and enter UEFI/BIOS again.
- Ensure the firmware is set to UEFI (not Legacy/CSM) and that the Windows drive is the first boot option.
- In the Secure Boot section, set Secure Boot to Enabled.
- If there is a mode selection (such as Standard / Windows UEFI mode / Custom), choose the standard or Windows‑specific mode so the built‑in keys are used.
- Save and exit.
- Confirm that Windows now boots without the “Windows Boot Manager has been blocked by the current security policy” message.
- If Windows still will not boot with Secure Boot enabled
- Turn Secure Boot off again so the device is usable.
- Repeat the key reset to factory defaults in firmware.
- If the problem persists even after rebuilding boot files, perform a Windows reinstall from recovery media with Secure Boot enabled, then re‑enable Secure Boot after installation if the installer temporarily changes it.
- If none of these steps work, contact the device manufacturer (Lenovo) for firmware‑specific guidance, as recommended when Secure Boot cannot be re‑enabled successfully.
Once Windows boots normally with Secure Boot enabled and UEFI mode active, Valorant should pass its Secure Boot check (assuming TPM 2.0 is already enabled and active).
References:
- How to manage the Windows Boot Manager revocations for Secure Boot changes associated with CVE-2023-24932
- Disabling Secure Boot
- Secure the Windows boot process
- Windows 11 and Secure Boot
- Secure boot state is still off tried alot of things - Microsoft Q&A
- why don't i have the 2023 secure boot keys - Microsoft Q&A
- Can't enable secure boot - Microsoft Q&A