Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

The emulator says the GPU driver is unsupported and falls back to software

ErrorGPU Driver Warning - Falling Back To Software

Short 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.

  • Applies to Android Emulator 36.x, Android Studio current stable, Windows 11, macOS 26, Ubuntu 24.04
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 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 software
  2. 2Match what you see, then jump to its fix

    1. 1A warning about the GPU driver falling back, and slow renderingAutomatic mode chose software for a GPU it does not supportFix
    2. 2Crashes or wrong images right after you forced hardware renderingHardware graphics is on, but the driver cannot render the guest correctlyFix
    3. 3Shader compilation failures, graphical glitches or crashes only in hardware mode on a MacVulkan fails on an Apple silicon Mac in hardware modeFix
    4. 4vulkan-1.dll cannot be found when the emulator launchesvulkan-1.dll is missing on WindowsFix

What does the error look like?

  • GPU Driver Warning - Falling Back To Software
  • vulkan-1.dll cannot be found
  • The 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 host

2Fix

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=host

3Verify

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 host

Confirmed by developer.android.com

Did this fix it?

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 swiftshader

2Fix

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 software

3Verify

The screen draws correctly. Then try host again after the driver update.

emulator -avd Pixel_8_API_35 -gpu host

Confirmed by developer.android.com

Did this fix it?

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 -Vulkan

2Fix

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 -Vulkan

3Verify

The glitches are gone in the app that failed before.

adb devices

Confirmed by developer.android.com

Did this fix it?

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 host

2Fix

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 -Vulkan

3Verify

The emulator window opens.

emulator -avd Pixel_8_API_35 -feature -Vulkan

Confirmed by developer.android.com

Did this fix it?

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

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 fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.