0xNemi

0xNemi



08 May

Comment

Originally posted by Dwyer0022

Sorry had a slight delay but the game loaded up without a problem. Will update my main post as well to let people know. I seriously appreciate it Nemi thank you! And I’ll cancel my ticket.

<3 thanks man. Appreciate your patience. Enjoy!

Comment

Originally posted by Dwyer0022

Thank you. I’m sorry if I seem bitter about this as I don’t intend to be. I will update this post if it fixes my problem.

Any luck with the update? If not, let me know. I'll DM you and we can figure it out together.

Comment

Originally posted by I_Fap_To_Witch_Mercy

This fixed the issue for me 😄

Thank you for the confirmation!

Comment

Originally posted by Dwyer0022

Anyone getting vanguard not initialized? I'm assuming it's got something to do with this release?

Update: Riot has fixed this issue today 5/8 for a majority of people. Thanks to the team for sorting it out.

Vanguard is in a closed beta state as much as VALORANT is. Building an entire Anti-Cheat product from the ground up isn't easy. It'll take some time to get everything completely right.

For this specific issue, we've deployed a fix. Please try to patch VALORANT and Vanguard will update. You will need to reboot your machine in order for the fix to fully take. This requires a system restart, not a shutdown. If this fixes your problem, please close any player support tickets you have open. Thank you!

Comment

Originally posted by [deleted]

I literally see vanguard on the taskbar running and its saying not initialized, man vanguard broke the f**king game

A fix was released just moments ago. Thank you for your patience.

Comment

Originally posted by weju

Same problem but with MSI MEG Z390 MOBO

Going to DM you some questions.

Comment

Originally posted by N4zarus

Same issue here and I'm running Asus x570 crosshair VIII hero

Going to DM you some questions.

Comment

Originally posted by Nosyok_

Same issue but using ASUS Z370-e motherboard

Going to DM you some questions.

Comment

Originally posted by k1ngheezy

nope. same vanguard not initialized issue. msi mobo, logitech g pro mouse, 1080ti,
i7- 5930k, ducky keyboard.

I DM'd you with some questions. I'm confident that the fixes I'm working on will fix issues that folks on ASRock motherboards have, but not sure about other configurations.

Comment

Originally posted by Attackerby

This patch broke Vanguard for me. Was playing the last few weeks and now getting a Vanguard not initializing error. Edit: The later update corrected it for me. My game is working now.

Hey folks, we're looking into this one. We have a good lead. Is anyone here using ASRock motherboards?

EDIT: Reached out to a couple of folks. This issue is more widespread than just ASRock motherboards, but I've gotten confirmation that what I'm working should unblock most people. I'll update this when a fix is deployed. ETA is a few hours. Thank you for patience.

EDIT 2: A fix has been deployed. Please try to patch VALORANT and Vanguard will update. You will need to reboot your machine in order for the fix to fully take. This requires a system restart, not a shutdown. If this fixes your problem, please close any player support tickets you have open. Thank you!


07 May

Comment

Originally posted by Dwyer0022

Yeah that’s definitely not solving my issue as I’ve rebooted 7 times with updates and other things and no luck. I can do the WASD trick to avoid it but then error 43 hits me.

If you're getting error 43, it's a networking error that's related to our platform, I believe. The platform team is aware of this one and working on a fix.

Comment

Originally posted by Dwyer0022

Anyone getting vanguard not initialized? I'm assuming it's got something to do with this release?

Update: Riot has fixed this issue today 5/8 for a majority of people. Thanks to the team for sorting it out.

For most people, a reboot seems to fix this for them. Make sure you select "Restart" (not Shutdown). If this doesn't resolve your issue, your best course of action would be to make a player support ticket since it's the easiest way to get 1:1 support: http://support-valorant.riotgames.com/

Comment

Originally posted by SeaChangi

Does this fix the "valorant encountered an error, please restart" thing that keeps disconnecting me from games?

I'm not sure this is related to Vanguard, but please create a support ticket if you keep running into problems: http://support-valorant.riotgames.com/

Comment

Originally posted by Kaotic3XD

As of the ranked patch, I've been having game closures non stop. No errors, no hard crash. The game just closes. I've sent in a ticket and made a post on here with no response... Help?

I don't think this is related to Vanguard, but I'll let the team know. Feel free to poke your support ticket if you're still running into issues.

Comment

Thanks for your patience as we work out all of these kinks during the closed beta. Keep on delivering this invaluable feedback to us!


30 Apr

Comment

There's a temporary fix you can do while we work on a more permanent solution: https://software.intel.com/en-us/articles/openssl-sha-crash-bug-requires-application-update

Set the OPENSSL_ia32cap environment variable on your machine to this value ~0x20000000.

It's related to a weird bug with OpenSSL and specific CPUs.


28 Apr

Comment

Originally posted by [deleted]

Vanguard is blocking System32 .sys drivers on system start up. xtuacpidriver.sys to be exact. Which is Intel tuning software.

Make sure you have the latest update from the vendor: https://downloadcenter.intel.com/download/24075/Intel-Extreme-Tuning-Utility-Intel-XTU

Extremely old versions of this have been known to cause issues.

Comment

Originally posted by Theostru

Hi /u/0xNemi and /u/RiotArkem !

Is there a way to check what was blocked beyond the notification? On boot, the notification disappeared before I could click it, and when I then went to notification center and clicked on it, it went away without presenting any popup or additional information on what was blocked.

Reading this thread, I'm 99% sure it was HWMonitor, but the fact that I have to rely on an ephemeral popup rather than an actual application or even just a log file is pretty frustrating.

Run this command in command prompt:

reg query HKLM\System\CurrentControlSet\Services\vgk /v BlockedImage    

The tray icon reads from that location.

Comment

We're aware. There's some networking issues that we're sorting out on our backend. They're unrelated to the most recent changes.

Things should be back to normal in the next few minutes. Sorry for the inconvenience!

Comment

Originally posted by DingusDong

Well you've hit the nail on the head. Not having perfect security on what essentially a backdoor to potentially hundreds of millions of computers around the world is frankly a little terrifying given who's at the top of the Valorant totem poll.

Quoting what was said in another thread:

It depends how brazen they want to be. Small scale they could gather a whole heap of data. Like where do people look for their news and information would be really handy in prioritising propaganda efforts. Between Tik Tok monitoring phones and Riot monitoring PCs they can probably get a solid sample size for young westerners. On the other end of the spectrum, they could use it for distributed attacks (credential stuffing/DDOS) or to try and hide the origin on a more sophisticated attack (i.e. using compromised user credentials to exfiltrate data). They have administrator access to the machine, they can do with it whatever you could do with it.

Going really...

Read more

There's nothing I can say to help reduce your concerns. You've already made up your mind.

Ultimately, you get to choose what you run on your machine.