Repository navigation
Description
Description
The VirtIO GPU driver in the Windows 11 ARM guest does not provide Direct3D 9 at all: creating a Direct3D 9Ex device fails with D3DERR_NOTAVAILABLE (0x8876086A). The driver also exposes no Direct3D 12, so Windows cannot fall back to its D3D9On12 layer either. As a result, every WPF application that uses Microsoft's WebView2CompositionControl crashes on startup, because that control hands WebView2 content to WPF through D3DImage, which only accepts Direct3D 9Ex surfaces.
Affected in practice: Hottgenroth Energieberater 14.1 (x64, .NET Framework 4, WPF, Microsoft.Web.WebView2.Wpf 1.0.3967.48) is unusable in the VM.
Second, related bug: disabling the VirtIO GPU at runtime crashes dwm.exe and explorer.exe (see Current Behavior).
Steps to Reproduce
- Create a Windows 11 ARM64 VM in VMPal with the default VirtIO GPU (Red Hat VirtIO GPU 3D controller, driver 100.6.101.58000).
- Run the attached
d3d9_repro.py(ctypes only): it callsDirect3DCreate9Ex, thenIDirect3D9Ex::CreateDeviceEx(adapter 0, HAL, windowed, 1×1 back buffer), with hardware and with software vertex processing. - Alternatively start any WPF app that uses
WebView2CompositionControl, e.g. Hottgenroth Energieberater 14.1. - For the second bug: while the VM is running, disable the GPU with
pnputil /disable-device(or in Device Manager).
Current Behavior
-
Direct3DCreate9Ex: S_OK, 1 adapter ("Red Hat VirtIO GPU 3D controller") -
CreateDeviceExwith HARDWARE_VERTEXPROCESSING:0x8876086A D3DERR_NOTAVAILABLE -
CreateDeviceExwith SOFTWARE_VERTEXPROCESSING:0x8876086A D3DERR_NOTAVAILABLE -
Same result with x64 Python (emulated) and native ARM64 Python, so it is not only an x64 emulation issue.
-
Energieberater crashes right after the splash screen:
System.Runtime.InteropServices.COMException (0x8876086A)
at Microsoft.Web.WebView2.Wpf.Direct3DHelper.CreateD3D9Device(IntPtr)
at Microsoft.Web.WebView2.Wpf.GraphicsItemD3DImage..ctor(...)
at Microsoft.Web.WebView2.Wpf.WebView2CompositionControl.TryInitializeD3DImage() -
Workaround: with the VirtIO GPU disabled, Windows uses the Microsoft Basic Render Driver, both
CreateDeviceExcalls return S_OK and Energieberater starts — but with software rendering and lower resolution. -
Disabling the device at runtime:
dwm.exeandexplorer.execrash with an access violation (0xc0000005) inneptune_umd_arm64.dllat offset 0x7a2c; the VMPal window stops updating until the guest is rebooted. After the reboot the basic driver works.
Expected Behavior
- Direct3D 9 (9Ex) device creation works on the VirtIO GPU, or the driver exposes Direct3D 12 so Windows' built-in D3D9On12 layer can provide Direct3D 9 automatically.
- WPF apps using
WebView2CompositionControlstart normally. - Disabling the display device at runtime does not crash dwm/explorer.
Environment
- App version: VMPal 0.38 (Build 38)
- Mac: MacBook Pro, Apple silicon (please add chip and RAM)
- macOS version: macOS 27
- VM's OS: Windows 11 ARM64, build 10.0.26100.4349
- Display adapter: Red Hat VirtIO GPU 3D controller, driver 100.6.101.58000; dxdiag: DDI 11.1, feature levels 11_1–9_1, WDDM 2.2; user-mode driver
neptune_umd.dll(viogpu3d.inf_arm64_9de0e1d956655e28), Wow entryneptune_umd_x86.dll
Log
The VM itself did not crash, so there is no VM log. Attached: d3d9_repro.py (minimal reproduction). Happy to provide dxdiag output, the dwm/explorer crash dumps and event logs, or to test a preview build.
Activity
albeik-corp commentedon Oct 7, 2026
I just saw this after I posted something similar: #26
sonswift commentedon Oct 8, 2026
Thank for your feedback. Let’s me check it.
retr0five commentedon Oct 13, 2026
hey, any updates so far?
huyphams commentedon Nov 15, 2026
Hi @retr0five, Direct3D 12 and Direct3D 9 (through D3D9On12) work with GPU acceleration since release build 98. Closing this, please let us know if you’re still seeing the issue.