Steam Error Code E84: How to Fix the Login Loop on Windows

What Causes Steam Error E84

The error sits at the handshake between the Steam client and Valve's authentication servers. A few things tend to trigger it:

• A buggy or half-loaded React login interface after a client update.
• A wrong system clock, which breaks the secure token exchange.
• A flaky connection or a VPN that Steam's login servers don't like.
• An actual Steam server-side outage that no local fix will touch.
• Lingering Steam background processes from a previous session blocking a clean login.
• An aggressive firewall or antivirus rule quarantining the Steam client mid-handshake.

Why this matters: if you know it's a login-layer issue, you stop wasting time reinstalling your games or messing with your library. The fixes below go from the one that works most often to the nuclear option.

The 7 Fixes, In the Order That Actually Works

1. Add the -noreactlogin launch parameter. Right-click your Steam desktop shortcut, choose Properties, open the Shortcut tab, and click into the Target field. After the closing quote of the path, add a space and then -noreactlogin. Click Apply, then launch Steam from that shortcut. This forces the legacy login window and resolves E84 for most users.
2. Force-quit Steam completely and relaunch. Press Ctrl + Shift + Esc to open Task Manager, find every Steam-related process under the Processes tab, and click End task on each. Steam often leaves background processes running that block a clean re-login. Then reopen it.
3. Switch your network or kill the VPN. A slow, dropping, or filtered connection can starve the login handshake. Disconnect any VPN, switch from Wi-Fi to a wired connection if you can, or try a phone hotspot to rule your home network out.
4. Reset your Steam password. Go to Steam's site, click Login, then Help, I can't sign in, choose the password reset path, verify through your email, and set a new password. This refreshes your stored credentials and clears a stale-token cause of E84.
5. Check whether Steam is actually down. Open Downdetector or Steam's status pages. If reports are spiking, the problem is on Valve's end and your best move is to wait it out.
6. Fix your system date and time. Press Windows + I, go to Time & Language > Date & Time, and turn on Set time automatically. A clock that's even a few minutes off can break the encrypted login exchange.
7. Reinstall Steam. If nothing above works, uninstall Steam from Installed Apps, then download a fresh copy from Valve. Your installed games live in the steamapps folder and can usually be preserved, but back that folder up first if you're worried about re-downloading hundreds of gigabytes.

Before you reinstall, copy your steamapps folder somewhere safe. Drop it back into the new install directory and Steam will detect your existing games instead of re-downloading them.

Two Extra Checks Before You Reinstall

If the seven fixes above haven't landed and you'd rather not reinstall yet, two often-overlooked culprits are worth a minute each.

• Whitelist Steam in your antivirus and firewall. Security suites sometimes flag steam.exe or its web helper processes and silently block the handshake, which surfaces as E84. Add Steam and its install folder (typically C:\Program Files (x86)\Steam) to your antivirus exclusions and allow it through Windows Defender Firewall.
• Delete the Steam web cache. A corrupted browser cache inside Steam can keep the React login from rendering. Close Steam fully, then delete the contents of the htmlcache folder inside your Steam directory. Steam rebuilds it on the next launch, often fixing a login window that loads blank or loops.

Quick Comparison of the Main Fixes

Pro tip: launching Steam "as administrator" once can also clear a stuck handshake, because it ensures the client has permission to write its login token and update files. Right-click the shortcut and choose Run as administrator before reaching for a full reinstall.

If E84 Keeps Coming Back

A parameter fix that works today can stop working after the next client update, because Valve sometimes deprecates old launch flags. If -noreactlogin stops helping, remove it, let Steam fully update, and retry the plain login first. Persistent E84 across networks and a fresh install usually points to a server-side problem, and Valve typically patches those within a day or two.

If you hit E84 in waves, every few weeks right after an update, that pattern itself is the tell that it's the React login regressing rather than anything on your machine. In that case the practical move is to keep the -noreactlogin shortcut around as your default launcher and only remove it when you specifically need a feature that requires the newer login screen, such as QR-code sign-in from the mobile app.

E84 on the Steam Deck and Other Platforms

The launch-parameter fix is a Windows desktop solution, so it doesn't translate directly to every platform. On the Steam Deck and on Linux, you can't simply edit a shortcut's Target field. Instead, switch the Deck to Desktop Mode, right-click the Steam icon, and add -noreactlogin to the launch options there, or set it through the Steam client's properties. On macOS, the equivalent is launching Steam from Terminal with the same flag appended. If editing launch options isn't practical on your platform, lean harder on the connection-side fixes, correct clock, no VPN, a stable network, since those address the same handshake without touching the login interface at all.

Mobile is a different story: the Steam mobile app and Steam Chat use a separate sign-in path, so if you can log in there but not on desktop, that confirms your credentials and account are fine and the problem is purely the desktop client's login window. That's a useful diagnostic, if mobile works, skip the password reset and go straight to the -noreactlogin and cache fixes.