Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/ERROR_FILE_NOT_FOUND upon executing WSL

[Atari2]

Windows Version

Microsoft Windows [Version 10.0.19045.2788]

WSL Version

1.1.3.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.90.1

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

Execute wsl from a terminal.
I don't really have repro steps because it happened suddently. Yesterday everything was working fine.

Expected Behavior

WSL execution starts as normal

Actual Behavior

WSL hangs for a while and after a couple of minutes exits with

❯ wsl
The system cannot find the file specified.
Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/ERROR_FILE_NOT_FOUND

Diagnostic Logs

No response

[benhillis]

/logs

I suspect the virtual switch is in a bad state, but logs would confirm.

[microsoft-github-policy-service]

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging

Thank you!

[Atari2]

WslLogs-2023-03-24_22-45-05.zip
Logs here, sorry.

[Atari2]

@benhillis sorry to ping but any update on this?

[sm-msft]

Thank you for your patience. We need additional information and logs to further investigate this issue.

If you had rebooted your machine since you last observed this issue, do you still observe any problems launching WSL? We would like the following logs collected for further investigation, whether or not the issue still exists.

Please collect your system networking related state using this script and share it with us: https://raw.githubusercontent.com/microsoft/SDN/master/Kubernetes/windows/debug/collectlogs.ps1

Running that script downloads other scripts on to your machine. Please look for "c:\k\debug\starthnstrace.cmd" to locate the next script, or you can download it from here: https://github.com/microsoft/SDN/blob/master/Kubernetes/windows/debug/starthnstrace.cmd

Please follow these steps to collect networking traces for WSL launch:

1. starthnstrace.cmd
2. launch wsl
3. netsh trace stop

The traces are written to c:\server.etl. Please collect this file and share it with us as well.

[Atari2]

Yes, the issue continues even after reboots (I rebooted the machine various times when I tried to diagnose the issue myself before making the issue here), if anything, it worsened.
Now, after various normal-use reboots during these past days, trying to run the wsl command just hangs forever without erroring out ever, it just stays there without any message on the command line or anything.
I collected the extra logs (now stopping the wsl command with Ctrl+C after various minutes of letting it run since it doesn't error out explicitely anymore, but it still hangs) but I would like to refrain from posting it publicly in this github thread and would like to know if there was any way to share them privately.

[zhenchengyang]

Hello Atari2
Have you solved this problem? I have encountered the same problem as you. Can you tell me how to solve it if it has already been solved? thank you

[Atari2]

Hello Atari2 Have you solved this problem? I have encountered the same problem as you. Can you tell me how to solve it if it has already been solved? thank you

No, unfortunately the last message you see on this thread is the last time I heard from ms, I haven't received new instructions or help since.

[RrazzmatazZ]

After update my window system I got this problem too...

[olegueret]

I solved this by reinstalling VMware Workstation Player:

I got this problem after updating my Windows 10 from 21H2 to 22H2. Just before updating I uninstalled VMware Workstation Player 16 because I was not using it, and also manually removed its leftover network adapters "VMware Network Adapter VMnet1" and "VMware Network Adapter VMnet1".

I tried many things (rebooting computer, disable Hyper-V, reenable it, enable features Microsoft-Windows-Subsystem-Linux and VirtualMachinePlatform with disam.exe, etc) but nothing worked.

Then I realized that the error wsl gave had someting to do with networking (.../CreateVm/ConfigureNetworking/), so I downloaded and installed VMware Workstation Player 17 (which recreated its VMNet network adapters) and now WSL works again!

[siaynoq]

Confirmed 👍
I had the exact same issue - removed VMWare Player and WSL2 stopped responding. Re-installing the Player "resolved" the issue immediately, however it would be great to understand the underlying problem as I'm not using that tool anymore and would like to remove eventually.

[XiaoSenLuo]

I got this error also when uninstall VMWare 17, and I found all Hyper-V Network Adapter removed also, I try remove the function "Windows sub Linux system" and enable it again, but cann't add Hyper-v network adapter automatically.

[ruoyiqiao]

I solved this by reinstalling VMware Workstation Player:

I got this problem after updating my Windows 10 from 21H2 to 22H2. Just before updating I uninstalled VMware Workstation Player 16 because I was not using it, and also manually removed its leftover network adapters "VMware Network Adapter VMnet1" and "VMware Network Adapter VMnet1".

I tried many things (rebooting computer, disable Hyper-V, reenable it, enable features Microsoft-Windows-Subsystem-Linux and VirtualMachinePlatform with disam.exe, etc) but nothing worked.

Then I realized that the error wsl gave had someting to do with networking (.../CreateVm/ConfigureNetworking/), so I downloaded and installed VMware Workstation Player 17 (which recreated its VMNet network adapters) and now WSL works again!

The same issue, thanks for sharing this fix.

[AidanWelch]

I get the same issue

[blackliner]

Confirmed, VMware Player 17. What a garbage SW, had to install it again to make it work.

[douglas541]

I had the same issue. Just dont download VMware.

[Raven-Singularity]

Removing comment, as I added my own issue, as it's not exactly the same as this one.

#12055

[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