Unable to launch wsl2

[ReinForce-II]

Windows Version

10.0.22631.3007

WSL Version

2.1.5.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.146.1-2

Distro Version

Ubuntu 20.04

Other Software

No response

Repro Steps

type wsl in powershell

Expected Behavior

wsl2 launched with no errors

Actual Behavior

The distribution failed to start. Error code: 5, failure step: 2
Error code: Wsl/Service/CreateInstance/E_FAIL

Diagnostic Logs

[github-actions]

View similar issues

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!

Open similar issues:

• Error code: Wsl/Service/CreateInstance/CreateVm/HCS/E_INVALIDARG (#10285), similarity score: 0.78

Closed similar issues:

• WSL2 2.0.1.0 Cannot start. (#10545), similarity score: 0.80
• Catastrophic failure : Error code: Wsl/Service/CreateInstance/E_UNEXPECTED (#10140), similarity score: 0.79
• Cannot start WSL, error Wsl/0x8007041d (#10910), similarity score: 0.78
• {Application Error} The exception %s (0x Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x8007023e (#9888), similarity score: 0.78

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

Diagnostic information

Detected appx version: 2.1.5.0
Detected user visible error: Wsl/Service/CreateInstance/E_FAIL

[FreedSoul]

@ReinForce-II i have the same issue, how did you resolve it?

[ReinForce-II]

@ReinForce-II i have the same issue, how did you resolve it?

In my case, the rootfs is corrupted, run e2fsck on it solved the problem.

[FreedSoul]

i cant even start wsl, can you give some insights or links, how to run e2fsck?

[ReinForce-II]

i cant even start wsl, can you give some insights or links, how to run e2fsck?

attach the vhdx containing rootfs of wsl2 to another linux system

[FreedSoul]

whoever that get this error message, the problem is that, you have your ext filesystem corrupted, because a dirty shutdown (in my case close vscode then quickly shutdown the pc) or power outage, you can repair the issue here or follow this other thread