Skip to content

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

New issue
New issue
Closed
Closed
Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x80041002#9016

Description

@jpmchia
Jean-Paul C (jpmchia)
opened on Oct 14, 2022

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:

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: **
image

Docker Desktop:
image
image

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

image
image
image
image
image

VMWare Virtual Ethernet Adapter:
image
image

Diagnostic Logs

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

Activity

  1. ToddRosenkrantz commented on Oct 15, 2022

    @ToddRosenkrantz
    Stoddard Rosenkrantz (ToddRosenkrantz)
    on Oct 15, 2022

    I resolved this by adding a virtual switch in Hyper-V Manager named "Bridge". I set mine up for external network connection.
    image

    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.

  2. hijimasa commented on Dec 27, 2022

    @hijimasa
    Masaaki Hijikata (hijimasa)
    on Dec 27, 2022

    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.

  3. owen118z commented on Jan 29, 2023

    @owen118z
    owen (owen118z)
    on Jan 29, 2023

    +1

  4. JiaHuann commented on Jan 30, 2023

    @JiaHuann
    JiaHuann (JiaHuann)
    on Jan 30, 2023

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

  5. keiveulbugs commented on Mar 9, 2023

    @keiveulbugs
    keiveulbugs
    on Mar 9, 2023

    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

  6. 0xMashiro commented on Mar 19, 2023

    @0xMashiro
    Shiina Mashiro (0xMashiro)
    on Mar 19, 2023

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

    Have you solved it? I meet the same situation.

  7. neoOpus commented on Mar 24, 2023

    @neoOpus
    Anoir Ben Tanfous (neoOpus)
    on Mar 24, 2023

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

  8. abraham-yusuf commented on Mar 24, 2023

    @abraham-yusuf
    Abraham Yusuf (abraham-yusuf)
    on Mar 24, 2023

    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

  9. o-talaver commented on Mar 30, 2023

    @o-talaver
    Talaver Oleh (o-talaver)
    on Mar 30, 2023

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

  10. soroshsabz commented on May 10, 2023

    @soroshsabz
    soroshsabz
    on May 10, 2023

    related to #10089

  11. emapco commented on May 17, 2023

    @emapco
    Manny Cortes (emapco)
    on May 17, 2023
    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.

  12. ledinhduy281 commented on May 23, 2023

    @ledinhduy281
    KTANE (ledinhduy281)
    on May 23, 2023

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

  13. KrauseStefan commented on May 30, 2023

    @KrauseStefan
    Stefan Krause-Kjær (KrauseStefan)
    on May 30, 2023

    Rebooting helped for me.

  14. neoOpus commented on May 30, 2023

    @neoOpus
    Anoir Ben Tanfous (neoOpus)
    on May 30, 2023

    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.

  15. zty012 commented on Jun 10, 2023

    @zty012
    zty012
    on Jun 10, 2023
    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

  16. cjens00 commented on Jul 16, 2023

    @cjens00
    Cameron Jensen (cjens00)
    on Jul 16, 2023

    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.
    image

    VM Platform enabled. Oddly, WSL is disabled in the features list.
    image

  17. as-thanhdao commented on Jul 16, 2023

    @as-thanhdao
    Thanh Dao (as-thanhdao)
    on Jul 16, 2023

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

  18. cjens00 commented on Jul 16, 2023

    @cjens00
    Cameron Jensen (cjens00)
    on Jul 16, 2023

    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. image

    VM Platform enabled. Oddly, WSL is disabled in the features list. image

    Nevermind. Running into the same issue again even with VMWare Workstation uninstalled.
    This latest dev update is genuinely not good as Thanh Dao (@as-thanhdao) mentioned.

  19. jpliraa commented on Jul 20, 2023

    @jpliraa
    Jota (jpliraa)
    on Jul 20, 2023
    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!

  20. SmashingQuasar commented on Aug 2, 2023

    @SmashingQuasar
    Nicolas Lebacq (SmashingQuasar)
    on Aug 2, 2023

    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

  21. kokokh commented on Aug 13, 2023

    @kokokh
    kokokh
    on Aug 13, 2023

    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.

  22. Arya2255 commented on Sep 16, 2023

    @Arya2255
    arya aryaii (Arya2255)
    on Sep 16, 2023

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

  23. zmasek commented on Oct 6, 2023

    @zmasek
    Zlatko Mašek (zmasek)
    on Oct 6, 2023

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

  24. Raven-Singularity commented on Sep 19, 2024

    @Raven-Singularity
    Raven-Singularity
    on Sep 19, 2024

    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

  25. iimasum commented on Sep 22, 2024

    @iimasum
    Masum Ahmed Tapadar (iimasum)
    on Sep 22, 2024

    I think it might be useful
    Screenshot 2024-09-21 201232

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

    Screenshot 2024-09-22 231158
    Screenshot 2024-09-22 231217

    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

  26. Raven-Singularity commented on Sep 22, 2024

    @Raven-Singularity
    Raven-Singularity
    on Sep 22, 2024

    Masum Ahmed Tapadar (@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

  27. microsoft-github-policy-service
    closed this as completedon Sep 25, 2025

  28. microsoft-github-policy-service commented on Sep 25, 2025

    @microsoft-github-policy-service
    microsoft-github-policy-serviceBot
    on Sep 25, 2025 – with Microsoft GitHub Policy Service
    Contributor

    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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions