Windows 11: WSL2 cannot able to start, Error: 0x80041002

[erbanku]

Version

WSL 版本： 0.64.0.0 内核版本： 5.10.102.1 WSLg 版本： 1.0.40 MSRDC 版本： 1.2.3213 Direct3D 版本： 1.601.0 DXCore 版本： 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows版本： 10.0.22621.232

WSL Version

• WSL 2
• WSL 1

Kernel Version

Cannot able to run commands to get Kernel Version

Distro Version

All Distro

Other Software

No response

Repro Steps

Trying to start the WSL application or any distros

Expected Behavior

Should be able to start normally

Actual Behavior

Cannot able to start. I reviewed all solutions mentioned in #5329 and #5340 all methods does not work.

My hyper-v option missing strangely in option features.
I think this issue maybe related with the software VMware Workstation Pro 16 I installed before, but the problem remains even I uninstall the software completely.

Returns error below:

Error: 0x80041002
Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x80041002
Press any key to continue...


[process exited with code 4294967295 (0xffffffff)]

Diagnostic Logs

No response

[arnon001]

/dupe #5340
scroll there down a little bit

[erbanku]

/dupe #5340 scroll there down a little bit

I know someone is going to say duplicated, but I think it is not, I am NOT able to solve the issue according to #5329 and #5340 or doing Google search for hours.

[OneBlue]

/logs

[ghost]

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging

Thank you!

[erbanku]

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1[](https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1)" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging

Thank you!

Here is log:

WslLogs-2022-07-27_03-34-35.zip

[erbanku]

I did the steps in this answer on the Superuser, and reinstalled the WSL completely (sadly, I lost my 5 distro configs and files in it), but I re-encounter the problem again, now I only able to use WSL1 and unable to install WSL2 distros or transfer the WSL1 distros to WSL2, and same error code 0x80041002

The answer

1. Uninstall all distributions
2. Deactivate Hypervisor and WSL service in Windows Features + Restart
3. Activate Hypervisor and WSL service in Windows Features + Restart
4. If you install the Distribution via Shell, start it as admin
5. Then install it

I found that every time I tried to open or install WSL2 distro, the device manager would appear a Hyper-V Virtual Switch Extension Adapter, but it cannot start successfully, seems has some issues, but I am not able to fix this after doing a lot of Google search, I think this maybe the breakpoint. Please help, thanks.

I have already enabled the WSL and virtualization in Windows optional features.

[OneBlue]

Thank you @erbanku. I have added another log provider to our log collection script.

Can you please share another trace of the issue ?
/logs

[ghost]

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging

Thank you!

[erbanku]

Thank you @erbanku. I have added another log provider to our log collection script.

Can you please share another trace of the issue ? /logs

After days of waiting and unable to solve the problem even after trying almost all methods, I came up with CLEAN INSTALL THE WHOLE SYSTEM and managed to solve it. Thanks!

[erbanku]

Problem solved after clean install the whole system. 😕