Skip to content
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

Ubuntu WSL hanged on launch #5747

Closed
darkRaspberry opened this issue Aug 12, 2020 · 8 comments
Closed

Ubuntu WSL hanged on launch #5747

darkRaspberry opened this issue Aug 12, 2020 · 8 comments

Comments

@darkRaspberry
Copy link

darkRaspberry commented Aug 12, 2020

Environment

Windows build number: Microsoft Windows [Version 10.0.20190.1000]
Your Distribution version: Release:        20.04
Whether the issue is on WSL 2 and/or WSL 1: WSL 2

Steps to reproduce

Simply launch the WSL by any method.

Expected behavior

To Open WSL by any method.
Atleast
$ wsl -l -v should runs.

Actual behavior

struck on the screens

@darkRaspberry
Copy link
Author

Probable duplicate Still not resolved.
#849

@darkRaspberry
Copy link
Author

No luck with changing Virtual memory. Still get the error after restart.

@darkRaspberry
Copy link
Author

darkRaspberry commented Aug 18, 2020

Upgraded to build 20190. Still seriously facing issue.
How to collect logs so that you guys can debug.

@darkRaspberry
Copy link
Author

darkRaspberry commented Aug 18, 2020

After restart it work. If i use wsl --shutdown in cmd. To solve that Ram issue. After sometime as I open wsl by any method. It doesn't open..

even wsl - l -v doesn't show anything.

@therealkenc
Copy link
Collaborator

Probable duplicate Still not resolved. #849

That was WSL1 and unrelated.

How to collect logs so that you guys can debug.

Instructions to collect log. Please link the feedback item in this issue.

@magneticflux-
Copy link

magneticflux- commented Aug 20, 2020

I'm having the same issue on build 20190. Any wsl command, even wsl -l hangs. I'll collect a log from a fresh boot demonstrating the issue and link the feedback item to this issue.

Edit:
Nevermind, I don't understand it at all anymore. I did some troubleshooting earlier where I re-enabled the Hyper-V components (as in this article) and it didn't do anything. Then I restarted to get a fresh baseline for a report and everything works again. I guess try the steps in that article and restart to see if that fixes it?

@benhillis
Copy link
Member

/dupe #5744

@ghost
Copy link

ghost commented Aug 21, 2020

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!

@ghost ghost closed this as completed Aug 21, 2020
@ghost ghost added the duplicate label Aug 21, 2020
@github-actions github-actions bot mentioned this issue Oct 21, 2024
2 tasks
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants