Roblox keeps crashing on launch, the most recent thing done was to do a Defender Offline Scan.

You're welcome!

We're glad that we were able to assist you with your concern today.

Yes, restart is indeed, very helpful and easy to perform troubleshooting because it helps your computer to clear up its memory/RAM.

Please do not hesitate to ask the community anytime just in case you have any questions in the future.

Happy Holidays to you!

Regards,

Thank you Kathy.

Although a simple restart didn't fix the issue.
The combination of Uninstalling, restarting and than reinstalling and restarting again did fix the issue of it crashing at launch.

Though I will keep these steps in mind for future troubleshooting attempts.

Hello,

Thank you for posting in Microsoft Community.

We understand that you're trying to launch Roblox. Game launching issues happens when there is compatibility issue, third-party software preventing the game to launch and issues with either the game or PC.

Based on the information you provided, it seems that you have already taken some steps to troubleshoot the issue. Since you have already reinstalled Roblox and updated your drivers, the next step would be to try resetting the app. Here's how you can do it:



1. Press the Windows key + I to open Settings.

2. Click on Apps.

3. Scroll down and find Roblox.

4. Click on it and select Advanced options.

5. Scroll down and click on Reset.



If resetting the app doesn't work, you can also try running Roblox in compatibility mode. Here's how:



1. Right-click on the Roblox shortcut and select Properties.

2. Click on the Compatibility tab.

3. Check the box that says "Run this program in compatibility mode for:"

4. Select Windows 8 from the drop-down menu.

5. Click Apply and then OK.

Then, you may try the troubleshooting you have not tried for Xbox app game launching issues here: Troubleshoot issues with the Xbox App for Windows



If issue still persists, you can try contacting Roblox support for further assistance.

Sincerely,



Microsoft Community Moderator

Thank you for your response.

I would highly suggest you run the Microsoft Defender Offline. It is an offline scanning tool that runs from a trusted environment to help you protect your device from viruses and other malicious software without starting your operating system. Here's how:

Save any open files and close all apps and programs.

Select Start, and then select Settings > Update & Security > Windows Security > Virus & threat protection.

On the Virus & threat protection screen, do one of the following:

In an up-to-date version of Windows 10 or Windows 11: Under Current threats, select Scan options.

In older versions of Windows 10: Under Threat history, select Run a new advanced scan.

Select Microsoft Defender Offline scan, and then select Scan Now.

You'll be prompted that you're about to be signed out of Windows. After you are done, your PC should restart. Microsoft Defender Offline will load and perform a quick scan of your PC in the recovery environment. When the scan has finished (usually takes about 15 minutes), your PC will automatically restart.

NOTE: You typically need administrator rights on the PC on which you plan to run Microsoft Defender Offline.

If you experience a Stop error on a blue screen when you run the offline scan, restart your device and try running a Microsoft Defender Offline scan again.

To see the Microsoft Defender Offline scan results:

Select Start, and then select Settings > Update & Security > Windows Security > Virus & threat protection.

On the Virus & Threat protection screen in Windows 10, under Current Threats, select Scan options, and then select Protection History (In previous versions of Windows it may say Threat history).

Reference link: https://support.microsoft.com/en-us/windows/hel...

Okay so the only thing that's popping up for application logs at the time of an attempted launch is something to do with windows defender. "Updated Windows Defender status successfully to SECURITY_PRODUCT_STATE_ON."

Update edit: After tying again it seems that error in event viewer isnt even related to the crash.