VAN RESTRICTION 5: Memory Integrity isn't on and running
Riot VanguardLeague + VALORANTThe message
Error VAN: RESTRICTION: 5What it means
Vanguard couldn't confirm that Memory Integrity, the Windows Core Isolation feature also called HVCI or VBS, is switched on and actually running.
What to try first
Turn on Memory Integrity under Windows Security, Device security, Core isolation, then restart. Grayed out? Enable CPU virtualization in the BIOS first.
Is it you or Riot? If lots of players are hitting this at once, it's probably the servers. Check League server status before you start reinstalling things.
Is 5 the number on your message?
Memory Integrity is RESTRICTION: 5's whole subject. If your message has a different number, or none, it's asking for something else: plain VAN: RESTRICTION, 1 and 4 (both Secure Boot) or 3 (the install drive).
Why flipping the switch might not be enough
Riot gives three ways to land here: Memory Integrity is off in Windows, CPU virtualization isn't fully enabled, or a BIOS/UEFI security setting isn't set right. Only the first is a Windows toggle. The other two live in firmware, and BIOS menus differ by maker, so Riot points you at your PC or motherboard maker's instructions for the exact setting names.
Vanguard wants the feature running, not just enabled. Riot's Memory Integrity guide gives the check: in msinfo32, Virtualization-based security should say Running, and the services running under it should include Hypervisor enforced Code Integrity. Task Manager's Performance tab also shows Virtualization: Enabled under CPU when the BIOS side is right.
Problems the steps don't cover
VBS says enabled but not running. Besides virtualization being off in the BIOS, the guide says VBS needs the Windows hypervisor. Open Turn Windows features on or off and tick Hyper-V (Windows Hypervisor Platform on its own is enough if Hyper-V isn't offered).
The Core isolation page won't open. Some Windows builds hide it. The guide's first suggestion is updating Windows (check your version with winver).
Blue screen after turning it on. A driver that can't run under Memory Integrity can crash Windows at boot. Riot's recovery is to get into the Windows Recovery Environment, open Command Prompt from Troubleshoot, Advanced options, and switch Memory Integrity back off with this line, then fix or remove the driver before trying again:
reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity" /v "Enabled" /t REG_DWORD /d 0 /f
If your CPU has no hardware virtualization at all (VT-x on Intel, SVM on AMD), Riot says the PC doesn't meet Vanguard's requirements, and no setting will change that.
Riot's fix, in Riot's order
Turn on Memory Integrity (HVCI/VBS)
Run
msinfo32and look at Virtualization-based security near the bottom. Running is good. Enabled but not running means virtualization is off in the BIOS. Not enabled means you haven't switched it on in Windows yet.In Windows Security, open Device security, then Core isolation, and turn on Memory integrity. If the switch is grayed out, enable CPU virtualization in the BIOS first (Intel VT-x, AMD SVM). An incompatible driver can also block the toggle, and Windows names it when that happens.
Riot's guide: Turn on Memory Integrity (HVCI/VBS)
Restart your PC
A full restart, not a sign-out. Vanguard's driver loads when Windows boots, so a restart is the only thing that gives it a clean start.
Riot's article ends by telling you to also handle any other requirement your restriction message lists. If yours names something besides Memory Integrity, the plain VAN: RESTRICTION page covers the rest.
Other wordings of the same error
VAN RESTRICTION 5VAN: RESTRICTION: 5Memory Integrity VAN restrictionCore Isolation Vanguard
Related errors
Source: Riot Games Player Support, Error VAN: RESTRICTION: 5, updated March 13, 2026. Riot's steps are paraphrased here, not copied; checked September 25, 2026.