-
Notifications
You must be signed in to change notification settings - Fork 822
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 failed to reopen after run wsl --shutdown #11684
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload 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 View similar issuesPlease 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! Closed similar issues:
|
/question |
Diagnostic information
|
Oops, I solved this issue by restart LxssManager in services.msc. If anyone got the same issue, welcome to contact me by [email protected]. :) |
Windows Version
Microsoft Windows [Version10.0.19045.4412]
WSL Version
0.0.0.0
Are you using WSL 1 or WSL 2?
Kernel Version
No response
Distro Version
Ubuntu 20.04
Other Software
No
Repro Steps
Everything was fine at first, when my computer was booted up and running wsl's Ubuntu.
Until I shutdown Ubuntu, I run wsl --shutdown through the powershell, and powershell didn't return any value at this time.
I shut down powershell and tried to reopen Ubuntu, but I got stuck without any error messages, and I used powershell to try to view wsl-l--v without returning any values.
Expected Behavior
Reopen my wsl's Ubuntu 20.04.6
Actual Behavior
Nothing shown in terminal
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: