Valorant Error Code: VAL 43 Fix Guide - Error Connecting to the Platform PC 

Since its announcement, closed beta testing and up until its global launch, VALORANT has gotten a warm welcome from the world of gaming. But just like all other games, VALORANT is bound to face errors and issues, especially since it is fresh and built from scratch.

val.jpg


A lot of VALORANT players have been dealing with Error Code: VAL 43 - "There was an error connecting to the platform. Please restart your game client." and it is getting on their nerves. The error is quite common and usually comes up when either the servers are under maintenance or Riot Games is shipping a new update. It generally gets fixed after a short while, but for others, it takes them more than an hour trying to get into the game lobby which can be very frustrating.

Although there are no conclusive solutions at your end, here's a quick fix guide, posted by Facebook user Viar on Valorant PH's Facebook group, that might help you get out of Error Code: VAL 43.

How to fix VALORANT Error Code: VAL 43?​

  1. On the search bar, located at your task bar, search for the 'Services' app and open it.

    val1.jpg


  2. Scroll down to locate the 'vgc' service setting and double click on it.

    val2.jpg


  3. On the 'General' tab, click on the Startup type dropdown menu and select 'Automatic'.

    val3.jpg


  4. Apply, then click 'Start' and wait for the process to finish.

    val4.jpg


  5. Before re-launching the game, right-click on the VALORANT icon and select 'Properties'.

    val5.jpg


  6. Under the 'Compatibility' tab, make sure to check 'Run this program as an administrator' then apply.

    val6.jpg


  7. Re-launch the game and login to your account.
This should help fix the Error Code and get you inside the lobby. There is no need to panic and reinstall the game. But unfortunately, if it doesn't, you can try to spend your time on another game until the error gets fixed.

You can also check out VALORANT's official website and submit a request ticket on their support section. Fix guide and photo credits goes to Facebook user, Viar.
 

Similar threads


Reply