Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x80041002

[jpmchia]

Version

Microsoft Windows [Version 10.0.22623.746]

WSL Version

• WSL 2
• WSL 1

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

• Issue encountered when starting any WSL terminal session.
• Docker Desktop does not fully start up and displays "Docker Desktop starting ..."
• Hyper-V

Expected Behavior

• WSL terminal session initiation.
• Docker Desktop start up sequence completes.

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":

• Windows Subsystem for Linux
• Windows Hypervisor Platform
• Virtual Machine Platform
• Hyper-V Hypervisor
• Hyper-V Services

Have tested after completely uninstalling / removing applications via "Apps > Installed Apps":

• Docker Desktop
• VMWare Workstation

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:

• #5092
• #8657
• #8841

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: 0x80041002
Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x80041002

[process exited with code 4294967295 (0xffffffff)]

**Error message reported when starting any WSL terminal session, for any installed distribution: **

Docker Desktop:

Hyper-V Virtual Switch Extension Adapter:

Device ROOT\VMS_VSMP\0000 had a problem starting.

Driver Name: wvms_mp_windows.inf
Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}
Service: VMSMP
Lower Filters: 
Upper Filters: 
Problem: 0x0
Problem Status: 0xC00000E5

VMWare Virtual Ethernet Adapter:

Diagnostic Logs

WslLogs-2022-10-14_12-05-35.zip

[ToddRosenkrantz]

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.

1. Windows "ipconfig" shows the router address as the Windows IPv4 address and WSL "ip a" shows the "real" IP address.
2. The WiFi icon in the system tray shows connected but hovering the mouse over it says "No Internet Access" (Which I most certainly do have.

This does allow Docker Desktop to start. I have not tested any network functionality in docker yet.

[hijimasa]

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.

[owen118z]

+1

[JiaHuann]

+1 after I enable IPV6 and disabled on Windows ，then Docker and WSL report Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x8007023e

[keiveulbugs]

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.

1. %userprofile% in windows searchbar
2. there it should be, otherwise make it and just paste the following and save

[wsl2]
swap=0

https://learn.microsoft.com/en-us/windows/wsl/wsl-config

[cheekyshibe]

+1 在我启动 IPV6 和在 Windows 上禁止使用后，然后 Docker 和 WSL 报告 Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x8007023e

Have you solved it? I meet the same situation.

[neoOpus]

Got the same issue and it was because of Acrylic DNS, disabling it or configuring it properly would solve this.

[abraham-yusuf]

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

[Vidzhel]

It suddenly stopped working in the middle of the day. I checked updates, which happened to be, updated, and started working immediately

[soroshsabz]

related to #10089

[emapco]

1. Disable all VM-like options (wsl, docker, vm platform, hyperv ...) in Turn Windows features on or off
2. Reboot
3. Enable WSL and Virtual Machine Platform
4. Reboot
5. Open powershell
6. Enter wsl --install Ubuntu --web-download

This installed the Ethernet adapter vEthernet (WSL) virtual ethernet adapter that I was missing.

[ledinhduy281]

I've done what you said, but still have these issues. Do you have any ideas to solve it?

[KrauseStefan]

Rebooting helped for me.

[neoOpus]

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.

[zty012]

1. Disable all VM-like options (wsl, docker, vm platform, hyperv ...) in Turn Windows features on or off
2. Reboot
3. Enable WSL and Virtual Machine Platform
4. Reboot
5. Open powershell
6. 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

[cjens00]

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

1. Add or Remove Programs
2. Removed VMWare Workstation 17.x
3. 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.

[as-thanhdao]

the latest update of Windows is suck, tried to rollback then it works now.

[cjens00]

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

1. Add or Remove Programs
2. Removed VMWare Workstation 17.x
3. 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.

[jpliraa]

1. Disable all VM-like options (wsl, docker, vm platform, hyperv ...) in Turn Windows features on or off
2. Reboot
3. Enable WSL and Virtual Machine Platform
4. Reboot
5. Open powershell
6. 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!

[SmashingQuasar]

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

[kokokh]

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.

[Arya2255]

I uninstalled vmware and restarted the system, the problem was solved.

[zmasek]

Over here, too, but don't have any other virtualizations. Everything's vanilla.

[Raven-Singularity]

I had a similar incident after installing then uninstalling VMware, which left my Hyper-V Extensible Virtual Switch entirely broken. I was unable to load WSL2 for about 10 days due to the missing virtual network adapter.

What fixed it for me was removing this registry key which VMware left behind:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{3d09c1ca-2bcc-40b7-b9bb-3f3ec143a87b}

After removing this registry key manually, then clicking Network Reset on the Networking Control Panel page, my system came back up with fully working networking, including my WSL2 launching again!

Note: Network Reset made me wait 5 minutes before it rebooted the system.

Hope it helps other people who are stuck!

Other error codes and error messages I experienced:

Windows is still setting up class configuration for this device. (Code 56)
0x80071779
0x80041002

[iimasum]

I think it might be useful

basically i am beginner .. so sorry in advance ..thanks for being kind

I have tried almost every way on the internet(stack...windows..) but i am unable to solve ..the first screenshot one iwas able to solve but it appeared after i tried anather one... i tried many ways but none working...i downloaded docker yesterday its updated almost and tried again how many times installing and uninstalling...

its for one of my exam projects i need to use docker

thanks for your time

[Raven-Singularity]

@iimasum:
What is node-vulcanjs and vulcanadapter.cc?

It is not starting because it can't create a virtual network adapter for NAT network access. Have you tried removing the VMware registry key like my previous post, and doing a Network Reset, to fix your virtual networking?

If you go to Hyper-V Management and go to the Virtual Switches section, does it list any virtual switches?

Does your container require network access?

If you don't need networking, you can disable it by adding this:

[wsl2]
wsl2.networkingMode=None

To this file in your user folder:

C:\Users\YourUser\.wslconfig