Roblox kicked you out of a game with "Same account launched experience from a different device (Error Code: 264)." In plain words: your account is inside a game on two devices at once, or Roblox thinks it is.
Roblox only allows one active game session per account. That is partly there to protect your account, but most 264s are caused by a leftover session, not by someone stealing your login.
| Situation | Do this |
|---|---|
| Roblox is open on another device | Close it there, then rejoin |
| Roblox just crashed or you just left a game | Wait a minute, then rejoin |
| It keeps happening | Log out of all other sessions |
| You never opened a second device | Run the security check below |

How to fix it, most likely first
1. Close Roblox on every other device
The most common cause is exactly what the message says: your account is in a game somewhere else.
- Check your phone, tablet, console, and any other PC you play on.
- Fully close Roblox on each one. On mobile, force close the app, because leaving it in the background keeps the session alive.
- Rejoin the game on the device you want to play on.
2. Wait a minute if Roblox just crashed or you just left
A crash, a force close, or rejoining too fast can leave a ghost of your old session behind, and Roblox counts it as a second device. Joining from the website while the app is still shutting down can do the same thing.
- Fully quit Roblox on the device you are using.
- Wait a minute or two so the old session can expire.
- Rejoin the game, ideally from inside the Roblox app.
If a crash kicked this all off, the fix for "An unexpected error occurred and Roblox needs to quit" deals with the crash popup itself, and there are separate steps when Roblox keeps closing on PC.
3. Log out of all other sessions
One click kicks every other device off your account instantly, ghost sessions included.
- Sign in at roblox.com and click the gear icon in the top right.
- Open Settings, then Security.
- Scroll to Where You're Logged In.
- Click Log Out of All Other Sessions.
- Rejoin the game.
4. Clear Roblox's local data and reinstall
If 264 still shows up, Roblox's official advice is to clear the app's local data and, if needed, reinstall.
- Windows: press Win + R, type
%temp%, and delete the Roblox folder. - Mac: in Finder, choose Go > Go to Folder, open
~/Library/Caches, and delete com.roblox.com. - Mobile: delete the app, restart the device, and reinstall. Also check that the date and time are set correctly.
- Still stuck? Reinstall from the official Roblox download page and try a different internet connection, like a phone hotspot.
Reinstalling never touches your account or items. Everything is saved on Roblox's servers.
One heads-up: the exact same message sometimes appears as Error Code 273 right after a game teleports you between its own places. That one is on the game's side, not yours. Just rejoin.
If you never opened Roblox on a second device
If 264 keeps appearing and you know nothing else was running, spend two minutes ruling out the bad case: someone else using your account.
- Go to Settings > Security > Where You're Logged In.
- Look for a device, browser, or location you do not recognize.
- If you find one, click Log Out of Session next to it.
- Change your password and turn on 2-Step Verification.
Do not panic if the list looks clean. Glitches trigger 264 far more often than stolen accounts, and players with 2-Step Verification already on still hit it. The check just makes sure you are in the harmless group.
If you keep getting kicked after all of this, contact Roblox Support and describe what is happening. And if a different error number shows up instead, the full list of Roblox error codes and fixes covers each one, including the launch popup "An error occurred and Roblox cannot continue".









