-
Notifications
You must be signed in to change notification settings - Fork 814
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 not starting #4993
Comments
If you're still experiencing this in 19042 please open a new issue. |
2 tasks
This was referenced Nov 28, 2023
2 tasks
2 tasks
This was referenced Feb 3, 2024
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please use the following bug reporting template to help produce issues which are actionable and reproducible, including all command-line steps necessary to induce the failure condition. Please fill out all the fields! Issues with missing or incomplete issue templates will be closed.
If this is a console issue (a problem with layout, rendering, colors, etc.), please post to the console issue tracker.
Important: Do not open GitHub issues for Windows crashes (BSODs) or security issues. Please direct all Windows crashes and security issues to secure@microsoft.com. Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".\
See our contributing instructions for assistance.
Please fill out the below information:
Your Windows build number: Microsoft Windows [Versione 10.0.18363.720]
What you're doing and what's happening: from powershell (admin mode)
PS C:> wsl -l
Distribuzioni del Sottosistema Windows per Linux:
Ubuntu-18.04 (valore predefinito)
PS C:> wsl
(after about 1 minute)
Operazione di I/O terminata a causa dell'uscita dal thread oppure della richiesta di un'applicazione.
What's wrong / what should be happening instead: wsl should start
logs: logs.zip
The text was updated successfully, but these errors were encountered: