-
Notifications
You must be signed in to change notification settings - Fork 854
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wsl unable to start. #10679
Comments
@OneBlue - could you take a look please? Looks like it might be related to the change you made around init sockets. |
Thank you for reporting this @Tapir28. I'm not seeing the entire startup context in the logs. Can you try to:
And share those logs ? /logs |
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! |
@benhillis I hesitate to create another bug, my system exhibits a sort of hanging behavior… like no response from simply trying to start I collected logs. If this needs to be a new one, let me know.
WSL version: 2.0.6.0 |
This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-open it. Thank you! |
Windows Version
Microsoft Windows [Version 10.0.22635.2500]
WSL Version
2.0.6.0
Are you using WSL 1 or WSL 2?
Kernel Version
Ubuntu 22.04
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
From powershell, I shutdown and then try to restart wsl.
wsl --shutdown
wsl
Expected Behavior
wsl stops, and starts again.
Actual Behavior
(Ubuntu was updated to 22.04 from 20.04. The name distribution name is not accurate.)
PS C:\Users\Emma> wsl -l -v
NAME STATE VERSION
PS C:\Users\Emma> wsl --shutdown
PS C:\Users\Emma> wsl
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Error code: Wsl/Service/0x8007274c
PS C:\Users\Emma> wsl
The operation timed out because a response was not received from the virtual machine or container.
Error code: Wsl/Service/CreateInstance/HCS_E_CONNECTION_TIMEOUT
Diagnostic Logs
WslLogs-2023-10-25_11-08-30.zip
The text was updated successfully, but these errors were encountered: