How to Fix mBot “Sorry, this application cannot run under a virtual machine” Error
How to Fix mBot “Sorry, this application cannot run under a virtual machine” Error
If you’re trying to run mBot for Silkroad Online and hitting the dreaded “Sorry, this application cannot run under a virtual machine” wall, you aren’t alone. The frustrating part? Most users getting this error aren’t even using a Virtual Machine (VM).
This happens because mBot’s security packer (Themida/VMProtect) detects certain Windows features as “virtual environments” and shuts down to prevent debugging or cracking.
Here is the quick fix to get your bot back up and running on Windows 10 or 11.
The Main Culprit: Hyper-V
Windows has a built-in virtualization layer called Hyper-V. Even if you don’t have VMware or VirtualBox installed, Hyper-V might be running in the background, tricking mBot into thinking it’s inside a VM.
Step 1: Disable Hyper-V via Windows Features
- Press the Windows Key, type “Turn Windows features on or off,” and hit Enter.
- Look for Hyper-V and uncheck it.
- Also, uncheck Virtual Machine Platform and Windows Sandbox if they are enabled.
- Click OK and Restart your PC.
Step 2: The “Hard” Kill (Command Prompt)
Sometimes Windows keeps the hypervisor active even after unchecking the boxes. To force it off:
- Right-click the Start button and select Command Prompt (Admin) or Terminal (Admin).
- Type the following command and press Enter:
bcdedit /set hypervisorlaunchtype off - Restart your computer. This is the most effective fix for 99% of users.
Note: If you ever need to turn it back on for work or school (e.g., for Docker or WSL2), just run the same command but change
off to auto.Still Not Working? Check for “Core Isolation”
Windows 11 has a security feature called Memory Integrity (part of Core Isolation) that uses virtualization.
- Go to Windows Security > Device Security > Core Isolation details.
- Toggle Memory Integrity to Off.
- Restart your machine.
Final Word
mBot is a classic tool, but its protection system is a bit dated and oversensitive to modern Windows security features. Disabling the hypervisor usually does the trick.
Happy Grinding!
Shortlink for this post:
Link copied to clipboard!
