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:

• Systemd not starting correctly on fresh install after reboot (#9207), similarity score: 0.80

Closed similar issues:

• systemd no longer boots (#10557), similarity score: 0.83
• Distro not booting with systemd enabled (#9850), similarity score: 0.81
• Ubuntu 22.04 with systemd can't start (#11411), similarity score: 0.77
• OpenSuSE leap 15.4 on WSL2 will not start after enabling systemd (#9602), similarity score: 0.77

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

Appx package is not installed

from wsl.

Installing wsl should means It'll comes with the latest kernel version. It doesn't in my case

Unfortunately this is our bleeding open wound.

All our problems start here with the old version still in existence and it is installed by default anytime someone tries to install WSL. This is partly due to using windows 10 versions, as it had accumulated many sub-versions over the years.

Installing the newer, systemd compatible version has its pain all the time, and now it seems the store version (which previously was working) is broken and that dism method is the only one I read working for the moment.

You will need to experiment with the installation until you finally get at least 5.15.xxx kernel.

I've tried updating and upgrading. It doesn't update to the latest version still.
Now I can't even seems to get ubuntu to launch after downloading It. I'm being met with this error WslRegisterDistribution failed with error: 0x8037010d Error: 0x8037010d The virtual machine or container JSON document is invalid.

from wsl.

Issue was edited and new log file was found: https://github.com/user-attachments/files/15822158/WslLogs-2024-06-13_15-29-23.zip
Appx package is not installed

from wsl.

Is systemd=true on a separate line like this:

[boot]
systemd=true

from wsl.

Is systemd=true on a separate line like this:

[boot]

systemd=true

Yes it's

from wsl.

as a first aid, please delete your current ubuntu and reinstall it, but do not edit config file.

Last time I have checked (around 6 months), Ubuntu 22.04 image had a working configuration file, and the editor you have used might have broken its content. that is why I ask to leave the file alone.

also give the output for this command: wsl --version

from wsl.

Kernel Version

5.10.102.1

I could only see now this detail in your main post.

This kernel is the old one that is incompatible with systemd. please follow latest answers in the other discussion on how to get the correct one.

you will need version 5.15.xxx

from wsl.

Could you also try making sure you're on the latest WSL version? Please try running wsl --install or wsl --update to update. You'll know you're on latest if you run wsl --version and it has a readable output.

from wsl.

as a first aid, please delete your current ubuntu and reinstall it, but do not edit config file.

Last time I have checked (around 6 months), Ubuntu 22.04 image had a working configuration file, and the editor you have used might have broken its content. that is why I ask to leave the file alone.

also give the output for this command: wsl --version

I've uninstall and reinstall it multiples, It does'work. The wsl --version command does not work on my powerShell cl

from wsl.

uninstall and reinstal

Kernel Version

5.10.102.1

I could only see now this detail in your main post.

This kernel is the old one that is incompatible with systemd. please follow latest answers in the other discussion on how to get the correct one.

you will need version 5.15.xxx

Installing wsl should means It'll comes with the latest kernel version. It doesn't in my case

from wsl.

Installing wsl should means It'll comes with the latest kernel version. It doesn't in my case

Unfortunately this is our bleeding open wound.

All our problems start here with the old version still in existence and it is installed by default anytime someone tries to install WSL. This is partly due to using windows 10 versions, as it had accumulated many sub-versions over the years.

Installing the newer, systemd compatible version has its pain all the time, and now it seems the store version (which previously was working) is broken and that dism method is the only one I read working for the moment.

You will need to experiment with the installation until you finally get at least 5.15.xxx kernel.

from wsl.

This last error is a bit annoying as I am unfamiliar with that.

My experience with the WSL installation steps had no problems so far, so I am having hard times when someone fails to get the correct kernel version. (You may notice this in my posts that my help is all about steps after getting past this step).

Other than a complete system reinstall (if possible), unfortunately I am failing to offer you any advice to follow.

Can you please search for, or open a new issue, why you are getting this headache to get the latest WSL kernel on your system.

Another way is to wait for someone that could help to notice this issue, but it will be slow as you may guess.

from wsl.

Windows Version

Microsoft Windows [Version 10.0.21996.1]

This release version number seems to belong to the very first Windows 11 releases.

The first update to Windows, coded to be 21H2, is dated October 2021 and has "22000" version build number. Later, we got 22H2 in 2022 (22621) and 23H2 in 2023 (22631).

My current guess is that your system did not update at least required parts of the system, thus it fails to install the required WSL kernel.

If you are still struggling about this WSL installation, please try again after updating your system to at least 21H2.

Let us know if you find a fix for your system, especially if updating the system helps, so we can add your experience to our list of solutions.

from wsl.