Enable VBS and HVCI for Valorant: BIOS and Memory Integrity checks
ItsOOGWAY · PC guides & recorded tests
Enable VBS and HVCI for Valorant: BIOS and Memory Integrity checks
VBS or HVCI showing a red X in Riot Vanguard Pre-Check?
The key checkpoint: Check firmware virtualization first, then enable Memory Integrity in Windows Security and verify Vanguard again after any requested restart.
Before you start
- Identify your CPU and motherboard; firmware menus differ.
- Keep your BitLocker or device-encryption recovery key available before firmware changes.
- Follow the specific Vanguard requirement shown on your own PC.
Resources from this video
Links, downloads & documentation
Every original URL from the video description is collected here, including recorded releases, setup discussions and related videos. Use the version-specific notes when following a recorded build.
Current security reference: Riot’s Vanguard security requirements. Follow the requirement specific to your system.
Watch the complete video
Open this video on YouTube ↗. Screenshots below link to their exact recorded moments.
Walkthrough 01
Read the actual Vanguard requirement
The video begins with Vanguard’s pre-check and a VBS/HVCI requirement. Check the message on your own PC before changing firmware. VBS supplies an isolated security environment; Memory Integrity is the Windows setting associated with HVCI. A requirement can depend on your configuration, so use the current Vanguard guidance linked in the resources section as well as the recorded example.
Walkthrough 02
Enable the relevant firmware virtualization options
The recorded AMD/AORUS route enables SVM and IOMMU in the firmware settings. Menu names and locations vary by motherboard. Intel systems may label the corresponding options as Intel Virtualization Technology and VT-d. Check the motherboard instructions and keep your device-encryption recovery key available before changing firmware. Save the intended changes and return to Windows.
Walkthrough 03
Open Memory Integrity in Windows Security
Open Windows Security, then Device Security, Core isolation details and Memory Integrity. Turn Memory Integrity on when the device supports it, and complete any restart Windows requests. If Windows names an incompatible driver or another reason it cannot enable the setting, address that specific message. Do not remove unrelated protections to make the pre-check disappear.
Walkthrough 04
Verify after the change
Return to Vanguard Pre-Check and inspect VBS and HVCI again. Check that the firmware settings were saved and that Windows Security still shows the intended Memory Integrity state after reboot. If the red X remains, collect the CPU and motherboard model, Windows version and exact requirement text. A generic screenshot of a different motherboard cannot establish your menu path.
If your result differs
| Situation | Next useful check |
|---|---|
| Firmware menu names differ | AMD commonly uses SVM and IOMMU; Intel equivalents may appear as virtualization technology and VT-d. Use the motherboard documentation. |
| Memory Integrity will not turn on | Read Windows Security’s incompatible-driver or hardware message and address the named issue rather than disabling protection. |
| Vanguard still shows a red X | Complete the requested restart, recheck Memory Integrity and inspect Vanguard’s current requirement message. |
Comments
Post a Comment