Roblox Error 264: Same Account on Two Devices Fix

Updated November 6, 2026

Roblox Error Code 264 appears when the same account tries to play the same game on two devices at once. Roblox’s own definition: “Error code 264 occurs when the same account attempts to access the same game from multiple devices simultaneously.” The fix is simple in principle — close the Roblox session on the first device — but the practical path depends on which device holds the stale session and how to end it cleanly. This guide walks through every platform’s steps, verified from Roblox Support on 6 November 2026.

Source: Roblox Support — Error Code 264: Same account launched experience from different devices.

Why 264 appears

Roblox allows a single account to be logged in on multiple devices, but only one device can actively play the same game at the same time. If a second device tries to launch the same experience while a session is already active on the first device, Roblox blocks the second attempt and shows 264.

Three common scenarios that produce 264:

• You logged in on your phone, left Roblox running, then tried to log in on the computer.
• Your account is logged in on a shared console (Xbox, PlayStation) that someone else left running.
• Your account was hacked and the attacker is actively playing on another device.

The last scenario is rare but important — if 264 appears persistently with no obvious device holding the session, the account may be compromised. See our hacked account recovery guide.

How to end the other session

Four paths to close the active session on another device:

1. Physically close the Roblox app on the device holding the session.
2. Change the account password. Changing the password signs out every device. Any subsequent login requires the new password.
3. Use the Roblox Account Sessions tab in Settings → Security to view active sessions and sign devices out remotely.
4. Wait a few minutes. If a session was abandoned (device turned off, app crashed), Roblox usually clears it after a short timeout.

The password change is the nuclear option — it works on every device but requires you to log in again on each device you want to keep active.

Windows 7, 8.1, 10 fix

If 264 persists after closing other sessions, Roblox’s reinstall path on older Windows:

1. Start → Settings → Apps & features → Roblox → Uninstall.
2. Win+R → CMD → cd AppDataLocal → rmdir /s Roblox → confirm with y.
3. Restart the computer.
4. Reinstall from the Roblox website or Microsoft Store.

Roblox’s description of the AppData wipe: “This gets the access cache build-up cleared from your system, i.e., clearing the app’s data restores the app to its default settings and clears all stored app data.”

Windows 11 fix

On Windows 11, uninstall through Control Panel:

1. Taskbar search → Control Panel → open.
2. Programs → Programs and Features → right-click Roblox → Uninstall or Uninstall/Change.
3. Same AppDataLocal wipe with command prompt.
4. Restart and reinstall.

The cleanup clears any stuck session tokens the client may have cached locally.

macOS fix

Mac uninstall has three valid paths per Roblox’s article: drag Roblox to Trash, Move to Trash from the menu bar, or Command-Delete from Launchpad.

After reinstall, open System Settings → Privacy & Security and grant Roblox permission. Roblox’s exact line: “Open Privacy & Security settings, then turning on permission for the Roblox app.”

iOS, Android, Fire, and Chrome OS

Mobile devices share the same four-step pattern:

1. Reboot the device.
2. Force-close the Roblox app (swipe up from Recent apps).
3. Uninstall and reinstall from the platform’s app store.
4. Check date and time (Roblox requires accurate device clock).

Chrome OS adds an initial step: update the Chrome OS itself before reinstalling Roblox. Roblox’s note: “Update the chrome OS (Helps run the application with maximum optimization).”

When 264 signals an account compromise

Three warning signs that 264 is not a benign dual-device error:

• 264 appears repeatedly within hours even after signing out everywhere.
• Your Roblox account shows activity you did not perform — trades, purchases, friend requests, games joined.
• The Account Sessions tab shows a device you do not recognise.

If any one of these matches, treat 264 as a possible account compromise. Change the password, enable 2-Step Verification via authenticator app, and review trade/payment history. Our hacked account recovery guide covers the full response.

Preventing 264 in the future

Three habits that prevent 264:

1. Explicitly close Roblox before switching devices, rather than just locking the screen or switching apps.
2. Review Account Sessions in Settings every month. Sign out devices you no longer use.
3. Enable 2-Step Verification so any login attempt requires a second factor, which prevents accidental dual-logins and blocks unauthorized access entirely.

Shared accounts — where friends or siblings use the same Roblox credentials — are the single most common 264 source. If multiple people play the same account, coordinate so only one plays at a time.

When reinstall is actually needed

Most 264 errors clear by closing the other session — no reinstall needed. The reinstall path from Roblox’s article is for cases where 264 persists after the obvious session-closing fix:

• A Windows installation with a stuck session token in the AppData cache.
• A mobile installation with a corrupted login state.
• A Mac client missing the Privacy & Security permission.

Try the simple session-closing fix first. Reserve the full reinstall for cases where 264 keeps returning without an obvious second device.

How 264 interacts with device types

Three device categories have different 264 patterns:

• PC and Mac. Easy to force-close via Task Manager or Activity Monitor. The Roblox desktop client is a visible process; killing it clears the session immediately.
• Mobile (iOS, Android). Swipe up from Recent apps and dismiss the Roblox card. Background app refresh sometimes keeps the session alive even after the app looks closed — on iOS, Settings → General → Background App Refresh → Roblox: Off to be safe.
• Console (Xbox, PlayStation, Switch). Many consoles put apps in a “Quick Resume” state when switching, which keeps the Roblox session alive in the background. Explicitly close Roblox from the console’s running-apps menu, not just by switching to the home screen.

Consoles are the single most common 264 source for shared household accounts. The Xbox may hold a Roblox session for hours after the player seemingly stopped playing.

Family accounts and 264

Two patterns that create persistent 264 errors in family-shared accounts:

1. Multiple children using one account. If two kids share a Roblox login, one stays logged in on the TV console while the other tries to play on a tablet. Both try the same popular game and 264 appears.
2. Parents sharing with children. An adult logs in on a work laptop for curiosity, forgets, and 264 appears when the child tries the same game on the home computer.

The clean fix is one account per player. Roblox accounts are free to create, so every family member should have their own. Account-sharing creates 264 errors and also confuses the age-rating system Roblox uses to filter age-appropriate content.

Signs you can ignore 264 for now

Three cases where 264 is a transient glitch and no action is needed:

• The error appears once and disappears on retry. A brief session handoff produced it; it’s gone.
• You know exactly which other device holds the session. Close that device’s Roblox and retry; 264 should clear immediately.
• You just restarted or switched devices. The previous session is still clearing on Roblox’s servers; wait 30 seconds and retry.

If 264 keeps appearing across these cases, move to the fuller fix sequence — close all sessions explicitly, change password, or run through the reinstall if the local client is the problem.

FAQ

What does Roblox Error 264 mean?

Roblox’s own definition: “Error code 264 occurs when the same account attempts to access the same game from multiple devices simultaneously.” The account is trying to play the same specific experience on two devices at the same time.

How do I quickly fix Error 264?

Close the Roblox app on every other device the account is logged into. If the app is already closed on all other devices, change the account password — this signs out every session automatically.

Can I use the same Roblox account on two devices at once?

Yes, but only if you are playing different games on each device. 264 specifically triggers when both devices try to join the same experience. Different experiences on different devices work fine.

Why does 264 keep coming back?

If 264 recurs after closing all obvious sessions, the account may be compromised and an attacker is logging in from an unknown device. Change the password, enable 2-Step Verification, and review Account Sessions in Settings for devices you do not recognise.

Does reinstalling fix 264?

Only in specific cases — a corrupted local session token, a missing permission, or a cached login state. Most 264 errors clear by simply closing the other session. Try the session-closing fix before reinstalling.

Is 264 the same as 266?

No. 264 is “same account on multiple devices” — a session-conflict error. 266 is “your connection timed out” — a network error. Different causes, different fixes.

Why does Roblox restrict same-account multi-device play?

To prevent account-sharing abuse and to ensure a single avatar’s inventory state is consistent on the server. If two devices could play the same character in the same game at once, trades, purchases, and progress would conflict.

Related error codes

• Error 277 — connection lost mid-session.
• Error 279 — failed to connect to game.
• Full Roblox error codes table.
• Roblox hacked account recovery.
• Add 2-Step Verification to your Roblox account.
• Roblox account recovery — forgot password flow.

For Roblox tools to pair with your account after fixing 264, see the Roblox tools hub with the Robux-to-USD converter and the Premium monthly calculator.