How to Fix Valorant Error Code 39: "There Was an Error Connecting to the Platform"

You're queued up for a ranked game, you hit Play, and instead of the agent-select screen you get this: "There was an error connecting to the platform. Please restart your game client. Error Code: 39." No matter how many times you relaunch, the same message blocks you from even reaching the main menu. Sound familiar? Error 39 is one of Valorant's most common login-time errors — and the good news is it's almost always fixable in minutes.

In plain English, error code 39 means your game client can't reach Riot's servers — the "platform" that handles logins, your friends list, and matchmaking. Your PC, your internet, and Riot's infrastructure all have to shake hands for that connection to work, and when any one of them misbehaves, you get error 39. The 8 fixes below are ordered from quickest to most thorough — most players are back in the agent select within ten minutes. Start at the top and work down.

What does Valorant error code 39 actually mean?

Valorant connects to Riot through two layers: the game client (the match itself) and the platform (logins, social features, and the store), which runs through the Riot Client — the launcher behind Valorant, League of Legends, and Riot's other games. Error 39 fires when the Riot Client can't establish that platform connection. It's a connection failure, not an account failure: your rank, skins, and friends list are all fine — the client just can't talk to the servers right now. That also means error 39 is never a ban. Bans come with completely different messages.

What causes error code 39?

Since three different systems are involved (your PC, your network, Riot's servers), the trigger can be on any side:

• Riot server maintenance or outages — the single most common cause, especially on patch days. If Riot's platform servers are down or rolling out an update, nobody can connect and no local fix helps.
• A stuck Riot Client session — the launcher holds a broken login session that survives a game restart, so relaunching Valorant alone doesn't clear it.
• Riot Vanguard driver problems — Vanguard, Valorant's kernel-level anti-cheat, loads at boot. If it failed to start (often right after an update), the client refuses to connect.
• Firewall or antivirus blocking — Windows Defender or third-party antivirus silently quarantining or blocking Vanguard's driver is a classic trigger.
• Conflicting software — overlay apps, some RGB utilities, and cheat-adjacent tools can clash with Vanguard and break the connection.
• DNS or ISP routing issues — bad DNS entries or your ISP's routing can stop your PC from resolving Riot's platform servers.
• VPN or proxy interference — VPNs reroute your traffic through another region, which Riot's platform layer frequently rejects.

1Close and restart the Riot Client completely

Reopening Valorant isn't enough — the broken session lives in the Riot Client launcher underneath it. Press Ctrl + Shift + Esc to open Task Manager, and end every process named Riot Client, VALORANT, and RiotClientServices.exe. (On the Processes tab, right-click each one and choose End task.) Then launch Valorant fresh from your desktop shortcut or Start menu. This forces a brand-new login session, and it clears error 39 surprisingly often — it's Riot's own recommended first step.

2Restart your PC — don't skip this

If killing the launcher didn't work, do a full restart: Start → Power → Restart (not Shut down — Windows Fast Startup can keep drivers loaded through a shutdown). A reboot does two things a launcher restart can't: it reloads Vanguard's kernel driver from scratch, and it tears down every stuck network session on your machine. Right after a Valorant update, this is especially important, because Vanguard's driver version changes with the patch and the old one can't talk to the new client. Many players report error 39 vanishing after one clean reboot.

3Check Riot's server status before touching anything else

Still locked out? Now's the time to confirm whether the problem is even yours. Go to status.riotgames.com, pick VALORANT and your region (NA, EU, AP, etc.), and look at the platform status. Maintenance windows and patch-day incidents cause more error 39 cases than everything else combined — if there's an active incident, the honest answer is to wait. Riot usually resolves platform issues within a few hours. If the status page is all green and you're still getting error 39, the problem is local, so keep going.

4Run Valorant as an administrator

Vanguard runs at the kernel level, and on some systems it can't start properly without elevated permissions. Right-click your Valorant shortcut, choose Properties → Compatibility, and check "Run this program as an administrator", then click OK. Launch the game again. If you'd rather set it once for the Riot Client too, apply the same setting to the Riot Client shortcut. This one fixes a lot of "error 39 after a Windows update" cases, because Windows updates sometimes reset the permissions Vanguard was quietly relying on.

5Let Valorant and Vanguard through your firewall and antivirus

Your security software can silently block the exact processes error 39 needs. In Windows Security → Firewall & network protection → Allow an app through firewall, add exceptions for VALORANT.exe, RiotClientServices.exe, and the Vanguard folder (usually C:\Riot Games\VALORANT\live\ and C:\Program Files\Riot Vanguard\). If you run a third-party antivirus (Norton, McAfee, Bitdefender, etc.), do the same in its firewall/exclusions settings — or temporarily disable real-time protection for five minutes as a test. If the game connects with the antivirus off, you've found the culprit: whitelist the Riot folders permanently, don't just leave protection off.

6Flush your DNS and try Google's DNS servers

If your PC can't properly resolve Riot's platform servers, the connection fails before it starts. Open Command Prompt as administrator and run:

ipconfig /flushdns

This clears your DNS cache so stale entries can't send you to dead server addresses. For a longer-term improvement, switch to a reliable public DNS: go to Settings → Network & Internet → your connection → Edit DNS settings, set it to Manual, and enter 8.8.8.8 as preferred and 8.8.4.4 as alternate (Google's DNS). Restart your PC after the change, then launch Valorant. Slow or broken ISP DNS is a quiet, common cause of platform-connection errors.

7Turn off your VPN and proxy apps

Disable every VPN, proxy, and "gaming network optimizer" on your system — including browser VPN extensions, since some inject system-wide proxies. Riot routes your connection by region, and VPN tunneling regularly triggers error 39 because the platform sees your traffic arriving from somewhere unexpected. Also check Windows Settings → Network & Internet → Proxy and make sure nothing is forcing your traffic through a proxy server. Relaunch Valorant with a direct connection and see if the error clears.

8Reinstall Riot Vanguard — or do a clean reinstall of Valorant

If nothing above worked, Vanguard itself is likely corrupted. Go to Settings → Apps → Installed apps, find Riot Vanguard, and Uninstall it. Restart your PC, then launch Valorant — the game detects the missing anti-cheat and reinstalls it automatically. If error 39 still persists, take the nuclear option: uninstall Valorant itself, delete any leftover C:\Riot Games folders, restart, and download a fresh copy from playvalorant.com. A clean install resets every client file, every driver, and every cached session — it's the last resort because it takes the longest, but it ends virtually every stubborn error 39 case.

Quick checklist to keep error 39 away

• Always restart your PC after a Valorant patch — Vanguard needs the reboot.
• Keep Valorant and Vanguard whitelisted in your firewall and antivirus permanently.
• Play without a VPN — Riot's platform layer and VPNs don't mix.
• Close overlay and RGB utilities that hook into games if connection errors return.
• Bookmark the Riot service status page so you can tell server issues from PC issues in seconds.

Frequently asked questions

For most players, error 39 disappears by Fix 3 — it's either a Riot server hiccup or a Riot Client session that needed a proper restart. Work through the list in order and you'll be back in agent select before your duo queue fills. And if you ever want a game that skips launchers, logins, and error codes entirely, the free browser games here on GameAdda start with a single click. 🎮