Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WSL2: The network was not found #5294

Closed
bartek048 opened this issue May 29, 2020 · 3 comments
Closed

WSL2: The network was not found #5294

bartek048 opened this issue May 29, 2020 · 3 comments

Comments

@bartek048
Copy link

bartek048 commented May 29, 2020

After multiple experiments with WSL2 VPN network issues (Cisco AnyConnect), I lost "vEthernet (WSL)" adapter in Hyper-V. It happened after reboot. I'm not sure why, because didn't change Hyper-V settings.

When I try to open wsl2, I see:

WslRegisterDistribution failed with error: 0xffffffff
Error: 0xffffffff (null)

Mentioned missing "vEthernet (WSL)" is the problem, so I added it manually as "internal" network. Now I see:

WslRegisterDistribution failed with error: 0x803b0001
Error: 0x803b0001 The network was not found.

I tried reenabling WSL/Hyper-V or freshing distro installation, but didn't help.

Uncle Google is out of ideas, so I'm creating this issue.

@naidu72
Copy link

naidu72 commented May 30, 2020

Try to reinstall windows subsystem for Linux. It worked for me

@bartek048
Copy link
Author

Try to reinstall windows subsystem for Linux. It worked for me

By (un)checking it in Features list? Already tried that.

@bartek048
Copy link
Author

I had to temporarily disable dnscrypt-proxy service to unblock port 53

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants