Application Error. code 4294967295

[develooper1994]

Version

Microsoft Windows [Version 10.0.22000.438]

WSL Version

• WSL 2
• WSL 1

Kernel Version

5.10.81.1

Distro Version

Ubuntu 20.04

Other Software

No response

Repro Steps

I updated windows 11 to latest version and wsl stops working. I am not using docker or anything else. I reinstalled ubuntu and wsl. It doesn't work.
open wsl without problem.

Expected Behavior

open wsl without problem.

Actual Behavior

{Application Error}
The application was unable to start correctly (0x%lx). Click OK to close the application.

Press any key to continue...

[process exited with code 4294967295]

Diagnostic Logs

{Application Error}
The application was unable to start correctly (0x%lx). Click OK to close the application.

Press any key to continue...

[process exited with code 4294967295]

[sylvain-fano]

same here !

[eqn-group]

The error only happens when you click on either of the Ubuntu short-cuts icons. You can start WSL2 from the Windows Terminal.
Download Windows terminal and type wsl to run.
If you want to run from cmd/ps , open it and click on its icon on top-left of titlebar and go to properties, uncheck legacy mode.

also try uninstalling docker and running netsh winsock reset. possible /dupe #4904 #4929 #4364

[develooper1994]

I am using the windows terminal, powershell and wsl2 by default. I don't use docker.
Also netsh winsock reset didn't resolve the issue.

The error only happens when you click on either of the Ubuntu short-cuts icons. You can start WSL2 from the Windows Terminal. Download Windows terminal and type wsl to run. If you want to run from cmd/ps , open it and click on its icon on top-left of titlebar and go to properties, uncheck legacy mode.

also try uninstalling docker and running netsh winsock reset. possible /dupe #4904 #4929 #4364

[eqn-group]

check the issues #4904 #4929 #4364

[microsoft-github-policy-service]

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

Thank you!