WSL does not start: Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0x800706d9

[ElD4n1]

Windows Version

Microsoft Windows [Version 10.0.19045.4046]

WSL Version

2.1.4.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.146.1-2

Distro Version

No response

Other Software

Docker Desktop (Windows) Version 4.26.1

Repro Steps

Run "wsl" in command line

Expected Behavior

WSL starts

Actual Behavior

There are no more endpoints available from the endpoint mapper.
Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0x800706d9

Diagnostic Logs

WslNetworkingLogs-2024-03-07_10-24-12.zip

WSL suddenly stopped working, it was already working before.

I already tried the following steps, mainly based on #10755 :

• Disable Hyper-V
• Remove Hyper-V network adapter
• Reinstall WSL2
• Check that ICS service start state is set to Manual (Trigger Start) Docs

The networking logs were collected after performing those steps.

[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/HNS/0x80070424 (#10778), similarity score: 0.94

Closed similar issues:

• WSL2 fails to start with Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0x80070424 (#10755), similarity score: 0.95
• WSL fails to start with error code Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x800700b7 (#10435), similarity score: 0.94
• Error on first start: Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x800706bf (#8841), similarity score: 0.90
• Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x80041002 (#9845), similarity score: 0.89

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

[hdc-dragonfly]

Go try
Wsl --install --enable-wsl1

[ElD4n1]

Go try Wsl --install --enable-wsl1

Thanks, but unfortunately this didn't change anything and I think I need WSL 2 for Docker.

[hdc-dragonfly]

I also use docker, I did uninstall Docker and reinstalled with the latest installer. This won't harm your Containers, they presist.

[OneBlue]

@keith-horton: This seems to be caused by an HNS issue although I'm seeing any HNS logs in the trace. How can the user work around this ?

[keith-horton]

It doesn't look like HNS is running:
hnsdiag.exe : There are no more endpoints available from the endpoint mapper.

@ElD4n1 , can you see the state of the HNS service? did someone disable it? sc queryex hns

it might have crashed repeatedly which now it won't auto-start.

If the service shows stopped, then you can start the WSL Network powershell script again, then run "sc start HNS". If it doesn't start running, please share the traces. @OneBlue , do we publish a way to capture if someone has crashed? If so, we would want to look at the svchost crashing process for HNS.

[OneBlue]

@OneBlue , do we publish a way to capture if someone has crashed? If so, we would want to look at the svchost crashing process for HNS.

Yes, these are the instructions on how to collect a usermode crash

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!

[InspiringCode]

The problem in my case was, that the "Host Network Service" (hns) was not running. After setting it to "Auto Delayed" is worked for me.

[dmunoz2019]

Thank you! I disabled all the services in Windows, and everything stopped working. To get it working again, I had to use the following commands:
sc.exe config wslservice start= demand

And start this service: Host Network Service (hns).