How to Fix Valorant Error VAL 51 (Problem Creating a Party)

By FixMyError · Updated October 14, 2026 · 6 min read

What VAL 51 means

Valorant error VAL 51 hits at the worst possible moment: your friends are online, everyone is ready to queue, you try to create a party — and the game slaps you with "Something went wrong creating a party" and the code VAL 51. No lobby, no invites, no squad.

Under the hood, VAL 51 is a Riot Client problem, not a Valorant gameplay problem. The Riot Client manages your login session, your friends list, and the party service that assembles your squad before matchmaking even begins. When that session goes stale — after the client has been running for hours, after a crashed match, or after Riot Vanguard hiccups during startup — the party-creation request fails and Riot's own error table labels it VAL 51. The fix list from Riot itself is short: restart the Riot Client.

The reassuring part: VAL 51 is almost never serious. It has nothing to do with bans, it doesn't touch your skins or rank, and you can usually still log in and play solo matches while it happens. The failure is scoped to the party pipeline, so the fixes below target exactly that — Riot's server status, the client session, Vanguard's service state, your network route to Riot's backends, and finally a clean Vanguard reinstall.

Common causes

• Riot's services are degraded or in maintenance: if the platform or party backend is down, no client-side fix will help — this is the first thing to rule out.
• Stale Riot Client session: a long-running or half-crashed client session corrupts the party handshake; closing the window without killing background processes doesn't clear it.
• Vanguard not initializing properly: when the vgc anti-cheat service is stopped, disabled, or mid-update, the client session that party creation depends on breaks with it.
• Network and DNS problems: a stale DNS cache or VPN routing you through the wrong region can make the client fail to reach the party servers even while gameplay servers respond fine.
• Conflicting background software: game overlays, aggressive antivirus shields, and a second Riot Client instance running with admin rights can block the party-service connection.

How to fix VAL 51 — step by step

Work through these fixes in order. VAL 51 is very often a stale session, which is why the list starts with the checks Riot itself recommends before you touch anything deeper.

1. Check the Riot Games server status first. Before changing anything, confirm Riot's Valorant services are operational at status.riotgames.com. If Riot reports a platform outage, maintenance, or degraded party services, VAL 51 is on their side — no amount of restarting or reinstalling on your PC will fix it. Wait until the status page is green again, then relaunch the game. Only continue with the steps below if every service shows as operational.
2. Fully restart the Riot Client. Riot's own official fix for VAL 51 is restarting the Riot Client, and it works because the party failure usually comes from a stale client session. Close Valorant completely, then open Task Manager (Ctrl + Shift + Esc), go to the Processes tab, and end every Riot Client, Valorant, and RiotClientServices task. Relaunch the game from the Riot Client — not from a desktop shortcut — and try creating a party again. This single step clears VAL 51 for most players.
3. Restart the Riot Vanguard service. VAL 51 can also appear when Vanguard, Riot's anti-cheat, isn't initializing properly alongside the client. Press Win + R, type services.msc, and press Enter. Find the vgc service in the list, right-click it, and choose Restart. While you're there, double-click it and make sure Startup type is set to Automatic — a disabled vgc service will keep breaking the client handshake that party creation depends on. Relaunch Valorant after the restart.
4. Run the Riot Client as administrator. Permission problems can stop the client from talking to Vanguard and the party backend. Right-click the Riot Client shortcut and choose Run as administrator, then launch Valorant from inside it. While you're at it, temporarily close overlays and background apps that hook into games — Discord overlay, OBS, and aggressive antivirus real-time shields are known to interfere with Vanguard's startup sequence, which can surface as VAL 51. If the error disappears with antivirus paused, add the Riot Vanguard and Valorant folders to your antivirus exclusions instead of leaving protection off.
5. Flush your DNS and reset the network stack. A poisoned DNS cache or stale socket state can make the client fail to reach Riot's party servers even when the game itself connects fine. Open Command Prompt as administrator and run these three commands in order: ipconfig /flushdns, netsh winsock reset, and netsh int ip reset — then restart your PC. After the reboot, avoid VPNs and region-switching tools while testing: tunneling your traffic through another country is a frequent trigger for party-system errors because your client ends up talking to the wrong regional backend.
6. Clean-reinstall Riot Vanguard. If VAL 51 survives everything above, Vanguard itself is likely corrupted. Open Settings > Apps > Installed apps, uninstall Riot Vanguard (not Valorant yet), then restart your PC — the restart is required because Vanguard's kernel driver only clears on reboot. After rebooting, launch Valorant from the Riot Client: it will detect the missing anti-cheat and reinstall a fresh copy automatically. Let the install finish completely before clicking Play. As a true last resort, uninstall both Valorant and the Riot Client and reinstall from scratch.

Did this fix it? Quick checklist

• You can create a party and invite friends without VAL 51
• The Riot status page shows all Valorant services as operational
• Only one Riot Client instance is running in Task Manager
• The vgc service is running with Startup type set to Automatic

If VAL 51 still won't go away, double-check you aren't confusing it with a VAN code — VAN errors are pure Vanguard problems and need Vanguard-focused troubleshooting. Also make sure you are logged into Valorant on one device only; the same Riot account running on two PCs can produce session conflicts that look exactly like VAL 51. As a last resort, a clean reinstall of Valorant and the Riot Client clears every cached session file, but try the full list above first — it resolves the error for the vast majority of players.