-
Notifications
You must be signed in to change notification settings - Fork 816
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
WSL2 fails to start with Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0x80070424 #10755
Comments
Hi, I've resolved with these steps: I have only WSL, no vm no hyper-v machines and other virtualization tool.
let me know if these steps also work for you. Regards. |
+1 after a Windows update |
that helped |
It has fixed the problem for me too. |
Same here. I see it after the computer got rebooted by WU for installing KB5032883, KB5032007 and KB5032190 (not sure which would be the relevant one here). Problem is... I do use Hyper-V in this machine and I don't feel comfortable just removing it. Is there any other suggestion? |
Closed? Issue is still there.. |
I also use Hyper-V. Enabling it again and a third reboot restore the Hyper-V virtual machines. |
Disable Hyper-V |
I'm a VirtualBox user so I couldn't remove Hyper-V. But I found I didn't have Virtual Machine or Hypervisor installed now and I can't remember if they were. Once I check them off and rebooted, I could start Ubuntu without the network error message. However, it started in root. To fix this I issued the following in Admin Powershell: ubuntu config --default-user (your user id) |
I manually re-enabled Virtual Machine platform and that un-bricked things after the Windows Update caused the above problem. Now WSL starts up but it now starts as root instead of my usual user, how bizarre :D ( |
Resetting Ubuntu back to default via |
This worked for me. No apparent side-effects on existing VMs. No reboot needed. I too had the default user as root. I had to use |
To fix this I issued the following in Admin Powershell: ubuntu config --default-user (your user id) |
That helps me, Thanks. |
Thank you Marco! You saved my day! |
Worked for me too (step 3 specifically is in windows terminal: wsl.exe --install --no-distribution). How did they manage to push this update in production and just forget about WSL2 users? 🤡 Breaking our systems to push half-baked features (the multi-desktop transition effect still needs a good polish). |
This worked for me without the user issue. |
appreciated!It works for me and helps me a lot. |
This isn't working for me on Windows 11. It started after I rebooted for updates.
Happy to provide logs and such if someone can tell me what they need and how to get it. Thanks. |
I was also having issues after the latest update, I had no network at all. The solution above about Hyper-V completely solved the issue for me too, and I'm on Windows 11 Pro. I didn't even have to uninstall the other virtualization-related features. Read the comment I made in another thread, in case it gives you some idea to solve your issue. Edit:
Clicking the link about Hyper-V firewall default settings (https://learn.microsoft.com/en-us/windows/security/operating-system-security/network-security/windows-firewall/hyper-v-firewall) and running the command suggested there, those are the default values for me: C:\Get-NetFirewallHyperVVMSetting -PolicyStore ActiveStore -Name '{40E0AC32-46A5-438A-A0B2-2B479E8F2E90}'
Name : {40E0AC32-46A5-438A-A0B2-2B479E8F2E90}
Enabled : True
DefaultInboundAction : Block
DefaultOutboundAction : Block
LoopbackEnabled : True
AllowHostPolicyMerge : True I can't stop my WSL distro atm, but when I can, I will try changing the |
I just run "OptionalFeatures.exe" and then enabled "Virtual Machine Platform" and that's it. No additional steps before or after. |
it works for me(On Win11) |
does anyone else have two wsl services listed in services.msc after this issue? One that won't start and apparently doesn't exist. |
Oh, turns out mine was caused by #10764 actually, what is with windows update breaking so many things with wsl |
That helps me a lot, thank you~ |
Just throwing this out there in case anyone else hits the same headache. This was not working for me at first, for some reason I had to also run WSL with my VPN connection turned off after disabling this. After that, it now starts regardless of if the VPN is off or not, but does not work if Hyper-v is reenabled. |
您好,您的邮件我已收到,我会尽快给您回复,谢谢!
|
This also resolved the issue for me. Thanks! powershell: Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V
wsl --install ubuntu |
This work for me, thanks |
Thanks |
I had various errors that meant wsl had suddenly stopped working. In the end it was because I was using Acrylic DNS Proxy - it uses port 53 to run a dns proxy service. I spent days till I came across a stack overflow entry that showed me the problem. At that point I had uninstalled wsl and strugging to resintall it. Once I disabled Acrylic DNS Proxy, I managed to reinstall wsl. I use docker desktop and that wouldnt run would wsl, so once I fixed wsl everything works. |
您好,您的邮件我已收到,我会尽快给您回复,谢谢!
|
Same error but not resolved with above methods: |
WSL version: 2.0.14.0 |
Fixed on Windows 10 with shutting down PrivateInternetAccess VPN. It was auto-starting and auto-connecting. |
您好,您的邮件我已收到,我会尽快给您回复,谢谢!
|
Fixed on Windows 11 with |
您好,您的邮件我已收到,我会尽快给您回复,谢谢!
|
had the same issue. but with me the windows subsystem for linux randomly fully uninstalled???? but good i installed it again and now it works?? |
您好,您的邮件我已收到,我会尽快给您回复,谢谢!
|
1 similar comment
您好,您的邮件我已收到,我会尽快给您回复,谢谢!
|
Windows Version
Microsoft Windows [Versión 10.0.22621.2428]
WSL Version
2.0.9.0
Are you using WSL 1 or WSL 2?
Kernel Version
No response
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
Try to start WSL from command line.
Expected Behavior
WSL starts and we have access to Linux shell.
Actual Behavior
WSL throws an error about not being able to setup the network and drops to PowerShell again:
This happens since today's update to 2.0.9.0.
Diagnostic Logs
WslLogs-2023-11-15_10-06-57.zip
The text was updated successfully, but these errors were encountered: