-
Notifications
You must be signed in to change notification settings - Fork 829
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 2 uninstalled itself #6059
Comments
what's the output of |
We don't know what's the problem until collect-wsl-logs |
I accidentally sent bug report in wrong category. The thing is that I have Windows in Czech language, that makes it more difficult to pick the correct category sometimes. Now I have to wait until data collection is available again :( |
Okay, sent. |
I saw the two logs you submitted, but I didn't find anything interesting in WSL. You can first check if lxssmanager service is running, if not, start it. If it hangs, I don't know what your problem is, so I just list some generic solutions:
|
Well, uninstalling VMware isn't and option for me since I use virtual machines with various OS, including Windows 98 and MS-DOS v6.22, and I actually have development version of VMware that supports Hyper-V. The first 3 may actually help, so I'll try these out tomorrow. |
So I tried number 1 and 3. From number 1 I cannot clearly say that that's the issue since CPU doesn't seem to be busy with wsl running. It just stops midway and hangs. Number 3 - tried to disable it and reenable it again and same issue. Well, here's one thing: If I run
Anything else just hangs the process. Didn't try out the number 4 for obvious reason that I need VMware for other virtual machines (I have Windows 98, MS-DOS and Windows 2000 virtual machine with VMware), and also didn't try out number 2 because I can't remember how can I do that :( |
Try restart lxssmanager first from task manager. number 2: hang is because of lxssmanager, but |
Well, now it hangs on stopping 🤔 |
I have found other issues on the service hanging on stopping as well (#1086 and #2933) and it does seem to be a bug in latest Insider Build snapshot. Still not fixed though... I don't know how can I fix it. As a workaround, I'll have to use Ubuntu virtual machine I installed in VMware until this is fixed. |
Any advice on whether suggestion 3 in this comment is safe with respect to existing data in WSL? Also #4144 may be interest to those following this thread. |
Had this too, issue seemingly resolved itself after several reboots over the course of a week or so. |
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
Environment
Steps to reproduce
Well, I installed some updates and while I didn't use the WSL much, I definitely was able to at least see that Linux was still installed like just few days ago (although, I was unable to launch the Linux terminal inside Windows Terminal app). Now I tried it again to see that Linux has disappeared and was replaced with Microsoft Azure Cloud Shell (that thing definitely wasn't there before). I still can run WSL directly, but it doesn't do anything. I think I have lost my Ubuntu installation somehow.
WSL logs:
None, or I cannot retrieve them somehow (or don't know about them).
Expected behavior
Start up Linux shell.
Actual behavior
Does nothing.
The text was updated successfully, but these errors were encountered: