A Read-Only Pre-Check Workflow for VALORANT Vanguard On-Demand

Vanguard On-Demand changes when the anti-cheat driver loads. It does not remove the kernel driver or reduce the security requirements while a supported Riot title is running. The optional mode is available only on Windows 11 systems that satisfy Riot's Pre-Check security stack.

That distinction matters because a player should not begin by changing firmware. ALVIRAN uses a read-only audit first: inspect the operating system and current security state, let Vanguard identify the missing requirement, and change only the component that is genuinely unsupported or disabled.

What On-Demand changes

In the traditional mode, Vanguard's driver starts during Windows boot. In On-Demand mode, the driver starts with a supported Riot title and does not need to remain loaded between sessions. Windows driver-attestation and hardware-backed protections provide the security evidence required for that later start.

The mode remains optional. A PC that does not qualify can continue using Vanguard's traditional startup behavior. Players who are satisfied with the existing mode do not need to force a firmware migration merely to make the button appear.

How to run the read-only audit

Check the Windows version

Press Windows + R, run winver, and verify that the system uses Windows 11 version 25H2 or newer. An older release does not meet the stated On-Demand baseline.

Inspect System Information

Run msinfo32 and record these values without changing them:

• BIOS Mode should report UEFI rather than Legacy
• Secure Boot State should report On
• Virtualization-Based Security should be active
• Kernel DMA Protection should be available and enabled

Verify TPM 2.0

Run tpm.msc, confirm that the TPM is ready, and check that the specification version is 2.0. Do not clear the TPM as a troubleshooting shortcut. Clearing it can affect protected credentials and recovery workflows.

Check Memory Integrity

Open Windows Security, Device security, then Core isolation details. Memory integrity is the Windows interface associated with HVCI. If an incompatible driver blocks it, identify and update that driver instead of forcing the setting with a registry edit.

Run Vanguard Pre-Check

Use Vanguard's own tray workflow as the final decision. Windows screens provide useful diagnostics, but Vanguard evaluates the complete operating-system, driver, firmware and hardware combination.

Safe setup sequence

1. Install supported Windows and Riot/Vanguard updates.
2. Restart before judging the Pre-Check result.
3. Resolve Windows-side driver or Memory Integrity issues first.
4. Use documentation for the exact motherboard, laptop or prebuilt system before entering firmware.
5. Change only the specific missing requirement.
6. Restart and confirm the new state in Windows.
7. Run Vanguard Pre-Check again.
8. Enable On-Demand only after every required check passes.

This sequence preserves evidence. If Pre-Check changes from failed to passed after one adjustment, the cause is known. If several firmware options are changed together, a later boot or security problem becomes much harder to reverse.

Why the requirements exist

• UEFI Secure Boot protects the startup chain from untrusted boot components.
• TPM 2.0 provides hardware-backed measurements and attestation support.
• VBS isolates sensitive Windows security functions.
• HVCI or Memory Integrity enforces code integrity using virtualization-based protection.
• IOMMU or Kernel DMA Protection limits unauthorized direct-memory access from devices.
• Windows 11 25H2 supplies the driver-attestation capability required by the new lifecycle.

The important point is not memorizing abbreviations. It is understanding that On-Demand depends on a complete trust chain. One enabled feature does not compensate for another missing layer.

Unsafe shortcuts to avoid

• do not flash a BIOS from a generic guide
• do not disable Legacy or CSM without confirming the boot configuration
• do not clear TPM data without recovery preparation
• do not force Memory Integrity around an incompatible driver
• do not copy registry values intended for another motherboard
• do not treat On-Demand as mandatory for playing VALORANT

FAQ

Why does the On-Demand option not appear?

The system may be missing the required Windows version, Secure Boot, TPM 2.0, VBS, HVCI, IOMMU or a compatible driver state. Vanguard Pre-Check should identify the failing category.

Where can I see every requirement and setup step?

The ALVIRAN Vanguard On-Demand requirements and Pre-Check guide explains the security stack, read-only checks, safe setup sequence and troubleshooting path in detail.