If they don't fix that, I might stop playing EFT at all.
Is this happening with other supervisors as well? Like that from VMWare? I would consider switching then.
What exactly is the issue on that? It's not like the game is running inside a VM where you can easily manipulate the VM's memory and inject malicious code from the host machine into the game. I find it really stupid that you get kicked/banned for running VM's in background. That kind of environment seems better aligned to your methodology. Just a broad remark made absent any official guidance on the issue: it sounds like you guys might have better luck with making console games. I was kind of hoping there'd be a response here somewhere, but I'm new here, so maybe that's not how it works? I guess if I don't play then I might as well be banned. I could try playing without WSL enabled, but I don't really want to start playing again, because I don't want to get banned for, you know, nothing. Or, it's entirely something else altogether. Or, the game is just throwing false positives? Or, maybe bios level virtualization needs to be disabled? I assume this because it used to be dependent on hyper-v pre-WSL2. I have a running theory that WSL (which is a separate setting) is either implicitly enabling hyper-v or is being identified as hyper-v itself.
Apparently I didn't have hyper-v enabled to begin with, so that's. If I have to restart, I might as well be doing stuff in Linux and just dual boot. Hyper-v/WSL was my compromise to avoid dual booting. I'd like to play your game but you are making it hard for me. That would be helpful because I don't want to reorganize my workflow to permit me to disable hyper-v on this computer, only to still live with constant concern that something else is going to cause a deliberate game crash hours from now because it might be too scary to you to have it running.Ĭan I switch to VMWare? Do I need to refrain from any virtualization at all, ever? Do I need to disable virtualization extensions altogether in my bios? I need a list of the things you don't want me using. I guess maybe someone might use it to cheat or something? That's fine (it's really not, but we'll say it is) but I cannot find this in documentation anywhere.
So you guys don't want people running hyper-v, apparently. I'm a developer who uses WSL2, which depends on hyper-v to function. This is the first time this has happened after playing for about 20-30 hours.
All this means is that before you can launch into the game and start playing, you'll need to reboot your PC so that Riot Vanguard anti-cheat can finish installing.īest of luck if you're just starting out with the game! Now you know how the Riot Vanguard anti-cheat download works, why not check out all Valorant characters, abilities and ultimates while you're waiting to hit the ground running.I got killed the other day in game because the game kicked me because I run hyper-v. If you try and launch Valorant without rebooting first, you'll receive an error screen telling you that Riot Vanguard hasn't initialized yet.
Fortunately, there's an easy way to get it, so here's how to finish installing Riot Vanguard anti-cheat and launch Valorant. With more than a million eager gamers watching Twitch streams hoping for a closed beta key drop, there's huge interest in learning how to download Riot Vanguard anti-cheat, the final step to getting into Valorant now that is has launched. Valorant launches today, and thousands of fans are hoping to find the elusive Riot Vanguard anti-cheat download to get into the game themselves.