WSL2 fails to start with Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0x80070424

[raulpedroche]

Windows Version

Microsoft Windows [Versión 10.0.22621.2428]

WSL Version

2.0.9.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

No response

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

Try to start WSL from command line.

Expected Behavior

WSL starts and we have access to Linux shell.

Actual Behavior

WSL throws an error about not being able to setup the network and drops to PowerShell again:

PS C:\Users\rpedroche> wsl
No se pudo configurar la red (networkingMode Nat). Para deshabilitar las redes, establezca "wsl2.networkingMode=None" en C:\Users\rpedroche\.wslconfig
Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0x80070424
PS C:\Users\rpedroche>

This happens since today's update to 2.0.9.0.

Diagnostic Logs

WslLogs-2023-11-15_10-06-57.zip

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x80041002 (#9016), similarity score: 0.89
• Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/ERROR_FILE_NOT_FOUND upon executing WSL (#9840), similarity score: 0.88
• WSL error: Wsl/Service/CreateInstance/CreateVm/ERROR_FILE_NOT_FOUND (#9547), similarity score: 0.87
• Wsl/Service/CreateVm/ConfigureNetworking/ERROR_NOT_FOUND (#9365), similarity score: 0.87
• wsl does not work. wsl list returns error: "Insufficient system resources exist to complete the requested service." Wsl/Service/CreateInstance/CreateVm/0x800705aa (#9666), similarity score: 0.86
• install the wsl2 with WslRegisterDistribution failed with error: 0x80070002Error: 0x80070002 ???????????;Update wsl1 to wsl2 with Error code: Wsl/Service/CreateVm/ConfigureNetworking/ERROR_FILE_NOT_FOUND (#10107), similarity score: 0.86

Closed similar issues:

• WSL fails to start with error code Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x800700b7 (#10435), similarity score: 0.92
• Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x80041002 (#9845), similarity score: 0.89
• Error on first start: Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x800706bf (#8841), similarity score: 0.88
• {Application Error} The exception %s (0x Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x8007023e (#9888), similarity score: 0.87

You can give me feedback by thumbs upping or thumbs downing this comment.

[marcomezzaro]

Hi, I've resolved with these steps:

I have only WSL, no vm no hyper-v machines and other virtualization tool.
Take care of possible side effects or issues with the removal of hyper-v services

1. removed Optional Features: Hyper-v platform and Hyper-V managment tool
2. reboot
3. start WSL: it will ask to install virtual platform service. confirm to install
4. reboot
5. wsl works

let me know if these steps also work for you.

Regards.

[fenglielie]

same issue, after windows update

[craigemery]

+1 after a Windows update

[karpikpl]

Hi, I've resolved with these steps:

I have only WSL, no vm no hyper-v machines and other virtualization tool. Take care of possible side effects or issues with the removal of hyper-v services

1. removed Optional Features: Hyper-v platform and Hyper-V managment tool
2. reboot
3. start WSL: it will ask to install virtual platform service. confirm to install
4. reboot
5. wsl works

let me know if these steps also work for you.

Regards.

that helped

[raulpedroche]

Hi, I've resolved with these steps:

I have only WSL, no vm no hyper-v machines and other virtualization tool. Take care of possible side effects or issues with the removal of hyper-v services

1. removed Optional Features: Hyper-v platform and Hyper-V managment tool
2. reboot
3. start WSL: it will ask to install virtual platform service. confirm to install
4. reboot
5. wsl works

let me know if these steps also work for you.

Regards.

It has fixed the problem for me too.

[TheJCAB]

Same here. I see it after the computer got rebooted by WU for installing KB5032883, KB5032007 and KB5032190 (not sure which would be the relevant one here).

Problem is... I do use Hyper-V in this machine and I don't feel comfortable just removing it. Is there any other suggestion?

[beam]

Closed? Issue is still there..

[raulpedroche]

Same here. I see it after the computer got rebooted by WU for installing KB5032883, KB5032007 and KB5032190 (not sure which would be the relevant one here).

Problem is... I do use Hyper-V in this machine and I don't feel comfortable just removing it. Is there any other suggestion?

I also use Hyper-V. Enabling it again and a third reboot restore the Hyper-V virtual machines.

[hatuhay]

Disable Hyper-V
Enable the Virtual Machine.
Reboot and problem solved.
This means that WSL2 is not only not compatible with Hyper-V, but also conflicts with it.

[CyberSpock]

I'm a VirtualBox user so I couldn't remove Hyper-V. But I found I didn't have Virtual Machine or Hypervisor installed now and I can't remember if they were. Once I check them off and rebooted, I could start Ubuntu without the network error message. However, it started in root. To fix this I issued the following in Admin Powershell: ubuntu config --default-user (your user id)

[Foritus]

I manually re-enabled Virtual Machine platform and that un-bricked things after the Windows Update caused the above problem. Now WSL starts up but it now starts as root instead of my usual user, how bizarre :D (su myuser is a workaround for now).

[Foritus]

Resetting Ubuntu back to default via wsl --setdefault Ubuntu in powershell solved the "default user is root" issue (despite Ubuntu being the only distro I have installed, god knows what screwed up the WSL config so badly in this update)

[rcarde]

I manually re-enabled Virtual Machine platform and that un-bricked things after the Windows Update caused the above problem. Now WSL starts up but it now starts as root instead of my usual user, how bizarre :D (su myuser is a workaround for now).

This worked for me. No apparent side-effects on existing VMs. No reboot needed.

I too had the default user as root. I had to use <dist>.exe config --default-user <user> to reset it.

[CyberSpock]

Now WSL starts up but it now starts as root instead of my usual user, how bizarre :D (su myuser is a workaround for now).

To fix this I issued the following in Admin Powershell: ubuntu config --default-user (your user id)

[juliwang0205]

Hi, I've resolved with these steps:

I have only WSL, no vm no hyper-v machines and other virtualization tool. Take care of possible side effects or issues with the removal of hyper-v services

1. removed Optional Features: Hyper-v platform and Hyper-V managment tool
2. reboot
3. start WSL: it will ask to install virtual platform service. confirm to install
4. reboot
5. wsl works

let me know if these steps also work for you.

Regards.

Hi, I've resolved with these steps:

I have only WSL, no vm no hyper-v machines and other virtualization tool. Take care of possible side effects or issues with the removal of hyper-v services

1. removed Optional Features: Hyper-v platform and Hyper-V managment tool
2. reboot
3. start WSL: it will ask to install virtual platform service. confirm to install
4. reboot
5. wsl works

let me know if these steps also work for you.

Regards.

That helps me, Thanks.

[michaltorun]

Hi, I've resolved with these steps:

I have only WSL, no vm no hyper-v machines and other virtualization tool. Take care of possible side effects or issues with the removal of hyper-v services

1. removed Optional Features: Hyper-v platform and Hyper-V managment tool
2. reboot
3. start WSL: it will ask to install virtual platform service. confirm to install
4. reboot
5. wsl works

let me know if these steps also work for you.

Regards.

Thank you Marco! You saved my day!

[MaxDesignFR]

Hi, I've resolved with these steps:
I have only WSL, no vm no hyper-v machines and other virtualization tool. Take care of possible side effects or issues with the removal of hyper-v services

1. removed Optional Features: Hyper-v platform and Hyper-V managment tool
2. reboot
3. start WSL: it will ask to install virtual platform service. confirm to install
4. reboot
5. wsl works

let me know if these steps also work for you.
Regards.

Worked for me too (step 3 specifically is in windows terminal: wsl.exe --install --no-distribution).

How did they manage to push this update in production and just forget about WSL2 users? 🤡 Breaking our systems to push half-baked features (the multi-desktop transition effect still needs a good polish).

[westerguard]

I manually re-enabled Virtual Machine platform and that un-bricked things after the Windows Update caused the above problem. Now WSL starts up but it now starts as root instead of my usual user, how bizarre :D (su myuser is a workaround for now).

This worked for me without the user issue.

[kakadeguaidao]

Hi, I've resolved with these steps:

I have only WSL, no vm no hyper-v machines and other virtualization tool. Take care of possible side effects or issues with the removal of hyper-v services

1. removed Optional Features: Hyper-v platform and Hyper-V managment tool
2. reboot
3. start WSL: it will ask to install virtual platform service. confirm to install
4. reboot
5. wsl works

let me know if these steps also work for you.

Regards.

appreciated！It works for me and helps me a lot.

[vdavidoff]

This isn't working for me on Windows 11. It started after I rebooted for updates.

1. Hyper-V was NOT enabled, and best I know, it never was. I enabled it and rebooted and the problem persisted.
2. I disabled Hyper-V and rebooted and the problem persisted.
3. I ran wsl --install --no-distribution with Hyper-V disabled and it simply said the operation completed successfully without doing anything, best I could tell. I rebooted and the problem persisted.
4. I disabled Virtual Machine Platform and rebooted. The OS indicated I needed to enable features for WSL to work, and it enabled VMP, and I rebooted. The problem persisted.
5. Fully uninstalled WSL (best I could figure how), reinstalled, problem persisted.
6. Played with Hyper-V and firewall settings as noted below, problem persisted.

Happy to provide logs and such if someone can tell me what they need and how to get it.

Thanks.

[jtabox]

I was also having issues after the latest update, I had no network at all. The solution above about Hyper-V completely solved the issue for me too, and I'm on Windows 11 Pro. I didn't even have to uninstall the other virtualization-related features.

Read the comment I made in another thread, in case it gives you some idea to solve your issue.

#10774 (comment)

Edit:
I now read the following in the WSL networking documentation (https://learn.microsoft.com/en-us/windows/wsl/networking):

On machines running Windows 11 22H2 and higher, with WSL 2.0.9 and higher, the Hyper-V firewall feature will be turned on by default.

Clicking the link about Hyper-V firewall default settings (https://learn.microsoft.com/en-us/windows/security/operating-system-security/network-security/windows-firewall/hyper-v-firewall) and running the command suggested there, those are the default values for me:

C:\Get-NetFirewallHyperVVMSetting -PolicyStore ActiveStore -Name '{40E0AC32-46A5-438A-A0B2-2B479E8F2E90}'

Name                  : {40E0AC32-46A5-438A-A0B2-2B479E8F2E90}
Enabled               : True
DefaultInboundAction  : Block
DefaultOutboundAction : Block
LoopbackEnabled       : True
AllowHostPolicyMerge  : True

I can't stop my WSL distro atm, but when I can, I will try changing the DefaultInboundAction and DefaultOutboundAction settings, in case it makes any difference when having Hyper-V installed too.

[aalku]

I just run "OptionalFeatures.exe" and then enabled "Virtual Machine Platform" and that's it. No additional steps before or after.

[juparog]

The following steps were used to solve the problem with wsl Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0x80070424 on my Windows 11 after applying a windows update.

• disable Hyper-V and reboot the system, you can do this by running the following command as administrator in powershell:

  Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V

• After the reboot try to start wsl normally, if it does not start it will most likely ask you to execute the command:

  wsl.exe --install --no-distribution

• Reboot the system again and with this you could start wsl normally.

Greetings,

[GaussianGuaicai]

I just run "OptionalFeatures.exe" and then enabled "Virtual Machine Platform" and that's it. No additional steps before or after.

This work for me!
some how "Virtual Machine Platform" was no enable in my case, but i am sure it was enable before one of the Windows Updates; it work by just enable it, don`t even need to reboot.

[roboalex123]

I just run "OptionalFeatures.exe" and then enabled "Virtual Machine Platform" and that's it. No additional steps before or after.

This worked, nice job!

[YY-Edwards]

The following steps were used to solve the problem with wsl Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0x80070424 on my Windows 11 after applying a windows update.

• disable Hyper-V and reboot the system, you can do this by running the following command as administrator in powershell:

  Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V

• After the reboot try to start wsl normally, if it does not start it will most likely ask you to execute the command:

  wsl.exe --install --no-distribution

• Reboot the system again and with this you could start wsl normally.

Greetings,

it works for me(On Win11)

[adambirds]

does anyone else have two wsl services listed in services.msc after this issue? One that won't start and apparently doesn't exist.

[adambirds]

Mine just keeps doing this:

[adambirds]

Oh, turns out mine was caused by #10764 actually, what is with windows update breaking so many things with wsl

[loverchun]

marcomezzaro

That helps me a lot, thank you~

[hsakada321]

Hi, I've resolved with these steps:

I have only WSL, no vm no hyper-v machines and other virtualization tool. Take care of possible side effects or issues with the removal of hyper-v services

1. removed Optional Features: Hyper-v platform and Hyper-V managment tool

2. reboot

3. start WSL: it will ask to install virtual platform service. confirm to install

4. reboot

5. wsl works

let me know if these steps also work for you.

Regards.

Just throwing this out there in case anyone else hits the same headache. This was not working for me at first, for some reason I had to also run WSL with my VPN connection turned off after disabling this. After that, it now starts regardless of if the VPN is off or not, but does not work if Hyper-v is reenabled.

[loverchun]

您好，您的邮件我已收到，我会尽快给您回复，谢谢！

[psyll0n]

The following steps were used to solve the problem with wsl Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0x80070424 on my Windows 11 after applying a windows update.

• disable Hyper-V and reboot the system, you can do this by running the following command as administrator in powershell:

  Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V

• After the reboot try to start wsl normally, if it does not start it will most likely ask you to execute the command:

  wsl.exe --install --no-distribution

• Reboot the system again and with this you could start wsl normally.

Greetings,

it works for me(On Win11)

This also resolved the issue for me. Thanks!

powershell:

Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V

• After the reboot try to start wsl normally, if it does not start it will most likely ask you to execute the command:

wsl --install ubuntu

[frank-garcia-dev]

Hi, I've resolved with these steps:

I have only WSL, no vm no hyper-v machines and other virtualization tool. Take care of possible side effects or issues with the removal of hyper-v services

1. removed Optional Features: Hyper-v platform and Hyper-V managment tool
2. reboot
3. start WSL: it will ask to install virtual platform service. confirm to install
4. reboot
5. wsl works

let me know if these steps also work for you.

Regards.

This work for me, thanks

[Chandler-Fei]

Hi, I've resolved with these steps:

I have only WSL, no vm no hyper-v machines and other virtualization tool. Take care of possible side effects or issues with the removal of hyper-v services

1. removed Optional Features: Hyper-v platform and Hyper-V managment tool
2. reboot
3. start WSL: it will ask to install virtual platform service. confirm to install
4. reboot
5. wsl works

let me know if these steps also work for you.

Regards.

Thanks

[princeo]

I had various errors that meant wsl had suddenly stopped working. In the end it was because I was using Acrylic DNS Proxy - it uses port 53 to run a dns proxy service. I spent days till I came across a stack overflow entry that showed me the problem. At that point I had uninstalled wsl and strugging to resintall it. Once I disabled Acrylic DNS Proxy, I managed to reinstall wsl.

I use docker desktop and that wouldnt run would wsl, so once I fixed wsl everything works.
#5214

[loverchun]

您好，您的邮件我已收到，我会尽快给您回复，谢谢！

[vivekbajaj]

Same error but not resolved with above methods:
Failed to configure network (networkingMode Nat). To disable networking, set wsl2.networkingMode=None in C:\Users\Vivek Bajaj.wslconfig
Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/ERROR_FILE_NOT_FOUND

[vivekbajaj]

[vivekbajaj]

WSL version: 2.0.14.0
Kernel version: 5.15.133.1-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.3155

[vivekbajaj]

[Stepych]

Fixed on Windows 10 with shutting down PrivateInternetAccess VPN. It was auto-starting and auto-connecting.

[loverchun]

您好，您的邮件我已收到，我会尽快给您回复，谢谢！

[lukas-santiago]

Fixed on Windows 11 with wsl2.networkingMode = mirrored in .wslconfig file. This have some disadvantages cause actually doesn't solve the issue with virtual NAT networking creation but it can connect externally.

[loverchun]

您好，您的邮件我已收到，我会尽快给您回复，谢谢！