-
Notifications
You must be signed in to change notification settings - Fork 356
Roblox crashes or does not launch
If you're encountering Roblox crashes, or Roblox just doesn't show when it should be launching, it's very likely not a Bloxstrap problem, but is a problem with Roblox itself. Nonetheless, this page should help detail potential solutions.
At the very least, if you're using Bloxstrap, you should first check to see if it's possibly being caused by that. You can do that by temporarily switching back to the normal Roblox bootstrapper. If your problem is only happening with Bloxstrap and is not addressed here, then please open an issue. Otherwise, it's very likely a problem with Roblox itself.
Keep the following in mind: This page is not a definitive guide, but it merely outlines everything that I know. From what I have personally seen, these were the most common solutions that worked. It's possible that these solutions may not apply to you, in which case, I can't really help.
There are several variants of this issue that you can encounter when launching Roblox:
- (a) The RobloxPlayerBeta process exits instantly after trying to launch it
- (b) The RobloxPlayerBeta process stays running, but it just hangs around in the background and doesn't do anything
- (c) Roblox opens, but crashes instantly after opening
- (d) Roblox opens fine, but a crash happens sometime later, and this happens consistently
- (e) An error dialog saying 'Unapproved third-party applications or extensions detected' appears
- (f) An error dialog saying 'Roblox has timed out' appears
Each one of these have their unique traits (identified by the letters), and so each potential fix will be labelled accordingly.
Identify which type of issue you're having, then navigate to a topic which describes your issue:
- (a) (b) (d) (e) Software running on your computer is conflicting with Roblox (→)
- (c) Some files stored in your cache may be problematic (→)
- (a) (b) You're using an Insider Preview build of Windows (→)
- (a) You're using a heavily altered version of Windows (Tiny11, AtlasOS, etc) (→)
- (b) (d) (f) [Bloxstrap only] Your FastFlag configuration is unstable (→)
- (c) [Bloxstrap only] You have a custom font configured (→)
There's a few potential links to this:
-
(a) (b) - If Roblox just generally isn't opening, then it's likely that Hyperion is detecting what it thinks is a cheat. Known cases include:
- GPU tweaking tools, specifically RivaTuner or MSI Afterburner - this can be avoided by making sure they are not active when launching Roblox. They can be reopened after Roblox launches.
- Bad input devices/drivers - make sure that you have no other input devices (game controllers, steering wheels, etc) connected.
- NoMoreCookies - appears to only happen with Bloxstrap, probably because we aren't code signed (source)
-
(d) - If Roblox is crashing around one minute after launching, then it's likely that Hyperion is suspicious of something, and self-crashes after some period of time. This only happens if:
- The application keeps a process handle open for the Roblox game client for at least one minute.
- The application is not code signed.
Known cases of this include:
-
(e) - If you're getting this error dialog, something running in the background is trying to mess with Roblox. The most common case of this are multiplayer games running in the background, like Fortnite, as their anticheats interfere with Roblox.
It's a good idea to briefly examine any utility programs you have installed that are running in the background. If you find any, make sure they're not running and see if anything changes.
There may be some files in your cache that Roblox doesn't like, as a lot of people have noticed that clearing the Windows thumbnail cache turns out to fix any Hyperion related crashes. You can do this by opening Windows Disk Clean-up (cleanmgr.exe
), choosing your Windows drive, and opting to clean up thumbnails.
The Roblox game client is very well known for not working well with Insider Preview builds of Windows. If you're using one and Roblox isn't working for you, this could very likely be the reason as to why.
To possibly resolve your issue, you would either have to wait for a new build to release and see if the issue is fixed by then, or downgrade to an older build, or just stick to using a stable version of Windows.
It should be no surprise that Roblox's anticheat is very picky about the integrity of your system. If you're using a Windows mod that introduces very severe modifications (like Tiny11 or AtlasOS), then it's probably the cause of your troubles. It could be due to missing system files, alterations to system behaviour, etc.
In Tiny11's case, you might be able to restore some files needed by Roblox by installing Microsoft Edge.
If nothing else works, you'll have to bite the bullet and just install a stock version of Windows.
Pro tip: if you really care about "bloat", just install Windows IoT Enterprise LTSC. It's official, stable, and doesn't have most of the crap that probably made installing that Windows mod so alluring.
Important
Please read the warning at the top of 'A guide to FastFlags' if you haven't yet.
Please review what you have configured in the FastFlag editor (that shows the table list). By default, it is empty. If you have opted to add your own flag configurations, or you otherwise find that it is not empty, it is very likely that something in there is making Roblox unstable. Please remove all of them (using Ctrl+A to highlight all) and see if your issue goes away.
Again, we only advise you to use the editor if you know what you're doing. Do not use it to blindly paste in massive lists of flags.
You can back them up beforehand by opening the mods folder, and copying ClientSettings\ClientAppSettings.json somewhere else before you remove them. Afterwards, you can re-import it in the editor.
If you've opted to use a custom font, try removing it. Roblox won't be compatible with all font files, and in some cases an incompatible font can even stop it from launching entirely. If you're running into this problem, your luck might be better using .otf fonts instead of .ttf fonts.
See something here on this page that is incorrect or you otherwise think should be changed? Please open an issue!