Minecraft "Failed to Verify Username": Fix the Login and Session Error

Check account and service status before anything else

1. Confirm you are signed in with the correct Microsoft account in the official launcher, and sign out and back in to refresh the session token if the launcher has been open for a long time.
2. Check the Xbox Live service status page. Minecraft multiplayer verification relies on Microsoft/Xbox authentication, so a degraded status there can produce this error even when the game and the server are healthy.
3. Check the official Minecraft Help Center for a posted sign-in, account, or multiplayer incident. During a confirmed incident, wait for a timestamped recovery update instead of reinstalling.

Refresh the session, then re-test

• Fully close and reopen the launcher and the game after signing back in, so a new, valid session token is issued for the next join attempt.
• On console or mobile Bedrock Edition, confirm the device is signed in to the correct Microsoft/Xbox account and that the account is not signed in on another device in a way that interrupts the session.
• Verify the device date and time are set automatically. A clock that is wrong by minutes can break the secure handshake used to verify the login and read as a username-verification failure.

Separate the account problem from the server

• Try a second known-good server after re-authenticating. If the verification succeeds elsewhere, the first server or its whitelist is the boundary, not your account.
• If every server returns the same verification error, focus on the account, launcher session, device clock, and Microsoft/Xbox status rather than repeatedly reinstalling.
• For a whitelisted or Realms server, confirm the exact account name that was invited or added matches the account you are signed in with, because a mismatch can look like a verification failure.

Isolate the network only after the account checks pass

1. Test another network if it is safe and available, such as switching a device between Wi-Fi and a phone hotspot. A restrictive school, work, or public network can block the authentication endpoints Minecraft needs.
2. Change one firewall or security rule at a time if the evidence points to local security software, and restore normal protection immediately after a controlled test.
3. Avoid a VPN or proxy during the verification test, because rerouting the login traffic can trigger extra checks that surface as a failed username verification.

Avoid fixes that create bigger problems

• Never enter your Microsoft or Minecraft password, recovery code, or two-step verification code on a server-list, mod, or "account fixer" site. Real sign-in happens only through the official Microsoft flow.
• Do not install a third-party "session unlocker", cracked launcher, or account tool. Offline or cracked clients cannot pass official username verification and often carry malware or credential theft.
• Do not change your password repeatedly during an active Microsoft/Xbox incident; wait for the official status update, then re-authenticate once services recover.