-
Notifications
You must be signed in to change notification settings - Fork 832
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
WslRegisterDistribution failed with error: 0x80370102 #9656
Comments
I've made a little bit of progress, I think? I found there was an install of Kali Linux in my WSL and I have no idea how long it was there. I uninstalled it and installed Ubuntu, but now running the wsl command results in this message: `Windows Subsystem for Linux has no installed distributions. Use 'wsl.exe --list --online' to list available distributions Distributions can also be installed by visiting the Microsoft Store: I've tried reinstalling Ubuntu, from both the Microsoft store and by using wsl --install but I'm still getting the same result. Opening the Ubuntu app in my Start Menu I get this:
and Docker, which is what I'm ultimately trying to set up here, throws these errors: Docker.Core.HttpBadResponseException: at Docker.Core.GoBackend.GoBackendClient.d__19.MoveNext() in C:\workspaces\4.16.x\src\github.com\docker\pinata\win\src\Docker.Core\GoBackend\GoBackendClient.cs:line 226 I've been talking with a few people about this and apparently this means it can't find an install of WSL. So with all in this in mind, it seems WSL is still not working for me. Another way to run Docker would be in a virtual machine, but not even those are working for me anymore. I have tried both Hyper-V and VMWare. If I were unable to find a solution here or anywhere else, my only option would be to reinstall Windows which I'm avoiding at all costs. It may be a good idea for you to check your installed distros if you haven't already, with wsl --list or --list --verbose, uninstall any you find and see how WSL behaves afterwards. Edit: Also, I can't seem to tell if I'm on WSL 1 or 2. I tried setting the default version to 1 just to try, then disabling and re-enabling WSL in my Windows features, but I decided to go back to 2, did the same thing, and this is my version info: WSL version: 1.0.3.0 |
I also have the same issue. When this problem occurred, both my Windows Sandbox and WSL2 stopped working properly. Then I found an article about fixing the Sandbox and resolved the issue by following these steps: Uninstall Windows Sandbox. Restart your computer. Open Command Prompt (Run as administrator) and execute the following command: bcdedit /set hypervisorlaunchtype Auto Uninstall Hyper-V. Restart your computer. Install Hyper-V. Restart your computer and verify that Hyper-V is working. Install Windows Sandbox. Restart your computer and verify that Sandbox is functioning properly. The link: https://answers.microsoft.com/zh-hans/windows/forum/all/windows-10-%E6%89%93%E5%BC%80windows/286f8a35-6a74-433c-b00f-bcd03812d180 |
Additional information: The issue with my WSL2 occurred after I installed an Android emulator called Mumu. |
Thanks for your answer. I was really stuck on that error. Following first 6 steps helped me to install sucessfully Ubuntu and run docker server on my Winddoows 11 machine |
I'm experiencing absolutely the same problem. Tried all solutions listed, nothing really helps. |
@shokurov Please try to open window's terminal as administrator, enter bcdedit command and check if the value of hypervisorlaunchtype is Auto. then check if the Windows Subsystem for Linux software from Microsoft Store is the latest version. You can check as above, if all these are fine, I don't know anymore. |
You saved my day, i've spent 4 hours figuring this out, i did everything related to wsl, docker and BIOS stufff to enable virtualization, this was the answer. |
I struggled with this issue for some days and wasn’t able to fix it with the regular methods. I knew for sure I had virtualisation enabled in the bios, since wsl2 did work before. I turned off/on hyper-v and all other features. Nothing worked, although wsl 1 gave no issues. What I did notice lots off errors in eventlog and I ended up endlessly trying to fix several issues without solving the wsl2 issue. As a last resort I tried fixing windows with help of the MediaCreationTool. After installing windows 10, but luckily leaving my current setup fully intact, wsl 2 worked again perfectly (out of the box). |
Not work it! 🥹 |
I resolved the 0x80370102 error through the following steps:
|
Thank you. It worked for me. |
Version
Microsoft Windows [Version 10.0.22621.1265]
WSL Version
Kernel Version
2
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
In Windows Features:
In task manager, virutalization is fully enabled in my BIOS, confirmed via systeminfo, too:
All of the online documentation takes me in loops or tells me to roll back to WSL 1.
The BIOS says I have virtualization enabled, the task manager says it....
I've disabled and re-enabled all of these checkboxes and rebooted, and I still cannot get WSL2 working on my Windows 11 box
Expected Behavior
I would expect ubuntu to load
Actual Behavior
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: