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

You open Valorant, ready to queue — and instead of the main menu you get error code 29, with the message that there was an error connecting to the platform. In plain English, error 29 means Valorant could not connect to Riot's platform at all. Your client tried to reach Riot's servers to sign you in, the connection failed before the main menu ever loaded, and the game stopped right there. It is not a ban, your skins are not gone, and your rank is safe. Most of the time, the cause is one of three things: Riot's platform is down or overloaded (very common right after a patch), your client session is stuck in a broken state, or something on your PC — a firewall, antivirus, or stale network route — is blocking the connection to Riot's servers.

That is also why error 29 behaves differently from other Valorant login errors. Error 59 means the login queue step specifically failed, and error 43 means the platform timed out while fetching your profile. Error 29 is broader: the client could not establish the platform connection in the first place, which is why the fixes that work best are the ones that reset that connection — a truly clean client restart, a fresh network route, and a healthy Vanguard install. The 8 fixes below run from the 30-second checks to the full reinstall, in the order that actually solves the most cases. Start at the top and test a login after each fix so you know which one did it.

What causes Valorant error code 29?

Something is breaking the connection between the Riot Client, Vanguard, and Riot's platform servers. The usual suspects:

• Riot platform servers down or overloaded — the number one cause of error 29, especially right after patches, new Acts, and big events when everyone logs in at once.
• A stuck Riot Client session — leftover RiotClientServices or Vanguard processes from a crashed session keep holding a broken connection.
• Stale DNS or network routes — your PC keeps resolving Riot's platform to a dead or overloaded endpoint.
• Firewall or antivirus blocking the connection — security software silently blocks Valorant, the Riot Client, or Vanguard from reaching the internet.
• Corrupted Vanguard install — Vanguard's service fails to start, so the client cannot complete its handshake with the platform.
• VPN or proxy interference — a VPN routing your traffic through a distant or blocked exit node adds latency and dropped packets to the platform connection.
• Outdated client or Vanguard version — after a patch, a half-updated client no longer matches the server version and the platform refuses the connection.

1Check Riot and Valorant server status

Open the Riot Games service status page and select your region, then look at Valorant specifically. Error 29 spikes during outages and in the first hours after a patch, when the platform is flooded. If the status page shows problems, stop here and wait — every other fix below assumes Riot's side is healthy. If the status page is all green, move on: the problem is on your PC or your network.

2Close the Riot Client completely and restart it

A normal close often leaves the client half-running, which is exactly how a broken session survives. Do a truly clean restart:

1. Right-click the Riot Client icon in the system tray and choose Exit.
2. Open Task Manager (Ctrl + Shift + Esc) and end any leftover RiotClientServices, VALORANT, and Vanguard processes.
3. Relaunch the Riot Client fresh and sign in again.

This alone fixes error 29 for a large share of players, because the fresh client connects to the platform with a clean session instead of resuming a broken one.

3Restart your PC and your router

Restart your PC to clear hung Vanguard and client processes that Task Manager missed, then power-cycle your router: unplug it for 30 seconds, plug it back in, and wait for the connection lights to settle. This refreshes your network route to Riot's servers and clears stale connections that keep the platform connection failing. It sounds basic, but a stale route is one of the most common silent causes of error 29, and this is the only fix that resets it end to end.

4Run the Riot Client as administrator

Right-click the Riot Client shortcut and choose Run as administrator. Vanguard needs elevated permissions to start its service, and a client launched without them can fail to reach the platform and throw error 29. If this fixes it, make it permanent: right-click the shortcut, open Properties, go to the Compatibility tab, and tick "Run this program as an administrator" so every launch gets the permissions Vanguard needs.

5Flush DNS and reset your network settings

Stale DNS entries can keep pointing your client at a dead Riot endpoint long after Riot fixed the outage. Open Command Prompt as administrator and run these commands in order:

1. ipconfig /flushdns — clears the DNS cache.
2. ipconfig /release — drops your current network lease.
3. ipconfig /renew — gets a fresh lease and route.

Then restart your PC and try Valorant again. If you use a custom DNS, try switching temporarily to a public DNS like Google (8.8.8.8) or Cloudflare (1.1.1.1) to rule out a DNS provider problem. If you use a VPN, turn it off for one test login — a VPN exit node that Riot rate-limits or blocks will produce error 29 on an otherwise healthy setup.

6Allow Valorant and Vanguard through your firewall and antivirus

Security software that blocks the platform handshake is a common, silent cause of error 29, because nothing on screen tells you a block happened — the client just fails to connect. Add all three as allowed apps in Windows Defender Firewall and in any third-party antivirus you run:

• VALORANT (the game executable)
• The Riot Client
• Vanguard and its service (vgc)

After adding the rules, restart your PC so the firewall picks them up cleanly, then test a login. If you run a third-party antivirus with its own firewall, add the same exceptions there too — Windows rules alone do not override it.

7Repair Vanguard and the Riot Client

If the connection still fails, Vanguard itself may be corrupted. Uninstall Riot Vanguard from Windows Settings (Apps, then Installed apps), then relaunch Valorant — the client will reinstall a fresh copy of Vanguard automatically. Restart your PC after the reinstall so the Vanguard service starts cleanly, then sign in again. This replaces corrupted anti-cheat files that can break the platform connection without any visible error of their own.

8Reinstall Valorant clean as a last resort

If nothing above worked, do a clean reinstall: uninstall Valorant and the Riot Client, restart your PC, and install fresh from Riot's official site. Your account, skins, agents, Battle Pass progress, and rank live on Riot's servers, so a reinstall loses nothing you earned — it only replaces local game files. After reinstalling, launch the Riot Client as administrator for the first login, so Vanguard installs with the permissions it needs from the start.

Quick checklist

• ☐ Riot status page checked — green before troubleshooting your PC
• ☐ Riot Client fully exited, leftover processes ended, fresh relaunch
• ☐ PC and router restarted, network route refreshed
• ☐ Client launched as administrator
• ☐ DNS flushed, network lease renewed, VPN off for one test
• ☐ Valorant, Riot Client, and Vanguard allowed through firewall and antivirus
• ☐ Vanguard repaired, PC restarted after the repair
• ☐ Clean reinstall only if every fix above failed

Frequently asked questions

For most players, error 29 dies at Fix 2 — a truly clean client restart clears the stuck session in under a minute. Work through the list in order and you will be back in the lobby soon. And while Valorant sorts itself out, the free browser games here on GameAdda need no launcher, no platform connection, and no patch luck — just pick one and play. 🎮