WSL Networking Broken in 2.0.7

[fishfacemcgee]

Windows Version

Microsoft Windows [Version 10.0.22631.2506]

WSL Version

2.0.7.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

Linux version 5.15.133.1-microsoft-standard-WSL2 (root@1c602f52c2e4) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Thu Oct 5 21:02:42 UTC 2023

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

1. Launch a WSL instance
   • I usually do this by opening Terminal which defaults to my Ubuntu setup, but I can also repro this by just launching wsl.exe from Powershell

Expected Behavior

WSL Distro successfully starts

Actual Behavior

Following error is received

Failed to configure network (networkingMode Nat). To disable networking, set `wsl2.networkingMode=None` in C:\Users\bjgra\.wslconfig
Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0x80070424

[process exited with code 4294967295 (0xffffffff)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

Not sure how noteworthy it is but there is no .wslconfig file at the directory specified.

Diagnostic Logs

WslLogs-2023-11-07_17-30-23.zip - Launching Terminal with VMP Disabled
WslLogs-2023-11-07_17-32-12.zip - After enabling VMP again

[fishfacemcgee]

I found #10666 while looking through the 2.0.7 notes and it looks like I don't have Virtual Machine Platform enabled. So I'm confused as to why this wasn't an issue for me prior to 2.0.7 (is the version returned by wsl.exe --version wrong on the Microsoft Store provided version of WSL?) and, assuming MSS versioning isn't wrong, it appears the fix in 2.0.7 does not work.

[fishfacemcgee]

I can confirm that enabling VMP fixed the issue. I'll leave this open for now in case there's additional information you'd like to me provide, but I also don't have a problem with this being marked as closed/resolved. Now that I'm able to get back into my WSL env, I've update the issue with Kernel/Distro info.

[dominicfmazza]

Enabling VMP temporarily fixed the issue for me, but the issue is returning after running wsl --shutdown and wsl -t Ubuntu.

[ghost]

@dominicfmazza, after the issue has returned, when you say the issue has returned, do you mean the VMP feature is disabled again?

[benhillis]

/logs

[fishfacemcgee]

/logs

@benhillis Updated with logs with both VMP disabled (where I get the error in the original Issue) and enabled just in case both may help determine why the better error didn't show.

[cal4]

Downgrading to 2.0.4 fixes it for me

[lzhprigrammer]

Yes,I have the same problem!

Network error recv()

[bersbersbers]

Same problem after upgrading from WSL version 1.2.5.0 to 2.0.9 ("Failed to configure network (networkingMode Nat). To disable networking, set wsl2.networkingMode=None ..."). Fixed by installing VMP. Survives wsl --shutdown. Notable, and that's why I am posting here: On the first launch of wsl after installing VMP, I got this:

wsl: Failed to create virtual network with address range: '172.24.224.0/20', created new network with range: '172.18.16.0/20', The object already exists.
wsl: Failed to create network endpoint with address: '172.24.224.3', assigned new address: '172.18.31.109'

Could ping 8.8.8.8 as well as google.com with no problem.

Just in case this helps understanding what may be going on.

[ByteEnable]

Can confirm enabling "Virtual Machine Platform" in Optional Features fixed this same issue.

[dajhorn]

Disabling the Windows Firewall triggered this bug for me. Enabling the Windows Firewall and installing the Virtual Machine Machine Platform resolved it.

[HoracioDos]

Exact same problem here. Enabling Virtual Machine Platform fixed it.

[chanpreetdhanjal]

@fishfacemcgee please install the virtual machine platform.

[fishfacemcgee]

@chanpreetdhanjal As I stated in my follow-up comments, I did, and it fixed the issue.

However, the current issue now is that this release note for 2.0.7:

Add more actionable error message for when Virtual Machine Platform is not present (solves #10666)

does not appear to be valid. My WSL instance was working just fine on the prior version of WSL, and then I ran into the error in the original issue which, as we can all see, contains zero actionable information related to the Virtual Machine Platform. I do think it's potentially noteworthy that either:

• WSL2 didn't actually require VMP prior to 2.0.7
  or
• Something in a Windows update caused VMP to be disabled, coinciding with 2.0.7 rolling out on the Microsoft Store/winget

but the fact of the matter is 2.0.7 was supposed to contain fixed behavior around VMP-related errors that otherwise appeared to be networking related and this issue is proof otherwise. If MS wants to close this issue because the reported issue of "Networking error in 2.0.7" is resolved, I won't be offended, but I think my issue and the other comments here would warrant at least this being re-categorized around the incorrect error instead.

[ByteEnable]

To back up @fishfacemcgee , I did not see this error until WSL2 was updated to 2.0.7. I had not enabled VMP prior to this update. After the WSL2 update I launched my distro and recieved the same networking error as posted by @fishfacemcgee . I landed here after an Internet search for:

Failed to configure network (networkingMode Nat). To disable networking, set wsl2.networkingMode=None in C:\Users\ByteE\.wslconfig Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0x80070424

[chanpreetdhanjal]

Could you please follow the steps below and attach the diagnostic logs? https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues

[fishfacemcgee]

Could you please follow the steps below and attach the diagnostic logs? https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues

@chanpreetdhanjal Can you please read the rest of the comment thread where you can see that logs were already requested and provided?

[chanpreetdhanjal]

@fishfacemcgee The link above is new WSL networking log script. Please follow the link and share when you get some time.

[fishfacemcgee]

@fishfacemcgee The link above is new WSL networking log script. Please follow the link and share when you get some time.

@chanpreetdhanjal The link above is literally the commands I was asked to run to provide logs after I reported this issue.

[fishfacemcgee]

@fishfacemcgee The link above is new WSL networking log script. Please follow the link and share when you get some time.

@chanpreetdhanjal And again, as I stated, this is no longer a networking issue but an error reporting issue.

[chanpreetdhanjal]

@benhillis @craigloewen-msft

[bravedart]

TL;DR; VMP is enabled on my machine and I still have the issue.

I'm getting the same issue, but I already had (and still have) "Virtual Machine Platform" installed. WSL worked fine when I first installed it yesterday, but later in the day this same bug came up. I somehow got the error to go away by disabling VMP, restarting the computer, running wsl --install --no-distribution (which reenabled VMP), and restarting the computer again. However, the bug came up again today and I haven't been able to make it go away.

My WSL version is 2.0.9.0, and I'm happy to provide logs if you need.

Failed to configure network (networkingMode Nat). To disable networking, set wsl2.networkingMode=None in C:\Users\asdf.wslconfig
Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0x80072736

[process exited with code 4294967295 (0xffffffff)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

[bravedart]

I figured out my issue at least. If you have NordVPN client set to auto-connect when the computer starts, then you get the error when you try to start the terminal.

If you just disable your vpn before you try to start the terminal, then it starts ups without an error.

[L-ingqin12]

While I set the file in C:\Users\xx\.wslconfig as follows, the problem was fixed:

[experimental]
autoMemoryReclaim=gradual  # gradual | dropcache | disabled
networkingMode=NAT         # mirrored | NAT | None 
dnsTunneling=true
firewall=true
autoProxy=true

[emoneal]

Enabling VMP worked for me. I had a stressful time for a few days just trying to figure out the issue. No matter what I tried worked. You are a HUGE lifesaver!

[ReneNyffenegger]

Can I somehow verify that VMP is enabled? It should be, as per UEFI setup. But I still get the same error message.

Also, some commenters recommend to "install VMP". Is this a special software? Or another terminology for enabling VT-d in UEFI?

[emoneal]

Can I somehow verify that VMP is enabled? It should be, as per UEFI setup. But I still get the same error message.

Also, some commenters recommend to "install VMP". Is this a special software? Or another terminology for enabling VT-d in UEFI?

No, VMP stands for Virtual Machine Platform. It is part of Windows but can be enabled or disabled, which then installs or uninstalls it from your system on restart. You can verify if it is enabled by going to your start menu and searching "Windows features" and it should automatically find "Turn Windows features on or off." Scroll down until you find Virtual Machine Platform and make sure it is checked.

[mikeshutt]

The only thing that will resolve this issue for me is to

1. uninstall the Virtual Machine Platform
2. reboot
3. install the Virtual Machine Platform
4. reboot

The problem comes right back if I have to reboot for anything other reason. Quite annoying.

[alfablac]

I was getting errors when loading up WSL, same message error asking me to load with no network, error: 0xffffffff
Turns out the problem is when an application is running on port 53 it messes with WSL
Getting to resmon on win+r then network tab, listening port sections and killing the app running on port 53 solved for me.

[brianjlacy]

I am experiencing this issue as well:

> wsl
Failed to configure network (networkingMode Nat). To disable networking, set `wsl2.networkingMode=None` in C:\Users\...\.wslconfig
Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0xffffffff

• WSL 2 was working for me prior to the 2024-03 Cumulative Update for Windows 11 Version 23H2 (KB5035853) update.
• Virtual Machine Platform is already installed.
• Windows Hypervisor Platform was NOT checked/installed; I tried installing and rebooting but the problem persists.
• I tried adding a .wslconfig file as recommended by L-ingqin12 and others; problem persists.
• I complete uninstalled VMP, WHP, and WSL itself, rebooted, then re-installed them, updated WSL, and rebooted. The problem persists.

I have no idea what to do from here.

> wsl --version

WSL version: 2.1.5.0
Kernel version: 5.15.146.1-2
WSLg version: 1.0.60
MSRDC version: 1.2.5105
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22631.3296

> wsl --list --verbose
  NAME      STATE           VERSION
* Ubuntu    Stopped         2

[alohith]

I am experiencing this issue as well:

> wsl
Failed to configure network (networkingMode Nat). To disable networking, set `wsl2.networkingMode=None` in C:\Users\...\.wslconfig
Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0xffffffff

* WSL 2 was working for me prior to the 2024-03 Cumulative Update for Windows 11 Version 23H2 (KB5035853) update.

* Virtual Machine Platform is already installed.

* Windows Hypervisor Platform was NOT checked/installed; I tried installing and rebooting but the problem persists.

* I tried adding a .wslconfig file as recommended by [L-ingqin12](https://github.com/L-ingqin12) and others; problem persists.

* I complete uninstalled VMP, WHP, and WSL itself, rebooted, then re-installed them, updated WSL, and rebooted. The problem persists.

I have no idea what to do from here.

> wsl --version

WSL version: 2.1.5.0
Kernel version: 5.15.146.1-2
WSLg version: 1.0.60
MSRDC version: 1.2.5105
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22631.3296

> wsl --list --verbose
  NAME      STATE           VERSION
* Ubuntu    Stopped         2

I too am experiencing this.
Failed to configure network (networkingMode Nat). To disable networking, set 'wsl2.networkingMode=None' in C:\Users\TRaveler\.wslconfig Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/ERROR_UNHANDLED_EXCEPTION

Thought it was linked to me trying (and failing) to set up LAN network bridge connection, but I also just did the wsl.exe --update command in powershell, and it was working fine/as expected before... As suggested, in the error message I created a .wslconfig file in the designated directory with the following:

[experimental] autoMemoryReclaim=gradual # gradual | dropcache | disabled networkingMode=none # mirrored | NAT | None #dnsTunneling=false #firewall=false #autoProxy=true #[wsl2] # omit that if you already have it. #networkingMode=bridged #vmSwitch=wsl_switch

And wsl is working, but w/o networking, which kinda defeats part of the use case I have WSL for ('built-in' SSH, SFTP, rsync, rclone, etc ability and linux env), so a fix or solution soon would be greatly appreciated.

wsl --version --verbose WSL version: 2.1.5.0 Kernel version: 5.15.146.1-2 WSLg version: 1.0.60 MSRDC version: 1.2.5105 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.4170

[alohith]

I am experiencing this issue as well:

> wsl
Failed to configure network (networkingMode Nat). To disable networking, set `wsl2.networkingMode=None` in C:\Users\...\.wslconfig
Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0xffffffff

* WSL 2 was working for me prior to the 2024-03 Cumulative Update for Windows 11 Version 23H2 (KB5035853) update.

* Virtual Machine Platform is already installed.

* Windows Hypervisor Platform was NOT checked/installed; I tried installing and rebooting but the problem persists.

* I tried adding a .wslconfig file as recommended by [L-ingqin12](https://github.com/L-ingqin12) and others; problem persists.

* I complete uninstalled VMP, WHP, and WSL itself, rebooted, then re-installed them, updated WSL, and rebooted. The problem persists.

I have no idea what to do from here.

> wsl --version

WSL version: 2.1.5.0
Kernel version: 5.15.146.1-2
WSLg version: 1.0.60
MSRDC version: 1.2.5105
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22631.3296

> wsl --list --verbose
  NAME      STATE           VERSION
* Ubuntu    Stopped         2

I too am experiencing this. Failed to configure network (networkingMode Nat). To disable networking, set 'wsl2.networkingMode=None' in C:\Users\TRaveler\.wslconfig Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/ERROR_UNHANDLED_EXCEPTION

Thought it was linked to me trying (and failing) to set up LAN network bridge connection, but I also just did the wsl.exe --update command in powershell, and it was working fine/as expected before... As suggested, in the error message I created a .wslconfig file in the designated directory with the following:

[experimental] autoMemoryReclaim=gradual # gradual | dropcache | disabled networkingMode=none # mirrored | NAT | None #dnsTunneling=false #firewall=false #autoProxy=true #[wsl2] # omit that if you already have it. #networkingMode=bridged #vmSwitch=wsl_switch

And wsl is working, but w/o networking, which kinda defeats part of the use case I have WSL for ('built-in' SSH, SFTP, rsync, rclone, etc ability and linux env), so a fix or solution soon would be greatly appreciated.

wsl --version --verbose WSL version: 2.1.5.0 Kernel version: 5.15.146.1-2 WSLg version: 1.0.60 MSRDC version: 1.2.5105 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.4170

Log for when I don't have the wsl2.networkingMode set to None:

WslLogs-2024-03-25_02-03-12.zip

[alohith]

@brianjlacy did you get your situation working? if so, what steps did you take?

[ericsoderquist]

I figured out my issue at least. If you have NordVPN client set to auto-connect when the computer starts, then you get the error when you try to start the terminal.

If you just disable your vpn before you try to start the terminal, then it starts ups without an error.

you are amazing and i love you thank you so much this has been very hard to troubleshoot but your answer did it!

[azidancorp]

I had this problem persistent even with Virtual Machine Platform was enabled. I noticed that my Mullvad VPN wouldnt connect and it said due to VMWare conflict
Turns out it was something to do with the fact I installed and then uninstalled VMWare - which setup its bridging that conflicted with wsl

This fixed it:

Open Registry Editor:
Press Win + R, type regedit, and press Enter.

Navigate to the Registry Key:
Go to HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{3d09c1ca-2bcc-40b7-b9bb-3f3ec143a87b} or
Go to HKEY_CLASSES_ROOT\CLSID{3d09c1ca-2bcc-40b7-b9bb-3f3ec143a87b}.

Delete the Registry Key:
Right-click on {3d09c1ca-2bcc-40b7-b9bb-3f3ec143a87b} and select Delete.
Confirm the deletion.

Reboot Your PC:
Restart your computer to apply the changes.

Go to Network Connections:
Press Win + R, type ncpa.cpl, and press Enter.

Select Your Ethernet Adapter:
Find your Ethernet adapter, right-click on it, and select Properties.

Remove VMware Bridge Protocol:
In the Properties window, look for VMware Bridge Protocol.

Uncheck it or select it and click Uninstall.

[ttury]

In my case, this problem occurred when DHCP was disabled. Open services.msc and check that "DHCP client" is running and set to automatic.

[MikeS1042]

I had this same error although the error code was different at the end. Mine read

Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0xffffffff

Turned out my DNS proxy I had installed for development was messing things up (I am using Acyrlic DNS Proxy). When I stopped this it all worked.

[euanmacinnes]

I had the same issue here after installing the 2024-03 Cumulative Update for Windows 11 Version 23H2 (KB5035853) update.

@MikeS1042 's answer prompted me to look at the Technitium DNS server I have set up for "at home DNS". Stopping Technitium, starting WSL, then restarting technitium, seemed to resolve things. the .wslconfig file made no difference.

[3265]

I have the same issue..

ailed to configure network (networkingMode Nat). To disable networking, set wsl2.networkingMode=None in C:\Users\xxxx.wslconfig Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0x80041002 Press any key to continue...

[KubeDevMax]

I have this issue and none of the workarounds (I tried them all) worked.

[3265]

@KubeDevMax I eventually rolled back to WSL1 in order to avoid the Hyper-V problem, and then it worked

#12019

[fkpwolf]

I have this issue suddently. But since I have no change on system and VMP is always on, just restarted system and then OK.

[saeed-neorelm]

same issue here, version:

WSL version: 2.3.13.0
Kernel version: 6.6.36.3-1
WSLg version: 1.0.63
MSRDC version: 1.2.5326
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26120.1843

and

$wsl -l
Windows Subsystem for Linux Distributions:
Ubuntu (Default)

and turning no safe mode fixes this but of course thats not really a solution, it just hides it under the rug

edit: restarting the machine did fix the issue.

[jochenvw]

I have this issue suddently. But since I have no change on system and VMP is always on, just restarted system and then OK.

+1

[akr1999]

Port 53 is issue.

• make c:\users\<USER>\.wslconfig (remove everything from it if exists; do keep a backup of old .wslconfig) paste this only

[experimental]
networkingMode=mirrored

Open cmd as admin

• wsl --set-version 2

For a new docker installation install a distro also

• wsl --install Ubuntu-22.04

• wsl --shutdown

save and restart pc and start docker.

[ghidalgo3]

I think for me the problem was Docker Desktop. I disabled Docker Desktop on startup, restarted my machine, opened the Terminal into WSL Ubuntu 22.04 and networking worked again.

If I manually start Docker Desktop, networking still works so I believe it must be some kind of race condition between Docker Desktop and WSL.

WSL version: 2.3.24.0
Kernel version: 5.15.153.1-2
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26100.1742

And

Docker Desktop version = 4.34.2

[rfurtad]

I had the same issue, and nothing was working, like ping from wsl to host or ping from wsl to some server outside network. So based on @akr1999 comment, I did mv /etc/wsl.conf /etc/wsl.conf.bkp. Restart and wsl and guess what? it works! It may help someone, so here are my 2 cents. Thanks @akr1999 !

[destryptor]

I had this problem persistent even with Virtual Machine Platform was enabled. I noticed that my Mullvad VPN wouldnt connect and it said due to VMWare conflict Turns out it was something to do with the fact I installed and then uninstalled VMWare - which setup its bridging that conflicted with wsl

This fixed it:

Open Registry Editor: Press Win + R, type regedit, and press Enter.

Navigate to the Registry Key: Go to HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID{3d09c1ca-2bcc-40b7-b9bb-3f3ec143a87b} or Go to HKEY_CLASSES_ROOT\CLSID{3d09c1ca-2bcc-40b7-b9bb-3f3ec143a87b}.

Delete the Registry Key: Right-click on {3d09c1ca-2bcc-40b7-b9bb-3f3ec143a87b} and select Delete. Confirm the deletion.

Reboot Your PC: Restart your computer to apply the changes.

Go to Network Connections: Press Win + R, type ncpa.cpl, and press Enter.

Select Your Ethernet Adapter: Find your Ethernet adapter, right-click on it, and select Properties.

Remove VMware Bridge Protocol: In the Properties window, look for VMware Bridge Protocol.

Uncheck it or select it and click Uninstall.

Thanks a lot @azidancorp ! I have limited knowledge in networking, and had no idea uninstalling VMWare would cause the issue.

[borjamunozf]

Reported by one developer today, started to fail after Windows update KB5045935, coincidence or not.

WSL --version
2.3.14.0

Restarted & rebooted machine 3 times, no success.

Virtual Machine Platform is already enabled:

Uninstall the KB5045935 does not fix the problem:

wusa /uninstall /kb:5045935

Any idea? He cannot work.

[noobie158]

If you have a vpn. turn it of.

[DaRacci]

Using a networking mode of mirrored works until you want to expose ports, so nat mode is still a requirement for myself.

Hope this can be resolved as every time i reboot my machine it fails, I have to change to mirrored, start up wsl, shutdown wsl, change back to nat, get a new IP, add new firewall rules to forward to the correct address.

This is extremely annoying to go through daily.