无法启动分发。错误代码： 117，失败步骤： 2 错误代码: Wsl/Service/CreateInstance/E_FAIL

[liuhao16]

Windows Version

10.0.26100.4061

WSL Version

2.5.7.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.87.1-1

Distro Version

Ubuntu-24.04

Other Software

No response

Repro Steps

After a weekend, that's it. I promise no one touched my computer.

Expected Behavior

WSL can be started normally.

Actual Behavior

`C:\Users\liuhao>wsl
无法启动分发。错误代码： 117，失败步骤： 2
错误代码: Wsl/Service/CreateInstance/E_FAIL

C:\Users\liuhao>wsl --export Ubuntu-24.04 C:\Users\liuhao\Downloads\ubunutu.tar
正在导出，这可能需要几分钟时间。 (0 MB)

无法启动分发。错误代码： 117，失败步骤： 2
错误代码: Wsl/Service/E_FAIL

C:\Users\liuhao>wsl -v
WSL 版本: 2.5.7.0
内核版本: 6.6.87.1-1
WSLg 版本: 1.0.66
MSRDC 版本: 1.2.6074
Direct3D 版本: 1.611.1-81528511
DXCore 版本: 10.0.26100.1-240331-1435.ge-release
Windows: 10.0.26100.4061`

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How 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 script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

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

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

[liuhao16]

WslLogs-2025-06-09_14-23-35.zip

[github-actions]

Diagnostic information

.wslconfig found
Detected appx version: 2.5.7.0
Detected user visible error: Wsl/Service/CreateInstance/E_FAIL
Detected user visible error: Wsl/Service/CreateInstance/E_FAIL

[OneBlue]

Thank you for reporting this @liuhao16. In the logs I can see this:

1548	False	Microsoft.Windows.Lxss.Manager	GuestLog	0	06-08-2025 23:23:55.272	"	"	"text: 	""[    0.749312] JBD2: journal transaction 1275392 on sdd-8 is corrupt. ""
vmId: 	{1ab413d4-285b-4c16-abdd-637bf25a9057}"				7224	26076	5		00000000-0000-0000-0000-000000000000		
1549	False	Microsoft.Windows.Lxss.Manager	GuestLog	0	06-08-2025 23:23:55.272	"	"	"text: 	""[    0.749609] EXT4-fs (sdd): error loading journal ""
vmId: 	{1ab413d4-285b-4c16-abdd-637bf25a9057}"				7224	26076	5		00000000-0000-0000-0000-000000000000		
1550	False	Microsoft.Windows.Lxss.Manager	GuestLog	0	06-08-2025 23:23:55.275	"	"	"text: 	""[    0.752396] WSL (1 - LaunchDistro) ERROR: UtilMount:1704: mount(/dev/sdd, /distro, ext4, 0x0x, discard,errors=remount-ro,data=ordered) failed 117 ""
vmId: 	{1ab413d4-285b-4c16-abdd-637bf25a9057}"				7224	26076	5		00000000-0000-0000-0000-000000000000		

Based on the output, it looks like you need to run fsck on the disk. Here are instructions on how to do that: https://learn.microsoft.com/en-us/windows/wsl/disk-space#how-to-repair-a-vhd-mounting-error

[201983001]

可能是磁盘空间满了，昨天我也是显示无法挂载，结果一看D盘就剩几K了

[wsd12345]

WslLogs-2025-07-11_09-31-50.zip.
I encountered a similar error, but wsl.exe lsbl not work.