How to Fix Roblox Error 264 (Same Account on Another Device)

By FixMyError · Updated October 14, 2026 · 8 min read

What error 264 means

Error 264 is one of the least scary Roblox errors, even though its wording sounds alarming. The full message reads something like "Disconnected… Same account launched game from different device. Reconnect if you prefer to use this device." Roblox intentionally stops one account from playing the same experience on two devices at once. That rule exists to keep game states consistent and to protect accounts — if two devices both tried to control the same character, servers would have no idea which one to believe.

In most cases the cause is exactly what it says: you (or someone using your login) started Roblox on a phone, tablet, or second computer and the first session never fully ended. The tricky part is that you do not have to be actively playing on the other device. If the app crashed on your phone, a browser tab stayed open in the background, or the network dropped without a clean logout, Roblox's servers may keep your old session "alive" for a while. Those ghost sessions are the reason many players see error 264 while staring at the only device they own. The fix is almost never on your current device — it is about clearing the stale session on Roblox's side.

Common causes

• Roblox still open on another device: the classic case — you played on your phone, switched to your PC, and the phone app is still running in the background holding your session.
• Ghost sessions after crashes or drops: an app crash, a closed laptop lid, or a network hiccup can leave a session that never logged out. Roblox keeps it alive for a few minutes before giving up.
• Someone else using your account: if a sibling, friend, or stranger logged into your account on their device, their session will trigger error 264 on yours — this is the cause you should never ignore.
• Duplicate browser tabs or app instances: launching Roblox from two tabs, or having both the Microsoft Store app and the browser client open with the same account, counts as two sessions.
• Corrupted local cache or a stuck client: less common, but a damaged cache can keep retrying a bad session state. Clearing the cache usually breaks the loop.

How to fix error 264 — step by step

Work through these fixes in order. Most players are back in the game by step 3 — the later steps only matter if the error keeps returning or you suspect somebody else is on your account.

1. Close Roblox on your other devices. Start with the obvious: check your phone, tablet, laptop, or any browser where you might be logged in, and fully quit Roblox — swipe it out of the app switcher on mobile, quit the app (not just the game window) on PC, and close any Roblox browser tabs. Then wait two to three minutes so Roblox's servers register that the old session ended. Launch Roblox again on your preferred device and try joining. If it works, you are done — make a habit of quitting the app on one device before opening it on another.
2. Log out of all other sessions. If closing the apps did not help, or you cannot reach the other device, force every session to sign out. Open Roblox in a browser, click the gear icon, and go to Settings → Security. Scroll to the "Where You're Logged In" section and choose "Log Out of All Other Sessions". This signs your account out everywhere except the browser you are using right now. Then log back in on just the device you want to play on and rejoin the experience.
3. Wait a few minutes and relaunch. Sometimes the only thing wrong is timing: the old session is dying but Roblox's servers have not noticed yet. Sign out, give it a full two to three minutes, then fully close Roblox on your current device and launch it fresh. Do not mash the play button every ten seconds — each attempt can create a new half-session and reset the clock. One patient relaunch fixes more 264 cases than any cache-clearing trick.
4. Clear Roblox's cache. If the error survives logout and waiting, a corrupted local cache may be replaying a stuck session. On Windows: close Roblox, press Win + R, type %temp%\Roblox, press Enter, select everything (Ctrl + A), and delete it. If that folder does not exist, repeat with just %temp%. On Android: go to Settings → Apps → Roblox → Storage and tap Clear Cache (not Clear Data — you would lose your saved settings). On iPhone, there is no cache button: offload or reinstall the app instead. Restart your device and try again.
5. Secure your account if you don't recognize the session. Back in Settings → Security, the "Where You're Logged In" section lists the date, browser, and rough location of every active login. If you see a device, browser, or city that is not yours, someone else is on your account — and that is your error 264. Change your password immediately (use a strong, unique one you have never used anywhere), then turn on 2-step verification on the same Security page. Changing your password alone forces all sessions to log out, which clears the error as a side effect.
6. Reinstall Roblox as a last resort. If error 264 keeps appearing on one device when no other session exists, the client itself may be in a bad state. Uninstall Roblox completely (on Windows: Control Panel → Programs, or Settings → Apps; on mobile: long-press and uninstall), restart the device so no Roblox process lingers, and install a fresh copy from roblox.com or your device's official app store. Do not install from third-party sites. A clean install with a fresh login almost always ends the stubborn cases.

Did this fix it? Quick checklist

• Roblox is fully closed on every other device, tab, and app instance
• You used "Log Out of All Other Sessions" and signed back in on one device
• You waited a few minutes before relaunching (not just hammering retry)
• You checked "Where You're Logged In" and every session is yours

If error 264 appears only right after switching devices, you just need to be a little more deliberate about closing the old session first. If it appears constantly even on a single device after all six steps, look hard at account security — a persistent mystery session usually means the login details have leaked.