Closed mateusz-brzozowski closed 1 month ago
The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
.wslconfig found
Detected appx version: 2.3.21.0
Found no WSL traces in the logs
none of the similar issues helped
/dumps
logs with /dumps: https://we.tl/t-j5v2qO7n4S
Thank you @mateusz-brzozowski. The dumps shows that VM is stuck. I wonder if AutoMemoryReclaim is what's causing that. Can you try to change .wslconfig to:
[wsl2]
autoMemoryReclaim=disabled
And see if that solves the issue ?
If it doesn't please collect dumps again
Windows Version
Microsoft Windows [Version 10.0.22631.4169]
WSL Version
2.3.21.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.153.1-2
Distro Version
Ubuntu 22.04.3 LTS
Other Software
No response
Repro Steps
Steps from this stack to program in android studio on wsl: https://stackoverflow.com/questions/62145379/how-to-connect-android-studio-running-inside-wsl2-with-connected-devices-or-andr Windows update. After updating windows I can't start wls2, no commands respond. I turned on and off options in "Turn Windows features on or off", setting "autoMemoryReclaim=dropcache" didn't help.
Expected Behavior
When ubuntu starts it should start. Typing "wsl" in powershell should return something
Actual Behavior
Ubuntu won't start. Typing "wsl" in powershell doesn't return anything. Freezes.
Diagnostic Logs
WslLogs-2024-09-18_23-31-59.zip WslLogs-2024-09-18_23-31-59.zip