Skip to main content
The 2026 Annual Developer Survey is live— take the Survey today!.
8 events
when toggle format what by license comment
Nov 16, 2022 at 21:58 history closed NotTheDr01ds
andrew.46
Duplicate of System has not been booted with systemd as init system (PID 1). Can't operate
Nov 16, 2022 at 21:55 comment added NotTheDr01ds Good to hear -- Yes, that's what I was assuming your issue was. Marking this as a duplicate of System has not been booted with systemd as init system (PID 1). Can't operate. I do cover in one of my answers there that you have to install the latest WSL version for Systemd to work ;-). When you see this, if you could mark this as "That solved my problem" in the header so that this gets closed out. Thanks!
Nov 16, 2022 at 19:06 comment added José Ramos The version now is the following: wsl --version Versión de WSL: 1.0.0.0 Versión de kernel: 5.15.74.2 Versión de WSLg: 1.0.47 Versión de MSRDC: 1.2.3575 Versión de Direct3D: 1.606.4 Versión DXCore: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Versión de Windows: 10.0.22000.1219 I hope this could help others to have Ubuntu in WSL2 and SYSTEMD working.
Nov 16, 2022 at 19:03 comment added José Ramos I have already found the issue. Eventhough It was WSL2, was a latter version. I find out that the version that comes with Windows 11 is outdated, and doesn´t update when we run the Windows updates. Also find out that the latest version is the one in Windows Store. I have installed that one and now SYSTEMD works very well, and also could install the the snap packages...
Nov 16, 2022 at 16:48 history edited NotTheDr01ds CC BY-SA 4.0
Formatting and clarity
Nov 16, 2022 at 16:46 comment added NotTheDr01ds Can you add the output of wsl --version to your question (in code-blocks). Thanks!
S Nov 16, 2022 at 16:28 review First questions
Nov 16, 2022 at 22:05
S Nov 16, 2022 at 16:28 history asked José Ramos CC BY-SA 4.0