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

wsl-networking-problem-0x80041002 #12306

Closed
1 of 2 tasks
Lazox12 opened this issue Nov 21, 2024 · 3 comments
Closed
1 of 2 tasks

wsl-networking-problem-0x80041002 #12306

Lazox12 opened this issue Nov 21, 2024 · 3 comments
Labels

Comments

@Lazox12
Copy link

Lazox12 commented Nov 21, 2024

Windows Version

Microsoft Windows [Version 10.0.22631.4460]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

0

Distro Version

0

Other Software

No response

Repro Steps

when I try to start ubuntu using terminal I get this error:

Expected Behavior

I expect the linux to launch normaly as it was before

Actual Behavior

I get this error log
Image

Diagnostic Logs

WslNetworkingLogs-2024-11-21_09-55-10.zip
WslLogs-2024-11-21_09-51-19.zip

Copy link

The logs show that the VM failed to start because the HNS network couldn't be created. Adding network tag
Known vmswitch issue found (error: 0x80041002). Adding network tag

Diagnostic information
Multiple log files found, using: https://github.com/user-attachments/files/17842805/WslNetworkingLogs-2024-11-21_09-55-10.zip
.wslconfig found
Detected appx version: 2.2.4.0
optional-components.txt not found
Detected user visible error: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0x80041002
Detected user visible error: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0x80041002
Found evidence of HcnCreateNetwork failure: HcnCreateNetwork (null). HResult: 0x80041002
Found evidence of vmswitch error: 0x80041002

@borjamunozf
Copy link

One developer in my company had this exactly issue this week. My hypothesis is that a faulty Windows update could trigger the issue (KB5045935)

The only way to get a somehow working status was updating to prerelease and rebooting laptop. Perhaps it fixed internally certain status.

wsl --update --pre-release

However, he gets a different message now, even if he can at least get back to work:
Image

We tried a bunch of things:

  • Reinstall Virtual Machine Platform feature (disable, reboot, enable, reboot)
  • Reinstall Windows Subsystem for Linux feature
  • Run:
wsl --install --no-distribution
wsl --uninstall

@Lazox12 Lazox12 closed this as completed Feb 19, 2025
@Lazox12
Copy link
Author

Lazox12 commented Feb 19, 2025

Ive solved it by reinstalling windows which id still do because it was starting to slow down and filling up with bloatware

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

No branches or pull requests

2 participants