Thank you for sending us the crash dump, and based on it, we have found that the reason for the crash was Hyperion detecting what we call “badware.” Badware is typically some form of cheat software, but it could also be malware on your machine or a badly written driver.
We recommend performing a clean boot and attempting to run Roblox again. Additionally, as a precaution, we recommend thoroughly cleaning your computer using various virus scanners and malware removers.
I have another Roblox installation on a Windows 10 VMware.
There, I called Roblox Player, it auto-updated and then crashed (it didn’t even enter the game).
Then I performed all the steps for the clean boot, I did the boot, but it keeps crashing.
We received your crash dump, and as you mentioned, all of them show that the Roblox client is being executed in a virtual machine. Currently, Hyperion intentionally crashes clients that are executed on a VM.
Ok, before I have a psychotic break with your statement, I need to make it clear that I have been using Roblox Player (for years) in a VM simply because Roblox Player does not allow multiple simultaneous instances with different users in the same Windows session.
Testing my game on Roblox Player in a VM is the only way I’ve found to be able to test multi-user behavior with real users.
Preventing Roblox Player from running in a VM will simply prevent me from testing my game.
Now, I think it’s clear that a multi-billion dollar company like Roblox is always looking to improve their products, rather than going backwards like in this case. So, I think, Roblox must certainly have a Plan B, like allowing me to install a 32-bit version of the Roblox Player or anything else that allows me to test my game in a VM…
There are tools available to accommodate multiple instances (I can neither confirm nor deny if they are functional on zwinplayer64, that you will have to see for yourself), you can also use Microsoft Store Roblox in addition to zwinplayer64.
I didn’t need to do a clean boot.
I found that this crash, in my case, occurs when I have the Process Lasso program active. So, there is no “badware”, no “badly written driver”!
I use this Process Lasso to weight down concurrent processes.
It works perfectly, and it always has, but now with this new version of Roblox Player, the Player crashes.
The only way now to run my Roblox Player is to CLOSE this program first.
This is inconceivable!
Thank you for your feedback. We are pleased to hear that you were able to identify the issue. To provide further clarification, the term badware refers to unsigned software that opens a write handle to the Roblox client process. This does not necessarily mean it is malicious software. Another program that falls under this category is dtrace as we just discovered.
Unless there are further issues you would like to report, I’m going to go ahead and close this ticket.