Skip to main content

The Virtual device is stuck on "booting" status

  • Updated

You are using a Firewall or a VPN

Please refer to these articles:

ADB versions conflicts

This behavior may also occur when another ADB tool from a third party Android SDK is running and conflicts with Genymotion Desktop built-in ADB.

To solve this:

  1. Make sure that no adb server is running. To kill any running adb servers, you can use the command 
    adb kill-server
    Or kill any running ADB processes.
  2. Set Genymotion Desktop to use your third party Android SDK. Please refer to Genymotion Desktop user guide for details.
  3. If it still does not work, try to reboot the host machine.

If it doesn't help, you may need to revert to Genymotion built-in ADB and make sure that no other ADB services are running before using Genymotion (step 1 from above). However, you will not be able to use Genymotion and your third party ADB tool at the same time in this case.

Intel UHD/HD integrated GPU (Windows only)

Due to compatibility issues with Intel display drivers, Genymotion Desktop does not work well on computers with an Intel integrated GPU on Windows (see The virtual device crashes, freezes or fails to boot on Windows).

Also, many modern computers and laptops have a dual GPU: an NVIDIA/AMD discrete GPU and an integrated Intel GPU. If this is your case, you need to force Genymotion to use the NVIDIA/AMD discrete GPU.

To do so, please follow the instructions from this article: How to force Genymotion Desktop use the high performance discrete GPU on laptops?

VirtualBox

If you are using VirtualBox hypervisor, make sure to use VirtualBox supported versions.

Related articles