ON THIS PAGE
The quick answer
Fix the flagged driver—not all virtualization.
Riot’s VAN: INCOMPATIBLE SOFTWARE message normally identifies a specific blocked driver or file. Note the exact filename, update or uninstall the related program through its publisher, restart, and retry. Hyper-V, Docker, or WSL2 presence alone does not prove the cause.
Jump into the guide01Read-only hypervisor checks
Developers often want a simple ON/OFF boot toggle. First check the present configuration; do not change platform security until you know whether Riot has actually flagged an incompatible component.
bcdedit /enum {current}
systeminfo02Fix a genuinely incompatible driver
Write down the exact filename from Vanguard
Include the full path and take a screenshot before changing anything.
Find the program that installed it
Check Installed Apps, VirtualBox/VMware drivers, optional overlays or older peripheral suites.
Update or remove through the publisher
Use normal uninstall/update workflows, restart Windows, and retest VALORANT.
Reinstall Vanguard if still flagged
Use Riot’s procedure, then send a support ticket with logs if the restriction returns.
03Why blanket Hyper-V OFF scripts backfire
Developer tools use virtualization
Docker Desktop, WSL2 and certain VirtualBox modes can rely on Windows’ hypervisor. Turning it off can break these workflows.
Windows security may need the hypervisor
Memory Integrity / VBS use the Windows hypervisor. Disabling it can reduce device protection and trigger different Vanguard requirements.
Riot’s incompatible-software guidance is specific to the blocked file; it does not require every developer to permanently disable Hyper-V. Prefer a documented program update or removal.
Frequently asked questions
Does Vanguard ban Docker or WSL2 by default?
Do not assume that. Read the exact driver path and error; compatibility depends on current versions and security requirements.
Should I run bcdedit /set hypervisorlaunchtype off?
Not as a universal solution. It changes boot behavior and can disable features Windows security or development tools need.
Sources & update notes
Original Walker Bex explanations. Technical guidance checked October 15, 2026; follow the current linked support instructions if they change.