kartios

As much as I can appreciate your support as someone who has been in a similar role as you, it doesn't look good for a random Riot employee to be instructing people to delete System32 drivers without any explanation or acknowledgement from Riot itself. Why should some random virtualbox USB driver be affecting Vanguard? What happened to not scanning hardware?

I responded about the VirtualBox USB in another comment, but on the second point, these actions aren't contradictory to anything we've stated, or announced in our Security policies: https://www.riotgames.com/en/news/a-message-about-vanguard-from-our-security-privacy-teams . All these troubleshooting measures, and reasonings have not only been said on Reddit by Riot Employees, but are being shared with support.

I agree with you, Reddit is a limited scope. While it's more than what most say about the definites of Anti-Cheat vectors, I agree players would be benefited from a faster, easier way to troubleshoot and assess their issues.

I'll work harder as Closed Beta progresses to communicate better, and we will keep aspiring to be industry leaders in the Anti-Cheat space in our communication and transparency.

kartios

Seems legit, just delete some sys files.

Get this intrusive software out of the game. This is absolutely ridiculous. There are already so many issues that I have zero faith in the security of this driver. What are you guys waiting for, millions of users to get pwned? Just do it now before it's too late.

Edit: can you also explain why this file has to be deleted? Why should we be deleting virtualbox drivers for your driver to work? Without an explanation this is even more ridiculous than I previously stated.

https://github.com/hfiref0x/TDL

Here's a good example of using VirtualBox drivers to defeat driver signing. Not only has this been used in cheats in other games, it's been used in cheats in VALORANT.

Snowolf

Are there any issues with VirtualBox if the USB driver isn't installed? Not seeing ti in the list, and not seeing any unsigned drivers anywhere, yet experiencing this issue :(

There can certainly be other things that can cause it. I'd recommend making a ticket, and uploading the Vanguard logs. If you DM me the Ticket #, I can review it on a more expedited schedule.

Sigv1

I’m fine with having vanguard on my computer. I’m fine with updating/removing drivers to meet vanguards requirements. I’m fine with waiting for a solution to this. The only thing that bothers me is the fact that this is not being acknowledged on a larger scale. Make a twitter post, put it on the client. A simple statement saying that you know about the issue and are working on a solution can save people countless hours browsing reddit as-well as stopping misinformation being spread.

Agreed with you that this is a worthy pain point. We'll work on an easier way to see these issues. I've been adding issues I encounter here to guides Player Support can use, so they can help players faster in troubleshooting. I'll see what can be done in adding more visibility. You're right - even though this is not massively widespread, we can do better in letting players know.

Thanks for much for toughing it out and thank you for your feedback. It's not PR stuff when I say that getting to have this direct, instant feedback and troubleshooting, has, and will be, very helpful.

Theo_Choq

I don't seem to have VBoxUSBMon.sys in my drivers yet it still doesn't work. Any ideas?

There are other vulnerable drivers that could cause it. If you could zip up the Logs in C:\Program Files\Riot Vanguard\Logs , and send to me through preferred file sharing service in a direct message, I can assist you.

WowWhatWhyHow

How on earth can you play with music on?!

also, u/RiotNaCl might wanna check that out??

thanks. there's a bug here, they aren't hacking.

solMachina

Hope you don't mind me sending you my ticket number as well. I've been detailing every step of the process I've attempted to remedy this issue, myself. I tried reading the provided logs to get more verbose details than "Error 1" but they're encoded.

No problem! Working on a good bit of em right now so there may be some delay but will get to them ASAP.

inb4Downvoted

Why are you telling non technical end users to delete system files on their home computers?

It's why it's best to troubleshoot these things through Support, so the issue can be pinpointed and handled in a safe manner. I do have assistance to help safely remove these programs. Incompatibility is a standard part of Software Troubleshooting. I would not recommend people going into their system files and deleting things random things and hoping it'll work.

bruhwav3

what do i do with a unsigned files if i scan with sigverif?

For any unsigned driver files (.sys files) you should either remove them or try to update them to the latest version.

Altimor

I strongly discourage y'all from trying to mix and match Vanguard components across versions as this could cause system instability and looks a lot like cheating to our servers.

Why let people connect with an out of date Vanguard at all?

We like to give a short grace period during an update so that people who are in game when the update goes live aren't disconnected. Also, seeing who connects with an old version is very useful information.

ambivalent_teapot

Okay, but what do we do if this is a driver that we actually need really badly? The only driver that sigverif finds for me is a driver for my graphics tablet, which is the official and latest version of that driver, and which I need to have my tablet working.

As long as the driver isn't loaded the game should run, so one thing you could try is to unplug the tablet and then be able to play the game.

SouvenirSubmarine

The Realtek HD Audio Driver package is present on all Windows machines that feature a Realtek sound card, rendering all of them vulnerable to attacks. Exploitation, however, requires the attacker to have administrator privileges.

Isn't this is exactly why I should be wary about granting software like Vanguard administrator privileges?

You should be wary. You should carefully consider anything you install on your computer, user-mode or ring-0.

The comments about other drivers are just meant to put the risk into perspective; you already have lots of drivers with vulnerabilities running in ring-0 already and you probably didn't know about it.

clorster

What if everything is up to date when you run sigverif? And it still doesnt work?

Check for gdrv.sys (see my edit) and if that doesn't work I recommend a support ticket

Hey everyone, the latest version of Vanguard won't run if it detects vulnerable or out of date drivers on your computer.

If you run "sigverif" it will give you a list of unsigned components that could be preventing Vanguard from starting. Any driver (.sys file) on that list should be updated or removed.

I strongly discourage y'all from trying to mix and match Vanguard components across versions as this could cause system instability and looks a lot like cheating to our servers.

More discussion in this thread: https://www.reddit.com/r/VALORANT/comments/g3m5p7/vanguard_anticheat_not_enabling/

Edit: One thing I forgot to mention here or in the other thread is that there are some drivers that will pass sigverif but are still considered untrusted. The most common one is a vulnerable Gigabyte driver (commonly used by ransomware and cheats) known as gdrv.sys. Definitely recommend removing that driver!

Some of the software packages that installed the driver are:

GIGABYTE APP Center

AOR...

PM_ME_PRETTY_SUNSETS

Will muted teammate's pings still be played?

We're looking at what we can do there as well. It would be a separate change from the two changes I mentioned.

What would you like to see there personally? Should be tied to muting someone on Voice? Should it be it's own separate mute?

Disclaimer: I'm a Software Engineer not the one who's making UX decisions but I have chatted with them about it.

19Dan81

Something is definitely not right with this kid, first kill looks like any decent flick. The tracking on the second target is unnatural as it appears to track per pixel. Next clip his aim is horrible on 1st and second kill then flicks to the 3rd kill which isn't suspicious for a good player but could also be luck. Given the evidence on the whole I think there's enough here to warrant investigation based on how wildly different his aiming patterns are. What do you think /u/RiotArkem

We'll investigate!

chervz

LOVE THE GOOD COMMS

WE LOVE THE GOOD BUG REPORTS! Keep em coming Reddit.

toocanzs

Couldn't the client keep full precision aim vectors under the hood, but quantize them visually and when sending to the server so that if you make small movements like this eventually the crosshair will jump to the next rounded value?

Yeah something like this could definitely work.

However, it might have an unintended effect.

Imagine you stored 99% of a "down movement" locally on the client then try to hit a flick really fast. The mouse movement for the flick would need to overcome that 99% "storage" value to work. Might lead to some inconsistencies that are hard to detect but throw of the "feel" of the game if that makes sense. You could counter this in various ways "hand waving" so the basic idea could work with the right implementation.

When we look at problems like this we often write down all possible solutions and share them amongst the dev team to try and find the most optimal solution for the player experience. I'm sure something like this will be one of the options on the docket. The easiest solution is probably what RiotStealthyJesus suggests, simply increasing the precision to the point where it works for all sens and zoom factors.

carnivori

Hey! @RiotArkem I rand sigverif and it says nvcpl.dll is unsigned. nvcpl.dll is the library for Nvidia control panel and I have clean installed the latest Nvidia drivers.

Only unverified drivers (.sys files) should cause a problem so nvcpl.dll appearing on the list shouldn't be an issue. If you're still having a problem I recommend a support ticket.

This problem can sometimes occur if your device drivers are out of date, not signed properly, have been modified or are otherwise kind of busted.

This page has a few methods on how to detect drivers like this so you can update or remove them: https://www.drivethelife.com/windows-10/check-unsigned-drivers-on-windows-10.html

/u/zigzagdance recommends "sigverif" which comes with Windows, that or "dxdiag" are my preferred methods.

There are other reasons that this error can occur but this is worth a shot if you run into the problem!