Ubuntu failed to boot

[LanceJZ]

Windows Version

Microsoft Windows 10.0.19045.5555

WSL Version

2.4.11.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Ubuntu 24.04

Other Software

I'm having the same issue when I try to start Ubuntu, none of the things listed here resolved it. Here are my logs. My install has been working great for months until I attempted to make it so I could read the ext4 file system using Ubuntu. Thank you for any help you can give.

WslLogs-2025-02-25_17-37-39.zip

Repro Steps

I was following the instructions on this site. https://www.tomshardware.com/how-to/access-linux-ext4-partitions-in-windows

Expected Behavior

WSL2 Boots.

Actual Behavior

Ubuntu Boots.

Diagnostic Logs

See zip file attached.

[github-actions]

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information

.wslconfig found
	Custom kernel found: 'C:\users\lance\vmlinux'
appxpackage.txt not found
Found no WSL traces in the logs

[LanceJZ]

@github-actions how? I attempt to open Ubuntu and you see the screen I attached. WSL never starts. That is the issue I need fixed.

[OneBlue]

/logs

[LanceJZ]

@microsoft-github-policy-service I attempted to run it and got a ParserError.
PS C:\Users\lance> .\collect-wsl-logs.ps1
ParserError: C:\Users\lance\collect-wsl-logs.ps1:42
Line |
42 | … script type="application/json" id="client-env">{"locale":"en","featur …
| ~~~~~
| Unexpected token ':"en"' in expression or statement.
PS C:\Users\lance>
I ran one like that to get my orginal logs.

[LanceJZ]

/logs

I supplied the logs, they are attached.

[OneBlue]

@LanceJZ: The logs you shared earlier don't contains any WSL logs. Did you reproduce the issue while the script was running ?

Based on the powershell output, it looks like you have an HTML file instead of the PS1 script. Can you make sure you have the right file ?

/logs

[LanceJZ]

@OneBlue what am I supposed to do about that? I got the logs I can get. I got what the script put inside the zip file. That is all I have, and all I can get.

[OneBlue]

@LanceJZ: Can you try again ? You need to reproduce the issue while the log collection script is running so we can see where the issue is coming from.

/logs

[LanceJZ]

@OneBlue I was able to figure out why when I downloaded the ps1 file, it failed, it was a link to github, you can't download that by right clicking and saving it. You have to go there and copy it, if it is a text file, or download the repo.
Here is the new log, sorry about my frustration.

WslLogs-2025-03-07_21-28-28.zip

[github-actions]

Diagnostic information

.wslconfig found
	Custom kernel command line found: 'noxsave'
	Custom kernel found: 'C:\users\lance\vmlinux'
appxpackage.txt not found
Detected user visible error: Wsl/Service/CreateInstance/CreateVm/WSAENOTCONN

[LanceJZ]

I added the line 'kernelCommandLine=noxsave' in an attempt to get it working, it still fails, was in another issue in dealing with that error.

[OneBlue]

Thank you @LanceJZ. Looking through the logs, it looks like the VM is completely failing to boot.

I'm going to guess that it's because of the custom kernel in .wslconfig. Can you try to remove it and see if that solves the issue ?

[LanceJZ]

Huh, that fixed it...
That line "kernel=C:\users\lance\vmlinux" was already in there, I did not add it, so I did not want to touch it. I did not know what it did.
It is working now, thank you. You saved me days of work, that install is months old, and has so much setup in it. I owe you big time!

[OneBlue]

You're welcome. Closing, since the issue is resolved.