{"id":6488,"date":"2026-06-26T10:09:44","date_gmt":"2026-06-26T07:09:44","guid":{"rendered":"https:\/\/www.gamermarkt.com\/blog\/?p=6488"},"modified":"2026-10-26T03:02:27","modified_gmt":"2026-10-26T00:02:27","slug":"riot-vanguard-on-demand-mode-how-to-enable","status":"publish","type":"post","link":"https:\/\/www.gamermarkt.com\/blog\/riot-vanguard-on-demand-mode-how-to-enable\/","title":{"rendered":"Riot Vanguard Windows 11 25H2 requirement: On-Demand setup and fixes"},"content":{"rendered":"\n

Updated 26 October 2026: the page now opens with the Windows 11 25H2 message that most readers search for. Riot’s requirement list is unchanged since the 24 June announcement.<\/em><\/p>\n\n\n\n

Riot Vanguard asks for Windows 11 25H2 or later because its On-Demand mode depends on a Windows feature that older builds lack. Vanguard On-Demand loads Riot’s anti-cheat driver when you start a Riot game and unloads it when you close the game, in place of loading it at Windows startup. To use it, your PC must pass the Vanguard Pre-Check: Windows 11 25H2 or later, UEFI boot with Secure Boot, TPM 2.0, Virtualization-Based Security with HVCI, and IOMMU. The mode is optional; if you change nothing, Vanguard keeps working as before.<\/p>\n\n\n\n

Why Vanguard needs Windows 11 25H2<\/h2>\n\n\n\n

Riot’s announcement of 24 June 2026<\/a> tells players to update to at least Windows 11 25H2, because earlier builds lack the runtime driver attestation report that On-Demand reads. Windows 10 and Windows 11 23H2 or 24H2 cannot qualify, however clean the BIOS settings are. At launch Riot said that about 35% of players met every requirement, about 62% could qualify by switching settings on, and about 3% had hardware too old to pass.<\/p>\n\n\n\n

What the Vanguard Pre-Check requires<\/h2>\n\n\n\n

Six items, all Windows security features: Windows 11 25H2 or later, UEFI boot mode, Secure Boot, TPM 2.0, Virtualization-Based Security with Hypervisor-Protected Code Integrity, and IOMMU. Some boards need a BIOS update before the last two appear. Microsoft’s VBS and HVCI guidance<\/a> lists the same base: a 64-bit CPU with virtualisation extensions, SLAT, TPM 2.0, Secure Boot and every DMA-capable device behind an IOMMU.<\/p>\n\n\n\n

How to check your PC for Vanguard On-Demand<\/h2>\n\n\n\n
    \n
  1. Open the Vanguard tray icon (VGTray) and read the Pre-Check panel; it lists each unmet requirement.<\/li>\n\n
  2. Press Win+R, type winver and press Enter. The version must read 25H2 or higher.<\/li>\n\n
  3. Press Win+R, type msinfo32 and press Enter. In System Summary, BIOS Mode must read UEFI and Secure Boot State must read On.<\/li>\n\n
  4. In the same window, Virtualization-based security must read Running.<\/li>\n\n
  5. Press Win+R and type tpm.msc. Specification Version must read 2.0.<\/li>\n<\/ol>\n\n\n\n

    How to turn on Secure Boot, TPM 2.0 and memory integrity<\/h2>\n\n\n\n

    Make the Windows change first, then the firmware changes, and back up your data before you change firmware settings.<\/p>\n\n\n\n

      \n
    1. Open Windows Security, then Device security, then Core isolation details, and turn Memory integrity<\/a> on. Restart.<\/li>\n\n
    2. Confirm in msinfo32 that BIOS Mode already reads UEFI.<\/li>\n\n
    3. Restart into firmware setup: Settings, System, Recovery, Advanced startup, Restart now, Troubleshoot, Advanced options, UEFI Firmware Settings.<\/li>\n\n
    4. In the security or trusted computing section, enable the firmware TPM; your board manual gives the exact name.<\/li>\n\n
    5. Enable IOMMU in the CPU or chipset section: VT-d on Intel boards, AMD-Vi on AMD boards.<\/li>\n\n
    6. Turn CSM off and Secure Boot on, save, restart and run the Pre-Check again.<\/li>\n<\/ol>\n\n\n\n

      Secure Boot works only when Windows boots in UEFI mode from a GPT disk. On a legacy or CSM install on an MBR disk, turning Secure Boot on leaves the PC unable to boot, and a second operating system with an unsigned bootloader also stops starting.<\/p>\n\n\n\n

      Why the Vanguard Pre-Check still fails<\/h2>\n\n\n\n