Error Code: 0x89245111 Code: Swamp in Minecraft Launcher — Causes and Fixes

If the Minecraft Launcher stops you at sign-in with error code: 0x89245111 code: swamp, alongside messages like “Oh no! Something went wrong, and we couldn’t connect to the Minecraft services” or “We were unable to verify what products you own,” you are looking at a Microsoft account token failure — not a ban and not a broken game install.

In Microsoft’s own Game Development Kit (GDK) error reference, 0x89245111 is defined as E_GAMEUSER_FAILED_TO_GET_TOKEN — “The token request failed.” The launcher asked Microsoft’s sign-in system for an authentication token and never got a valid one back. “Swamp” is simply the Minecraft-themed code word the launcher attaches to the number, in the same family as Creeper, Crossbow and Glowstone.

This guide explains every cause and walks through the fixes in order, from the 30-second checks to the official repair tool.

Minecraft error code: 0x89245111 code: swamp sign-in error in the Minecraft Launcher
The Swamp code appears at sign-in, when the Minecraft Launcher cannot get a valid Microsoft account token. Image: TechFixIT / YouTube.

What Causes Error Code: 0x89245111 Code: Swamp?

Anything that breaks the sign-in chain — launcher → Microsoft account token → Minecraft services verifying the token and your game ownership — can produce this code:

  • A Minecraft/Microsoft authentication outage. This is the biggest trigger. The code spiked during the June 2026 authentication outages (June 1 and June 3), when login servers were down for hours and thousands of players were locked out at the same time.
  • A stuck or expired sign-in session on your PC — a frozen launcher or a stale cached token.
  • Account mismatch: the Minecraft Launcher, Microsoft Store and Xbox app signed in with different Microsoft accounts.
  • A wrong system clock, which makes secure token validation fail.
  • Network interference: a VPN, firewall, DNS problem or ISP block standing between you and Microsoft’s authentication endpoints.
  • Corrupted launcher files or a broken Gaming Services package, the Windows component that ties Store, Xbox and launcher licensing and sign-in together.

Fix 1 — Check for an Outage Before You Touch Anything

If this error appeared suddenly, first check whether Minecraft’s authentication is down for everyone (player reports on Downdetector and status trackers are the fastest signal). The tell-tale signs: other players reporting the same error in the same hour, Realms and the Marketplace failing too, third-party launchers failing as well, and the launcher acting as if you do not own Minecraft. During an outage no local fix works — and do not buy Minecraft again. Your ownership comes back on its own when the servers recover. Wait, then restart the launcher and sign in again.

Fix 2 — Fully Close the Launcher and Restart Your PC

Exit the Minecraft Launcher completely, open Task Manager (Ctrl + Shift + Esc) and end any lingering Minecraft Launcher or Java processes, then reopen it. If it still fails, restart the whole PC — this clears a stuck session. If you have been hammering the sign-in button repeatedly, also give it a rest for 15–30 minutes before trying again, in case the repeated attempts have tripped a temporary limit.

Fix 3 — Sign Out Everywhere, Then Sign In With the Same Account

Account mismatch is one of the most common local causes. Sign out of the Minecraft Launcher, restart it, and sign back in with the Microsoft account that actually owns Minecraft (or holds the Game Pass subscription). Then open the Microsoft Store and the Xbox app and confirm all three apps are signed in with that same account — update the apps if they ask. Also refresh the token through the Xbox app: sign out, wait about 30 seconds, sign back in, then launch Minecraft again. The launcher reuses the Xbox app’s Microsoft session, so this often clears the token failure on its own.

Fix 4 — Set Your System Clock to Automatic

A wrong date or time quietly breaks Microsoft token checks. Go to Settings → Time & language → Date & time, turn on Set time automatically and Set time zone automatically, click Sync now, then restart the launcher.

Fix 5 — Rule Out Your Network (VPN, DNS, ISP)

Turn off any VPN or proxy and try again. To test whether your network is the problem, connect through a different network — a phone hotspot is the quickest test. If the hotspot works, your home network or DNS is blocking Microsoft’s sign-in endpoints. In that case, switching to a public DNS often fixes it:

  1. Open Control Panel → Network and Sharing Center → Change adapter settings.
  2. Right-click your active connection → Properties → Internet Protocol Version 4 (TCP/IPv4) → Properties.
  3. Choose “Use the following DNS server addresses” and enter 8.8.8.8 (Preferred) and 8.8.4.4 (Alternate).
Setting Google DNS 8.8.8.8 and 8.8.4.4 in Windows IPv4 properties to fix Minecraft sign-in errors
Entering Google’s DNS servers in the IPv4 properties of your network adapter. Image: TechFixIT / YouTube.

You can also flush the old DNS cache: open Command Prompt as administrator and run ipconfig /flushdns, then ipconfig /release, then ipconfig /renew, and restart your PC.

Fix 6 — Clear Stale Saved Credentials

Old Xbox/Mojang sign-in entries can keep a dead token alive. Press Win + S, open Credential Manager → Windows Credentials, and remove entries containing Xbl, entries containing Mojang, and any entry for your Microsoft account email. Restart the PC and sign in fresh in the launcher. One step further: close the launcher, open %AppData%\.minecraft, delete the launcher_accounts.json file, then relaunch and sign in again — the launcher rebuilds it with a clean session.

Fix 7 — Repair (Then Reset) the Minecraft Launcher

Corrupted launcher files produce this error even when your account is fine. Go to Settings → Apps → Installed apps → Minecraft Launcher → Advanced options. Click Repair first — it rebuilds damaged files and keeps your data. Only if Repair does not help, use Reset (back up your worlds first, since Reset removes data that is not saved to the cloud). Game Pass players should also open the Xbox app, find the Minecraft Launcher entry, and run Manage → Verify and Repair to re-validate the license files.

Fix 8 — Run the Official Gaming Services Repair Tool

If the error survives everything above, the Gaming Services package is the prime suspect — it handles the licensing and sign-in link between the Microsoft Store, the Xbox app and the launcher. Microsoft’s official fix is the Gaming Services Repair Tool for PC from Xbox Support: download it, run it, and let it check system issues and update the Xbox app and Gaming Services.

Microsoft Gaming Services Repair Tool checking system issues and updating the Xbox app
The official Gaming Repair Tool checking system issues — it reports “Succeeded” line by line as it repairs Gaming Services and the Xbox app. Image: TechFixIT / YouTube.

If the tool cannot fix it, reinstall Gaming Services manually: open Windows Terminal or PowerShell as administrator, run get-appxpackage Microsoft.GamingServices | remove-AppxPackage -allusers, then run start ms-windows-store://pdp/?productid=9MWPM2CQNLHN and install Gaming Services from the Store page that opens. Restart your PC afterwards.

Fix 9 — Clean Reinstall (Last Resort)

Only when services are confirmed online and every fix above has failed: back up your worlds, uninstall the Minecraft Launcher, reinstall it, and then reinstall the Java and Bedrock editions. A fresh install clears deep file corruption — but remember, reinstalling does nothing at all while an authentication outage is still running.

What NOT to Do

  • Do not repurchase Minecraft when the launcher says it cannot verify what you own — that message is the outage/token failure, not a lost license.
  • Do not delete your worlds, instances or modpacks — a sign-in error never requires it.
  • Do not keep unlinking and relinking accounts, and do not factory-reset your router if every other online service is working fine.

FAQs

Is error code: 0x89245111 code: swamp a ban?

No. Error code: 0x89245111 code: swamp is a sign-in token failure (E_GAMEUSER_FAILED_TO_GET_TOKEN in Microsoft’s GDK reference). It says nothing about your account standing — it only means the launcher could not get a valid authentication token from Microsoft at that moment.

Why does error code: 0x89245111 code: swamp appear for everyone at the same time?

Because the failure is often on Microsoft’s side. When Minecraft’s authentication servers go down — as they did during the June 1 and June 3, 2026 outages — every player’s token request fails at once, and this code appears at scale. In that case the only fix is waiting for the services to recover.

What is the fastest fix for the Swamp error when it is only happening to me?

Work in this order: fully close the launcher in Task Manager and restart your PC, sign out of the Xbox app and back in to refresh your token, make sure the Launcher, Microsoft Store and Xbox app all use the same account, and confirm your system clock is set to automatic. Those four steps cover the most common local causes.

Will repairing or reinstalling Gaming Services delete my Minecraft worlds?

No. Gaming Services is a Windows licensing/sign-in component, separate from your game files. Repairing or reinstalling it does not touch your worlds. The only step in this guide that can remove local data is a launcher Reset, which is why you should back up your worlds before using it.

Does the Swamp error also affect third-party launchers like Prism?

Third-party launchers do not show the “Swamp” name, but they fail at the same moment with token, session or ownership errors, because they rely on the same Microsoft/Minecraft authentication. During an outage, do not remove your account from a third-party launcher — you may not be able to add it back until the services recover.

More Guides You May Like

Leave a Reply

Your email address will not be published. Required fields are marked *