Intel Arc iGPU not work in WSL2

[YiHui-Liu]

Windows Version

Microsoft Windows [Version 10.0.22631.4890]

WSL Version

2.4.8.0

Are you using WSL 1 or WSL 2?

• [x] WSL 2
• [ ] WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Ubuntu 24.04

Other Software

mesa-utils: 9.0.0-2 mesa-vulkan-drivers: 24.2.8-1ubuntu1~24.04.1 WDDM driver: 3.1

Repro Steps

a laptop with intel ultra gpu (like ultra 7 155H), install and run glxgears in wsl2.

Expected Behavior

Actual Behavior

Diagnostic Logs

more info:

display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Microsoft Corporation (0xffffffff)
    Device: D3D12 (Intel(R) Arc(TM) Graphics) (0xffffffff)
    Version: 24.2.8
    Accelerated: yes
    Video memory: 18490MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.1
OpenGL vendor string: Microsoft Corporation
OpenGL renderer string: D3D12 (Intel(R) Arc(TM) Graphics)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.2.8-1ubuntu1~24.04.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.2.8-1ubuntu1~24.04.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.1 Mesa 24.2.8-1ubuntu1~24.04.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10

is there a method to diagnose or locate the issue?

some posts may be related:

• Configure WSL 2 for GPU Workflows: not work
• Intel integrated arc igpu in Core Ultra 7 not working properly with WLS2

[github-actions[bot]]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

[YiHui-Liu]

Logs are required for review from WSL team

Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

here is the diagnostic log: WslLogs-2025-02-25_17-15-21.zip

[github-actions[bot]]

Diagnostic information

.wslconfig found
Detected appx version: 2.4.8.0

[github-actions[bot]]

Diagnostic information

.wslconfig found
Detected appx version: 2.4.8.0

[elsaco]

@YiHui-Liu you didn't specify what Arc driver version are you using. On an Asus Zenbook with the driver 32.0.101.6043 from 10/4/2024 it works as expected:

First I thought that the display scaling might be the issue, but the test was done with 200% scaling. mesa version is matching yours. The driver is whatever Windows update installed.

[YiHui-Liu]

@YiHui-Liu you didn't specify what Arc driver version are you using. On an Asus Zenbook with the driver 32.0.101.6043 from 10/4/2024 it works as expected:

thans for your reply. i try to update the driver but it doesn't work.

First I thought that the display scaling might be the issue, but the test was done with 200% scaling. mesa version is matching yours. The driver is whatever Windows update installed.

my laptop monitor also has 200% scaling.

I will attempt to use wsl debug console to find out the reason.

[YiHui-Liu]

here is the output when i run glxgears in wsl debug console:

it seems to be the same as https://github.com/microsoft/WSL/issues/11293#issuecomment-2297791087

[YiHui-Liu]

I use a new installation of Ubuntu-24.04 and the same issue happened.

[sascharo]

I use a new installation of Ubuntu-24.04 and the same issue happened.

Did you solve the issue?

[TYTYXI]

I use a new installation of Ubuntu-24.04 and the same issue happened, too, and I use U9 285H

But if i use the newest mesa , it works.

sudo add-apt-repository ppa:kisak/kisak-mesa
sudo apt update
sudo apt upgrade

[YiHui-Liu]

sudo add-apt-repository ppa:kisak/kisak-mesa sudo apt update sudo apt upgrade

I'm so sorry to tell you that you are still using llvmpipe as OpenGL renderer string. It doesn't matter with the mesa version. You can set export GALLIUM_DRIVER=d3d12 and then use glxgears to check the results.

[kingsimba]

Same problem. Please fix it. Or how to switch to software opengl. I want to use RVIZ which requires the very basic OpenGL 2.0 maybe.

[YiHui-Liu]

any update of this issue? so many issues related to this problem, please fix it.

[ProvenGuilty]

I’m seeing the same behavior on a Core Ultra 9 285K machine (Arc iGPU, PCI ID 0x7d67) under WSL2.

Windows / WSL

• Windows 11 build: 10.0.22635.x (same branch as OP)
• WSL version: 2.4.8.0 (Ubuntu 24.04)
• Kernel: 6.6.87.2-microsoft-standard-WSL2
• Intel Graphics driver: 32.0.101.8250 (also tested 32.0.101.8247/5869)

Diagnostics

• sycl-ls only reports the D3D12→OpenCL path:

  [opencl:cpu][opencl:0] Intel(R) Core(TM) Ultra 9 285K
  [opencl:cpu][opencl:1] Intel(R) Core(TM) Ultra 9 285K
  [opencl:gpu][opencl:2] Intel(R) Graphics [0x7d67] OpenCL 3.0 NEO [23.43.027642]
  

• clinfo shows only CPU devices (no GPU entries).
• dmesg | grep dxg repeats:

  misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
  misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
  misc dxg: dxgk: dxgkio_reserve_gpu_va: Ioctl failed: -75
  

• Installing Jammy level-zero packages caused loader conflicts/segfault (sycl-ls crash); removing them and using Ubuntu 24.04 libze1/libze-dev restores the OpenCL path but still no Level Zero device.

Takeaway Level Zero never appears inside WSL, even with the latest Intel driver and oneAPI runtime. GPU workloads fall back to the Microsoft D3D12 translation layer, so anything requiring Level Zero or native Xe support isn’t currently possible. Happy to provide more logs if helpful.

[vapidarcher]

I have the same issue on a Core Ultra 5 125U machine.

• Windows 11 build: 26100.6901
• WSL version: 2.6.3.0 (Ubuntu 22.04)
• Kernel: 6.6.87.2-1
• Intel Graphics driver: 32.0.101.5542

If I use software rendering, it works as expected.

export LIBGL_ALWAYS_SOFTWARE=1
export MESA_LOADER_DRIVER_OVERRIDE=llvmpipe

Without llvmpipe, glxgears appears black screen, but can see frame rate.

[hungfu-lee]

I have the same issue, on Intel(R) Core(TM) Ultra 7 155U (1.70 GHz) with lastest driver installed, include openvino

Once gpuSupport=false was configured in .wslconfig , it works fine,

Heres output from command wsl --version

WSL 版本： 2.6.3.0
核心版本： 6.6.87.2-1
WSLg 版本： 1.0.71
MSRDC 版本： 1.2.6353
Direct3D 版本： 1.611.1-81528511
DXCore 版本： 10.0.26100.1-240331-1435.ge-release
Windows 版本： 10.0.26100.7462

while gpuSupport=true It will make laptop hang/crash immeidately on running GPU-related application, i.e. glxgears, google-chrome

Followings are syslog near the moment

Dec 22 16:50:57 Hungfu-Lee kernel: [   31.582280] misc dxg: dxgk: dxgkio_is_feature_enabled: Ioctl failed: -22
Dec 22 16:50:57 Hungfu-Lee kernel: [   31.585189] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
Dec 22 16:50:57 Hungfu-Lee kernel: [   31.586378] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
Dec 22 16:50:57 Hungfu-Lee kernel: [   31.587624] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
Dec 22 16:50:57 Hungfu-Lee kernel: [   31.589076] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
Dec 22 16:50:57 Hungfu-Lee kernel: [   31.591599] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
Dec 22 16:50:57 Hungfu-Lee kernel: [   31.593156] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
Dec 22 16:50:57 Hungfu-Lee kernel: [   31.594522] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
Dec 22 16:50:57 Hungfu-Lee kernel: [   31.597210] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
Dec 22 16:50:57 Hungfu-Lee kernel: [   31.598499] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
Dec 22 16:50:57 Hungfu-Lee systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Dec 22 16:50:58 Hungfu-Lee systemd[1]: systemd-timedated.service: Deactivated successfully.
Dec 22 16:51:01 Hungfu-Lee kernel: [   35.072682] misc dxg: dxgk: dxgvmb_send_create_allocation: send_create_allocation failed ffffffb5
Dec 22 16:51:01 Hungfu-Lee kernel: [   35.073899] misc dxg: dxgk: dxgkio_create_allocation: Ioctl failed: -75
Dec 22 16:51:01 Hungfu-Lee kernel: [   35.199689] misc dxg: dxgk: dxgkio_is_feature_enabled: Ioctl failed: -22
Dec 22 16:51:01 Hungfu-Lee kernel: [   35.201416] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
Dec 22 16:51:01 Hungfu-Lee kernel: [   35.202282] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
Dec 22 16:51:01 Hungfu-Lee kernel: [   35.203034] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
Dec 22 16:51:01 Hungfu-Lee kernel: [   35.203843] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
Dec 22 16:51:01 Hungfu-Lee kernel: [   35.205531] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
Dec 22 16:51:01 Hungfu-Lee kernel: [   35.206219] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
Dec 22 16:51:01 Hungfu-Lee kernel: [   35.207162] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
Dec 22 16:51:01 Hungfu-Lee kernel: [   35.207835] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
Dec 22 16:51:01 Hungfu-Lee kernel: [   35.208489] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
Dec 22 16:51:03 Hungfu-Lee kernel: [   37.522258] misc dxg: dxgk: dxgvmb_send_create_allocation: send_create_allocation failed ffffffb5
Dec 22 16:51:03 Hungfu-Lee kernel: [   37.523485] misc dxg: dxgk: dxgkio_create_allocation: Ioctl failed: -75
Dec 22 16:51:03 Hungfu-Lee kernel: [   37.525831] misc dxg: dxgk: dxgvmb_send_create_allocation: send_create_allocation failed ffffffb5
Dec 22 16:51:03 Hungfu-Lee kernel: [   37.526896] misc dxg: dxgk: dxgkio_create_allocation: Ioctl failed: -75
Dec 22 16:51:03 Hungfu-Lee kernel: [   37.541540] chrome: chrome: potentially unexpected fatal signal 11.
Dec 22 16:51:03 Hungfu-Lee kernel: [   37.541546] CPU: 12 PID: 2212 Comm: chrome Not tainted 6.6.87.2-microsoft-standard-WSL2 #1
Dec 22 16:51:03 Hungfu-Lee kernel: [   37.541548] RIP: 0033:0x7316895fd7a4
Dec 22 16:51:03 Hungfu-Lee kernel: [   37.541553] Code: 89 fb 48 83 ec 08 48 8b 7f 40 e8 37 98 03 00 48 85 c0 74 0a 48 83 c4 08 5b 5d c3 0f 1f 00 48 8b 7b 40 48 89 ee e8 ac 98 03 00 <48> 8b 45 00 48 89 ef 48 8b 40 08 48 83 c4 08 5b 5d ff e0 66 0f 1f
Dec 22 16:51:03 Hungfu-Lee kernel: [   37.541554] RSP: 002b:00007ffface6bfd0 EFLAGS: 00010206
Dec 22 16:51:03 Hungfu-Lee kernel: [   37.541555] RAX: 000032e402a7bd30 RBX: 000032e400a445d8 RCX: 0000000000000000
Dec 22 16:51:03 Hungfu-Lee kernel: [   37.541556] RDX: 000073168a28b6a0 RSI: 0000000000000000 RDI: 000032e4006d88f0
Dec 22 16:51:03 Hungfu-Lee kernel: [   37.541557] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000001
Dec 22 16:51:03 Hungfu-Lee kernel: [   37.541557] R10: 0000000000000001 R11: 000073169ea44b70 R12: 0000000000000000
Dec 22 16:51:03 Hungfu-Lee kernel: [   37.541558] R13: 0000000000000000 R14: 000032e400bd3170 R15: 000032e400a44000
Dec 22 16:51:03 Hungfu-Lee kernel: [   37.541558] FS:  000073169d90e480 GS:  0000000000000000
Dec 22 16:51:03 Hungfu-Lee kernel: [   37.542677] WSL (2225 - CaptureCrash): Capturing crash for pid: 1841, executable: !opt!google!chrome!chrome, signal: 11, port: 50005

[mantangL]

I have the same issue on a Core CPU Intel(R) Core(TM) Ultra 9 285H machine.

WSL version: 2.6.3.0(Ubuntu) kernel version: 6.6.87.2-1 WSLg version: 1.0.71 MSRDC version: 1.2.6353 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows: 10.0.26200.7462 Intel Graphics driver: GPU 0

Intel(R) Arc(TM) 140T GPU (16GB)

version:	32.0.101.8331
update date:	2025/11/26
DirectX version:	12 (FL 12.1)

If I use software rendering, it works as expected.

export LIBGL_ALWAYS_SOFTWARE=1 export MESA_LOADER_DRIVER_OVERRIDE=llvmpipe Without llvmpipe, glxgears appears black screen, but can see frame rate.