Product docsAndroid emulator servers
Android emulator troubleshooting: virtualization, Hyper-V and graphics
Fix Android emulators on a HyperDC server: virtualization shown as off, Hyper-V conflicts and permissions, black screens, slow instances and apps that refuse.
- Intermediate
- 15 min read
- Updated
On this page
Most emulator problems come from four places: hardware virtualization, a hypervisor conflict on Windows, the graphics settings, or resources. Find your symptom below.
Before you start
- Note the emulator, its version and the exact error message, and take a screenshot.
- On Windows, sign in as an administrator; some fixes need a restart.
"Virtualization is disabled" or "VT-x is not available"
The emulator does not get the processor's virtualization extensions.
- Check what Windows sees:
Get-ComputerInfo -Property HyperV*
systeminfo | findstr /i "Hyper-V"- On an Android GPU server, a VDS or a nested dedicated server, the extensions are provided. If Windows reports them as unavailable, restart the server once, then open a ticket with this output.
- On a VPS, emulators cannot use hardware virtualization; move to a VDS, a nested dedicated server or an Android GPU server.
More checks for all hypervisors: nested virtualization problems.
The emulator conflicts with Hyper-V
- BlueStacks: BlueStacks states that versions 5.20 and later run with Hyper-V on or off, and that its website installs the matching build. With Hyper-V on, BlueStacks needs your user in the Hyper-V Administrators group; add it in an elevated prompt and restart:
net localgroup "Hyper-V Administrators" YourUserName /add- Other emulators that require Hyper-V to be off: turn off the Windows hypervisor and restart. This also stops WSL 2 and Hyper-V virtual machines:
bcdedit /set hypervisorlaunchtype offTurn it back on later with bcdedit /set hypervisorlaunchtype auto and a restart.
- Google's Android Emulator on Windows uses the Windows Hypervisor Platform: turn it on in Turn Windows features on or off and restart.
Black screen, stuck loading or graphics errors
- Switch the emulator's graphics renderer (for example between DirectX and OpenGL) in its settings and restart the instance.
- Install the current graphics driver from the GPU maker; BlueStacks lists up-to-date graphics drivers among its requirements.
- Lower the resolution and frame rate, especially with many instances.
- Update the emulator to its latest version.
Instances are slow or crash
- Check CPU and memory in Task Manager. If they are near their limit, stop instances or reduce their resources; see run many emulator instances.
- Free disk space: each instance stores a full Android system.
- Restart instances that have been running for days.
The emulator closed after a restart or update
Windows updates can restart the server. Set updates to download only and install them in a maintenance window (fix Windows Update problems), and set the emulator to start after sign-in (getting started).
An app refuses to run or cannot sign in
- Apps that detect emulators refuse to run; this is the app's choice.
- For sign-in problems, check that the Android system's date and time are correct and that the emulator has internet access.
Next steps
- Linux servers: Android Emulator on a Linux server.
- Back to the start: Android emulator servers: getting started.
Frequently asked questions
Do I have to turn Hyper-V off for my emulator?
Not always. BlueStacks states that versions 5.20 and later run with Hyper-V on or off. Older emulator versions may need Hyper-V off, which also turns off WSL 2 and Hyper-V virtual machines.
Why does an app say it cannot run on an emulator?
Some apps, such as certain banking apps and games with anti-cheat systems, detect emulators on purpose. No server setting changes this; use those apps on a phone.
Can I update the emulator myself?
Yes. Download updates only from the emulator maker's official website or from the emulator's built-in updater.
When should I open a ticket?
When the server reports no hardware virtualization at all, or when the emulator fails after you tried the fixes here. Include the emulator name and version and the exact error message.