Repository navigation
WSL 1.0.3 hangs forever #9659
Description
Version
Windows version: 10.0.22621.1265
WSL Version
- WSL 2
- WSL 1
Kernel Version
5.15.74.2
Distro Version
Any
Other Software
Docker Desktop
Repro Steps
After installing wsl 1.0.3 cannot start it. Tried completely re-installing, unregistered and registering the distros (tho they get stuck at the installation). I can see that a new process called vmmemWSL is tarted with around 700mb memory and 0% CPU that lingers around.
Rolled back to wsl 1.0 works ok.
Expected Behavior
wsl to work
Actual Behavior
wsl hangs either on start or on installation with the vmmemWSL process being dropped after a long time (can be speedup by stopping the wslservice process)
Diagnostic Logs
No response
Reacted by hetsch and traycerb
Activity
microsoft-github-policy-service commentedon Feb 23, 2023
Hello! Could you please provide more logs to help us better diagnose your issue?
To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The scipt will output the path of the log file once done.
Once completed please upload the output files to this Github issue.
Click here for more info on logging
Thank you!
Gitii commentedon Feb 24, 2023
I have the same issue (WSL-Version: 1.1.3.0). Here is the log:
WslLogs-2023-02-24_14-04-01.zip
I hope it's useful because wsl already hangs when the user session starts.
Gitii commentedon Feb 27, 2023
@gaelxcowi I've checked and it's ~830MB for me and 0-0.1% CPU. On my laptop, I noticed that after a clean start, everything is fine. But standby causes this behaviour. After realizing that, I have created a new log file with reproduction:
WslLogs-2023-02-27_11-22-21.zip
I've started logging, put system to sleep (power safe), waited until it's on standby, turned the system on again, waited a few minutes and then stopped logging.
It might be unrelated, but Microsoft Terminal is killed after standby&resume (it's no longer running after resume of the system) and docker desktop is super dead. It cannot start anymore but that's expected as it depends on the wsl2 vm to function.
Gitii commentedon Mar 4, 2023
After a few days of playing around, I can confirm that version 1.0 is working without issues for me (no freezes, no "slow" start). Just as expected. With version 1.0, Microsoft Terminal survives standby, too.
Gitii commentedon Mar 11, 2023
@pmartincic No worries and thanks for the honest update! I really appreciate that!
Gitii commentedon Mar 28, 2023
@gaelxcowi I couldn't reproduce this issue with 1.1.5.0 and the latest windows update anymore.
So maybe it has been fixed?
DanKaplanSES commentedon Jan 24, 2024
@gaelxcowi
Did you mean to check the WSL2 checkbox? I only see you mentioning v1.My mistake. @gaelxcowi was referring to wsl2 v1 whenever they said v1.xz-viewray commentedon Mar 20, 2024
I'm happy to report that after updating to Windows 11 a few weeks ago, the issue has yet to occur since the update.
The following is the
wsl --versionoutput after the update.Crowy-o commentedon Oct 11, 2024
Had quite the same issue, whenever I was starting wsl, it's just stuck forever. No error msg, no CPU usage - only 115mb of RAM was in use.
For some reason, manually enabling of "Host address loopback" in WSL settings app resolved the issue.
xz-viewray try this one, maybe you face the same issue.
microsoft-github-policy-service commentedon Oct 16, 2025
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.
Thank you!