-
Notifications
You must be signed in to change notification settings - Fork 859
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
starting wsl ubuntu gives me: no sessions [process exited with code 1 (0x00000001)] #11732
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:
|
The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running. Diagnostic information
|
Diagnostic information
|
Okay i figured out the issue, i ran |
Windows Version
10.0.22631.3737
WSL Version
2.2.4.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.153.1-2
Distro Version
Ubuntu
Other Software
No response
Repro Steps
starting wsl in anyway will gives me this error
Expected Behavior
I expect Ubuntu to open without any errors
Actual Behavior
this when running

wsl
orubuntu
commandthis when starting it from powershell

Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: