The emulator says the GPU driver is unsupported and falls back to software
GPU Driver Warning - Falling Back To SoftwareShort answer
The emulator picks a graphics mode when it starts. On a GPU it does not trust, the automatic mode falls back to software rendering and warns you. Set the AVD graphics to Hardware (host) if you want the GPU, or to Software if the picture is broken. Vulkan on macOS and old drivers are the other usual causes.
Fix it fast
1Find out which cause you have
Start the AVD from the command line with an explicit graphics mode. If it runs cleanly with software but not with host, the GPU path is the problem and the causes below apply.
emulator -avd Pixel_8_API_35 -gpu software2Match what you see, then jump to its fix
- 1
A warning about the GPU driver falling back, and slow renderingAutomatic mode chose software for a GPU it does not supportFix - 2
Crashes or wrong images right after you forced hardware renderingHardware graphics is on, but the driver cannot render the guest correctlyFix - 3
Shader compilation failures, graphical glitches or crashes only in hardware mode on a MacVulkan fails on an Apple silicon Mac in hardware modeFix - 4
vulkan-1.dll cannot be found when the emulator launchesvulkan-1.dll is missing on WindowsFix
- 1
What does the error look like?
GPU Driver Warning - Falling Back To Softwarevulkan-1.dll cannot be foundThe emulator shows crashes or incorrect images after a graphics option was changed
Cause 1 of 4
Automatic mode chose software for a GPU it does not support
1Check
Look at the Graphics setting of the AVD (Device Manager, edit the AVD, Emulated Performance). Automatic lets the emulator decide from your computer, and it can pick software on a GPU it does not recognise.
emulator -avd Pixel_8_API_35 -gpu host2Fix
Force hardware rendering. For images without Google Play, set Graphics to Hardware in Device Manager. For Google Play images, edit config.ini and hardware-qemu.ini in the AVD folder and set hw.gpu.mode to host. The Android team notes this can lower stability, so go back to Software if the picture breaks.
# ~/.android/Pixel_8_API_35.avd/config.ini
# ~/.android/Pixel_8_API_35.avd/hardware-qemu.ini
hw.gpu.mode=host3Verify
The warning is gone and the emulator is smooth. A warning may still show once, which the docs also say can happen.
emulator -avd Pixel_8_API_35 -gpu hostConfirmed by developer.android.com
Cause 2 of 4
Hardware graphics is on, but the driver cannot render the guest correctly
1Check
A graphics option your computer does not support gives crashes or wrong images. Run once with software rendering to confirm.
emulator -avd Pixel_8_API_35 -gpu swiftshader2Fix
Set Graphics to Software in the AVD settings, or start with -gpu software. If you have an Intel GPU, install its latest driver first. If you have both an Intel and a discrete GPU, the emulator docs suggest disabling the Intel one in Device Manager so the discrete GPU is used.
emulator -avd Pixel_8_API_35 -gpu software3Verify
The screen draws correctly. Then try host again after the driver update.
emulator -avd Pixel_8_API_35 -gpu hostConfirmed by developer.android.com
Cause 3 of 4
Vulkan fails on an Apple silicon Mac in hardware mode
1Check
On Apple silicon, hardware mode uses MoltenVK for Vulkan. It does not support every Vulkan feature.
emulator -avd Pixel_8_API_35 -feature -Vulkan2Fix
Either use software rendering (-gpu swiftshader, or Software in the AVD settings), or turn Vulkan off and keep hardware acceleration for GLES apps.
emulator -avd Pixel_8_API_35 -gpu swiftshader
# or keep the GPU for GLES apps:
emulator -avd Pixel_8_API_35 -feature -Vulkan3Verify
The glitches are gone in the app that failed before.
adb devicesConfirmed by developer.android.com
Cause 4 of 4
vulkan-1.dll is missing on Windows
1Check
The emulator build is too old for the machine, or the Vulkan runtime is not found.
emulator -avd Pixel_8_API_35 -gpu host2Fix
In Android Studio open Tools > SDK Manager and update the emulator to the latest stable. If you do not need Vulkan apps, start the emulator with -feature -Vulkan.
emulator -avd Pixel_8_API_35 -feature -Vulkan3Verify
The emulator window opens.
emulator -avd Pixel_8_API_35 -feature -VulkanConfirmed by developer.android.com
How do I stop it coming back?
- Leave Graphics on Automatic until it causes a problem, then change one AVD, not all of them.
- Update the emulator in SDK Manager when you update Android Studio.
- Keep the GPU driver current from the vendor, especially after an OS upgrade.
- Note which -gpu mode works on each machine so a teammate can copy it.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Mobile apps
The Android Emulator will not start with hardware acceleration (HAXM, Hyper-V, KVM)
KVM acceleration can NOT be used
Intel HAXM is discontinued, and current emulators no longer use it.
4 causes, each with a fixMobile apps
adb cannot start because something already holds its port
adb start-server failed
The adb server must bind local TCP port 5037, and every adb client talks to it there.
2 causes, each with a fixMobile apps
adb cannot connect to its daemon or start the server
* daemon started successfully *
The adb server is a background process on your computer that listens on TCP port 5037.
2 causes, each with a fixMobile apps
adb prints 'server version doesn't match this client; killing...'
adb server version doesn't match this client; killing...
adb runs a background server, and every adb command is a client.
3 causes, each with a fixMobile apps
adb tcpip 5555 fails because no device is found
adb: more than one device/emulator
adb tcpip only works while the device is attached and listed by adb, because it tells the phone to start listening on port 5555.
4 causes, each with a fixMobile apps
The Android Emulator says /dev/kvm is not found
KVM acceleration can NOT be used
The emulator wants a hypervisor and cannot find one.
4 causes, each with a fix