System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down

[MinWook6457]

Windows Version

Microsoft Window 10.0.22621.4317

WSL Version

WSL 버전: 2.3.24.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Ubuntu

Other Software

No response

Repro Steps

while checking systemctl, I encountered the following issue:

System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

Expected Behavior

So I specified the following options in the wsl.conf file:

[boot]
systemd = true

This did not resolve the issue, so I added the .wslconfig file to the C:\Users{name}\ subpath with the following content:

[wsl2]
bootCommand = ""

But it wasn't resolved..!

Picture

My PSTREE

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 [email protected] 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'.

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 Booting Up in WSL 2 Despite Configuration in wsl.conf (#11690), similarity score: 0.78

Closed similar issues:

• systemd Not Booting Up in WSL 2 Despite Configuration in wsl.conf (#11681), similarity score: 0.81
• systemd no longer boots (#10557), similarity score: 0.80
• Systemctl not working as expected (#10428), similarity score: 0.79
• [PID 1 Error] "failed to connect to bus: no such file or directory" Windows 10, WSL 2, Debian - possible fix detailed (#10350), similarity score: 0.78

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

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!