Repository navigation
wslc list returns ERROR_TIMEOUT on WSL 3.0.3.0 #42012
Description
Windows Version
Microsoft Windows [Version 10.0.26200.9711]
WSL Version
3.0.3.0
Are you using WSL 1, WSL 2, or WSLC?
- WSL 2
- WSL 1
- WSLC
Kernel Version
No response
Distro Version
No response
Other Software
No response
Repro Steps
Run from PowerShell any of the commands below:
wslc list
wslc images
wslc image ls
wslc container ls
But wslc version and wslc info work.
Expected Behavior
I worked with wslc during the public preview phase and it worked but since I did the Windows update and WSL was updated too, I got this problem.
I tried to resolve it by setting the networkingMode in the settings.yaml as it was mentioned in wslc run returns ERROR_TIMEOUT on WSL 3.0.1.0 · Issue #41740 · microsoft/WSL but that didn't help.
Actual Behavior
After some time the following error occurs as CLI output.
This operation returned because the timeout period expired.
Error code: ERROR_TIMEOUT
If this error was unexpected, please consider searching for existing issues or filing a new issue at https://github.com/microsoft/WSL/issues.
Diagnostic Logs
Running collect-wsl-logs.ps1 provided me with the following stderr.log contents:
[10:15:03.035] <3>WSLGd: LogException:71: Exception: No such file or directory @../FontMonitor.cpp:280 (Start)
[10:15:03.035] <5>WSLGd: Stop:330: FontMonitor: monitoring stopped.
dbus[18]: Unable to set up transient service directory: XDG_RUNTIME_DIR "/mnt/wslg/runtime-dir" can be written by others (mode 040777)
dbus[15]: Unknown username "pulse" in message bus configuration file
(WW) Option "-listen" for file descriptors is deprecated
Please use "-listenfd" instead.
Xwayland glamor: GBM Wayland interfaces not available
Failed to initialize glamor, falling back to sw
The XKEYBOARD keymap compiler (xkbcomp) reports:
Warning: Unsupported maximum keycode 708, clipping.
X11 cannot support keycodes above 255.
Errors from xkbcomp are not fatal to the X server
Running .\collect-wsl-logs.ps1 -LogProfile networking resulted in:
Saving logs...
<3>WSL (52121 - Relay) ERROR: CreateProcessParseCommon:1061: getpwnam(killall) failed 0
User not found.
Error code: Wsl/WSL_E_USER_NOT_FOUND
Apart from that the stderr.log contents is the same.
Activity
github-actions commentedon Oct 21, 2026
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:
The script will output the path of the log file once done.
If this is a networking issue, please use
.\collect-wsl-logs.ps1 -LogProfile networkinginstead, following the instructions in Collect WSL logs for networking issuesOnce completed please upload the output files to this GitHub issue.
See Collect WSL logs (recommended method).
If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.
ej-zhang commentedon Oct 24, 2026
I‘m using wslc in an intranet environment without internet access, a machine Windows 10 LTSC runs normally, but another machine Windows Server 2022 reports a timeout error. What's the minimum version of Windows Server requirement to running WSL Containers please?
Windows 10 LTSC 22H2 Version 19045.6456
Running wslc is normal
Window Server 2022 21H2 Version 20348.5761
Running wslc reports a timeout error