For players / ROBLOX
Roblox error 264: check a second device using your account
Find an extra game session, review your own devices and investigate unfamiliar access. Keep each family member on their own account.
Read the whole message #
Roblox associates error 264 with one account attempting to enter the same experience from multiple devices at the same time. Begin with the complete message: keep a screenshot, the experience name, the time and the device that was disconnected. The number suggests an investigation path; it does not identify who made another launch. Avoid diagnosing an account takeover from the code alone, and keep this message separate from a notice that entry to a particular experience is restricted.
Choose one main device for the rest of the checks. You will retry there while looking for an existing game on the other devices. Note what happened immediately beforehand: moving from phone to computer, selecting Play again, returning after a break, or using a shared computer. These are starting conditions against which you can compare the result. An open Roblox webpage does not by itself establish that an experience is running. A website login and an active game connection are different observations.
Open full-size image ↗Check your devices #
Start with devices you actually use: phone, tablet, desktop and laptop. On each available device, inspect whether Roblox is still inside the same experience. Do not select Play just to test the second device; that would create another competing launch. Compare the profile username, since matching display names and similar avatars are insufficient. If someone else is using a device, ask them to check which account and experience are already open rather than asking them to sign in with your credentials.
Consider a hypothetical example: you were playing on a tablet, then opened the same experience on a computer. The tablet still shows the game scene and the computer displays 264. Finish the known tablet game first, then check the computer. If no game scene is visible, record that too; the absence of a window does not establish the cause. You do not need a third-party Roblox tracking service to find a device left elsewhere. For a device you cannot access, use the official account-session controls discussed below.
Open full-size image ↗| What you found | Next step |
|---|---|
| The same game is open on a known device | Finish that launch; retry once on the main device |
| Recognized logins, but no visible running game | Compare devices and timing; an entry does not prove active play |
| A login cannot be explained by your devices | Review account security through official settings |
| 264 remains after launch and session checks | Compare another experience and send the results to support |
Close the extra launch #
On the known second device, leave the experience using its menu and close Roblox. On a computer, check that another client window is not still open; on a phone, close the application through the normal controls for that operating system. You do not need to uninstall Roblox, erase folders or wipe the device for this first check. Return to your chosen main device and make one launch attempt. Avoid repeated clicks and do not open the game on your phone at the same time to see whether it works there.
Describe the actual result: either you enter and keep playing without another 264, or the message returns. If closing a known additional launch helped, record that observation without treating it as proof of somebody else's access. If the message returns, save the new time and review sessions. A common testing mistake is to close Roblox on the phone, automatically reopen it and select Play again. That changes the conditions a second time and makes it difficult to judge the result of the first action.
Use separate family accounts #
If several family members use one login, agree who will finish the current game. Use each person's separate account for future play. Before starting, compare usernames rather than the names displayed above characters. Leaving an experience does not necessarily mean the account has been signed out on a shared device. After using a school or family computer, check whether the profile remains available to the next person. Do not exchange passwords as part of the investigation or ask someone else to test with your login details.
For example, a shared computer might retain an older child's account while a younger child starts the same experience and the older child is playing on a phone. Finish the extra game, sign out of the shared profile and select the appropriate person's own account. Buying Robux, a subscription or an item is not a remedy for this overlap. Separate profiles address an identifiable coordination problem. If 264 persists with one player and one device, however, that agreement does not remove the need for further checks.
Review active sessions #
Sign in through the official Roblox website or application. In account settings, open Security and find Where you’re logged in. Roblox's help describes device details, approximate regional location and activity timing there. Compare the entries with your own recent logins. This is an account-session list rather than an exact map of running experiences. Several entries do not establish that every listed session is currently playing the same game.
You can end a selected session individually, or use Log Out of All Other Sessions while retaining the current one. Before doing so, make sure you can sign back in on your own devices and access your login verification method. An Unknown entry alone does not prove an intrusion: the official explanation includes older inactive sessions with missing details. Location is approximate as well. A separate guide to signing out other devices is linked among this page's related materials. Avoid putting screenshots containing private session information in a public discussion.
Respond to unknown access #
If an entry cannot be explained by your devices, give account security priority. Open the official settings on a device you trust. Where malware or a suspicious extension is a concern, follow the official recovery sequence: remove the threat, then change the password and configure two-step verification. End additional sessions using the official controls. Clearing application data is not a substitute for these actions and does not show whether another person has lost account access.
If you cannot sign in anymore, use official recovery and Roblox Support. Nobody on our website needs your password, cookies, backup code or verification code to repair 264. Do not share these with someone offering a paid device-disconnection service either. Restore control of the account before resuming game tests. An error message and a security problem can occur together, but account recovery is a separate task. Repeatedly launching the experience cannot replace it, and an unexplained entry deserves investigation even if the next game launch succeeds.
Open full-size image ↗Retry without competing launches #
After closing known extra launches, restart Roblox on the main device and try the same experience once. If 264 returns, compare one other available experience using the same account, device and connection. Record both results. This comparison helps describe the scope of the problem; it does not establish a cause or require a new account. If another experience opens, avoid declaring the first one broken without additional evidence.
Check the official Roblox Status page. During a reported incident, retry after recovery is announced. The absence of a general incident does not guarantee that an individual client is functioning correctly. If an update is needed, obtain it from the official application source. Consider reinstalling only after reviewing additional launches and sessions, with account access prepared beforehand. Older operating systems named in some error instructions do not establish today's requirements. Avoid bulk folder-deletion commands and tools advertised as bypassing simultaneous-login restrictions.
Provide a clear account of events #
If 264 persists, prepare a short support report: username, experience URL, date and time with timezone, device, operating system, complete message and the stage at which it appears. List completed checks together with their outcomes. For instance: “Left the experience on the tablet, closed the app and launched once on the computer; 264 returned.” Describe the session review without exposing private details. Send account and client issues through official Roblox Support; the experience creator can address questions about their game but cannot restore a Roblox account.
This is a suggested report, not a tested player's story: “264 appeared after moving from phone to PC. I closed the phone game. Another experience starts on the PC, but the original one still shows the message.” Replace every detail with your own and do not claim checks you did not perform. Keep the original screenshot for support and remove private information from any public version. A clear sequence and a result for each action are more useful than a long list of random settings: they let the next person continue from a known state.
Original sources
Roblox SupportRoblox Support — Session Management
Roblox Support — Account Recovery
Roblox Support — Account Safety
Roblox Support — Contact Us
Roblox Status
