Open jpmchia opened 1 year ago
I resolved this by adding a virtual switch in Hyper-V Manager named "Bridge". I set mine up for external network connection.
This works but has some problems.
This does allow Docker Desktop to start. I have not tested any network functionality in docker yet.
I faced a similar problem.
I am still using Windows 10 for company reasons. So it is not supported with Bridge mode. I modified the .wslconfig as below, and can boot Ubuntu. Before
[wsl2]
swap=0
networkingMode=bridged
vmSwitch=Bridge
After
[wsl2]
swap=0
I use WSL2 directly, not use Docker Desktop. Therefore, you may not use same way. But I hope to help this you.
+1
+1 after I enable IPV6 and disabled on Windows ,then Docker and WSL report Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x8007023e
I faced a similar problem.
I am still using Windows 10 for company reasons. So it is not supported with Bridge mode. I modified the .wslconfig as below, and can boot Ubuntu. Before
[wsl2] swap=0 networkingMode=bridged vmSwitch=Bridge
After
[wsl2] swap=0
I use WSL2 directly, not use Docker Desktop. Therefore, you may not use same way. But I hope to help this you.
thanks fixed it for me! after having trouble for months, this simple thing fixed it. For anyone not being able to find the conf file.
[wsl2]
swap=0
+1 在我启动 IPV6 和在 Windows 上禁止使用后,然后 Docker 和 WSL 报告 Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x8007023e
Have you solved it? I meet the same situation.
Got the same issue and it was because of Acrylic DNS, disabling it or configuring it properly would solve this.
Got the same issue and it was because of Acrylic DNS, disabling it or configuring it properly would solve this.
this same issue, valet stop and its works
It suddenly stopped working in the middle of the day. I checked updates, which happened to be, updated, and started working immediately
related to #10089
Turn Windows features on or off
wsl --install Ubuntu --web-download
This installed the Ethernet adapter vEthernet (WSL)
virtual ethernet adapter that I was missing.
I've done what you said, but still have these issues. Do you have any ideas to solve it?
Rebooting helped for me.
Those who still have an issue try but it is not because of network issues (firewall, hosts, etc) then try to reboot if not possible then try to shutdown wsl via this command
wsl --shutdown
if this is stuck too then try to use this
taskkill /F /im wslservice.exe
Then start wsl again using this command
wsl
If the issue persists please collect diagnostics and submit an issue (https://docs.docker.com/desktop/troubleshoot/overview/#diagnose-from-the-terminal).
Resetting all network settings and performing troubleshooting tasks such as uninstalling/reinstalling WSL and Docker can be time-consuming. However, it is crucial to identify the root cause of the problem by reflecting on the actions taken that may have caused it. Whether you choose to share your findings with the community or keep them to yourself, remember that the community support is invaluable.
- Disable all VM-like options (wsl, docker, vm platform, hyperv ...) in
Turn Windows features on or off
- Reboot
- Enable WSL and Virtual Machine Platform
- Reboot
- Open powershell
- Enter
wsl --install Ubuntu --web-download
This installed the
Ethernet adapter vEthernet (WSL)
virtual ethernet adapter that I was missing.
It works for me!!!! ty
Preface A few days ago I removed both WSL and the Virtual Machine platform, then,
Problem
Upon launching 'wsl' from the command line or Visual Studio Code w/ WSL remote enabled (it was working about 12 hours ago), I'm given an error message by VS Code as well as some wsl terminal output
Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x80041002
Fix
Note: Hyper-V was disabled and removed during the uninstallation of VMWare.
VM Platform enabled. Oddly, WSL is disabled in the features list.
the latest update of Windows is suck, tried to rollback then it works now.
Preface A few days ago I removed both WSL and the Virtual Machine platform, then,
- Ubuntu for WSL via Microsoft Store was re-installed (the one simply titled, "Ubuntu")
- Configured the newly installed Ubuntu 22.04 and updated apt repositories
- Performed Ubuntu 22.04 system upgrade to 22.10
- Performed Ubuntu 22.10 system upgrade to 23.04
- Used as normal for about 24-36 hours
Problem Upon launching 'wsl' from the command line or Visual Studio Code w/ WSL remote enabled (it was working about 12 hours ago), I'm given an error message by VS Code as well as some wsl terminal output
Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x80041002
Fix
- Add or Remove Programs
- Removed VMWare Workstation 17.x
- WSL is working normally again.
Note: Hyper-V was disabled and removed during the uninstallation of VMWare.
VM Platform enabled. Oddly, WSL is disabled in the features list.
Nevermind. Running into the same issue again even with VMWare Workstation uninstalled. This latest dev update is genuinely not good as @as-thanhdao mentioned.
- Disable all VM-like options (wsl, docker, vm platform, hyperv ...) in
Turn Windows features on or off
- Reboot
- Enable WSL and Virtual Machine Platform
- Reboot
- Open powershell
- Enter
wsl --install Ubuntu --web-download
This installed the
Ethernet adapter vEthernet (WSL)
virtual ethernet adapter that I was missing.It works for me!!!! ty
me too!
I had the same issue and apparently resolved it by turning off my VPN prior to launching WSL.
In PowerShell: wsl --shutdown
Then turn off your VPN.
Then in PowerShell wsl
.
Here is my WSL 2 configuration file (.wslconfig
):
[wsl2]
memory=8GB # Limits VM memory in WSL 2 to 4 GB
processors=8 # Makes the WSL 2 VM use two virtual processors
dnsProxy=false
I had the same issue and apparently resolved it by turning off my VPN prior to launching WSL.
In PowerShell:
wsl --shutdown
Then turn off your VPN.
Then in PowerShell
wsl
.Here is my WSL 2 configuration file (
.wslconfig
):[wsl2] memory=8GB # Limits VM memory in WSL 2 to 4 GB processors=8 # Makes the WSL 2 VM use two virtual processors dnsProxy=false
This helped me. Distro booted right up after killing my VPN and restarting wsl.
Thanks.
I uninstalled vmware and restarted the system, the problem was solved.
Over here, too, but don't have any other virtualizations. Everything's vanilla.
Version
Microsoft Windows [Version 10.0.22623.746]
WSL Version
Kernel Version
5.15.68.1
Distro Version
Ubuntu 20.04, Ubuntu 22.04 - all distributions
Other Software
Docker version 20.10.17, build 100c701 (also affected) VMWare Workstation 16 Pro [16.2.4 build-20089737] (installed alongside WSL)
Repro Steps
Expected Behavior
Actual Behavior
Have tried removing each of the following components, rebooting in between each time and reinstalling in various different sequences:
Windows components via "Apps > Optional Features > More Windows Features":
Have tested after completely uninstalling / removing applications via "Apps > Installed Apps":
And tested after reinstalling each independently. The reinstall of VMWare subsequently broke its virtual network adapter installation (manually removed the device after uninstalling the application).
Have tried each of the various suggested resolutions from:
Only course of action left to try is a complete reinstallation of Windows 11.... am just waiting for the backups to complete before attempting... fingers crossed!
Error message reported when starting any WSL terminal session, for any installed distribution:![image](https://user-images.githubusercontent.com/5074976/195827926-b31a238c-0e93-4343-8bb1-28c9c8311364.png)
Docker Desktop:
![image](https://user-images.githubusercontent.com/5074976/195830997-1dc2e48d-2398-48de-9752-31918731fa36.png)
Hyper-V Virtual Switch Extension Adapter:
VMWare Virtual Ethernet Adapter:
![image](https://user-images.githubusercontent.com/5074976/195831891-8938e409-a147-4caf-8a14-e6d54f351929.png)
Diagnostic Logs
WslLogs-2022-10-14_12-05-35.zip