The Virtual device takes a very long time to boot and is very slow

Windows specific issues

VirtualBox + Hyper-V

Genymotion Desktop uses VirtualBox hypervisor on Windows by default.

This configuration does not work well with Hyper-V.

Hyper-V can cause crashes and very low performance.

It is therefore recommended to disable Hyper-V completely when using Genymotion.

Please follow the instructions from the article:

Intel UHD integrated GPU

Limited OpenGL support with Intel UHD drivers on Windows can cause Genymotion Desktop to not work well.

Genymotion Desktop does not work well on computers with Intel UHD integrated GPU on Windows, especially laptops.

For more information and possible solutions, refer to .

Laptops with discrete GPU

Many modern laptops and notebooks have integrated and dedicated GPUs.

These GPUs can include an NVIDIA/AMD high-profile discrete GPU and an integrated Intel/AMD GPU.

If this is your case, force Windows to use the high-profile discrete GPU globally. To do so, follow the instructions from

Android 15 & 16

Android 15 and 16 do not work well with VirtualBox hypervisor.

Use QEMU hypervisor instead.

See .

Linux / Mac Intel

Android 15 and 16 do not work well with VirtualBox hypervisor on Linux and Mac Intel.

Use QEMU hypervisor instead.

See the .

Windows

Android 15 and 16 do not work well on Windows hosts at this time.

The virtual device does not have enough resources

If none of the above worked, or if none applies to your case, then the virtual device may not have enough resources.

Recent versions of Android can be demanding on hardware resources.

If the selected does not have enough resources (CPU, RAM) to run Android comfortably, very poor performances and/or crashes can occur.

To avoid this, make sure the virtual device has the following hardware settings:

| Android version | Virtual CPUs | RAM | | Android 14 and above | 4 | 4GB or 8GB (recommended) | | Android 10 - 13 | 2 or 4 (recommended) | 2GB or 4GB (recommended) | | Android 9.0 and below | 2 | 2GB or more |

For more information, please refer to .