How to Fix “Failed to Login: Invalid Session” Error in Minecraft?

Minecraft: Java Edition can reach a multiplayer server and then reject the join with “Failed to login: Invalid session (Try restarting your game and the launcher).” The server was reached, but its account check did not pass. It could not validate the launcher’s session.

The session can fail when the launcher keeps old sign-in data, the same account opens in another instance, or the wrong Microsoft account is active. Third-party launchers can hold a separate expired login.

A service outage or one-server problem can show the same message, so scope matters.

This error is not a ban, a game-version mismatch, or a reason to change your Minecraft profile name.

If the Multiplayer button itself is disabled or an account-privacy message appears instead, use the separate Minecraft multiplayer account guide.

1. Restart Every Minecraft Session and Sign In Again

This usually happens when a remaining Java process or another launcher keeps using the old session. A full sign-out forces the launcher to request new account credentials.

1. Exit Minecraft: Java Edition and close the launcher.
2. Press Ctrl + Shift + Esc to open Task Manager. End remaining Minecraft, Minecraft Launcher, javaw.exe, and mod-launcher processes.
3. If the same Microsoft account is running Minecraft on another PC or in a second instance, close that copy as well.
4. Open the official Minecraft Launcher, select the profile or account menu, and choose Log out.
   
5. Close and reopen the launcher, select Microsoft Login, and sign in with the account that owns Java Edition.
   
6. Start one fresh game instance and try the server again.

Minecraft documents the same launcher sign-out and sign-in procedure.

Do not use a second account as a shortcut unless it also owns Java Edition. If every server now works, the old session was the problem. If the launcher no longer recognizes ownership, continue below and verify the account before repeating the restart.

2. Verify the Microsoft Account That Owns Java Edition

Ownership validation fails when the launcher signs into a Microsoft account that does not hold the purchase. The clearest warning is Play Demo, Buy Now, or a product-verification message where Play normally appears.

1. Check the email address and Xbox gamertag displayed by the launcher.
2. Use Minecraft’s official sign-in checks to compare that email with the purchase confirmation or Microsoft order history.
3. On Windows, open the Xbox app and sign in with the account that owns Minecraft. Use the same account in the Microsoft Store and Minecraft Launcher.
4. Sign out of the launcher once more, sign back in with the confirmed account, and test multiplayer.

If the launcher specifically says it cannot verify the products you own, the focused Minecraft ownership-verification guide covers that separate launcher problem.

Do not use this account check when the launcher already shows the correct gamertag and a normal Play button. If the correct account restores multiplayer, the launcher had loaded the wrong entitlement. If only a modded launcher still fails, continue to the next method below.

3. Test the Third-Party Launcher Against a Clean Java Installation

A third-party launcher fails when its saved account session expires independently of the official launcher. A clean official installation isolates that session from the Microsoft account and server.

1. Open the official Minecraft Launcher and sign in with the confirmed owning account.
2. Select Minecraft: Java Edition > Installations > New installation.
3. Choose a release that a known vanilla-compatible server accepts, keep the default game directory, and create the installation.
4. Launch the clean installation and join that server. If your original server requires mods, this comparison checks the account session rather than mod compatibility.
5. If it works, return to the third-party launcher, update it, then sign out and re-add the same Microsoft account through its supported account menu.

Minecraft provides the same clean Java installation procedure.

A successful official-launcher test proves that the Microsoft account and server can authenticate. The stale session belongs to the other launcher or profile.

An offline or cracked account cannot authenticate to a normal server that verifies paid accounts. Do not use a username-changing or token-generation workaround. If the clean official installation still fails on every server, continue to the next method below.

4. Check for a Service Incident or Local Network Filter

Authentication fails when a service incident or local filter interrupts verification. Testing another server and network separates an outage from a problem limited to this PC.

1. Try one other known-working Java server. Ask another player to test the original server at the same time.
2. If unrelated servers and many players fail together, check the official Xbox status page for account or sign-in problems and retry later.
3. A clean Xbox page does not rule out a Minecraft-only incident. Compare current player reports before changing Windows.
4. If the failure is limited to your PC, disconnect an active VPN or proxy for one test.
   
5. Try the launcher through a phone hotspot. If that works, the normal network’s DNS, proxy, parental-control, or filtering layer is interrupting authentication.
6. Only when the launcher itself cannot sign in or verify ownership, pause the antivirus Web Shield for one attempt.
   
7. Turn protection back on immediately. If that one comparison succeeds, allow the official Minecraft Launcher in the security product instead of leaving protection disabled.

This network test is not needed when other servers accept the same game instance. If another network works, correct the filter on the normal connection.

If every player is affected, wait for authentication to recover. If only one server fails, continue below with the server-side checks.

5. Check One-Server Failures Without Disabling Authentication

A one-server failure usually points to the affected host, its authentication connection, or its proxy. A successful join elsewhere confirms that the player’s current session can be validated.

Do not use these server checks when every public server rejects the account.

1. Give the server owner the exact error text and the time of the failed join so they can match it to the console log.
2. The owner should restart the server and any proxy, then confirm that the host can reach Minecraft’s authentication services.
3. For a normal standalone server, keep online-mode=true in server.properties.
4. For a Velocity or BungeeCord network, follow that proxy’s secure player-forwarding setup and prevent direct public access to backend servers. Do not copy a generic offline-mode value from an unrelated setup.

If the account joins other servers, reinstalling Minecraft on the player’s PC will not repair this server. The owner should review the logs or contact the host.

If the official launcher fails on every server instead, continue to Method 6.

6. Repair the Official Launcher and Contact Minecraft Support

Launcher repair belongs at the end because reinstalling the game does not normally replace an invalid session. It becomes reasonable when the owning account fails everywhere in the official launcher.

1. Install pending Minecraft Launcher updates from the Microsoft Store Library, or download the current launcher from the official Minecraft download page.
2. On Windows, open Settings > Apps > Installed apps > Minecraft Launcher > Advanced options and select Repair if the option appears.
3. If repair fails, reinstall the launcher only. Do not delete .minecraft or its saves folder for an authentication error.
4. If the error remains, contact Minecraft Support. Include the exact message, launcher name, Microsoft gamertag, whether Play or Play Demo appears, and whether one or every server fails.

This final repair is not needed when the error is limited to one server or one third-party launcher. Repair leaves worlds in place; keeping .minecraft unchanged provides the rollback if you need to return to the previous launcher setup.

If repair or reinstall works, stop before changing Java or world files. If the error still appears, the support details above separate an account problem from a launcher defect or server-side rejection.