tag:blogger.com,1999:blog-291117001383316504.post4243965318762685145..comments2024-03-11T15:35:11.958+05:30Comments on LinuxTopic: System has not been booted with systemd as init system (PID 1) | failed to connect to bus: host is down wsl2 #linuxtopicLinuxtopichttp://www.blogger.com/profile/12411230835520798076noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-291117001383316504.post-44949920955379728532023-08-06T05:54:16.948+05:302023-08-06T05:54:16.948+05:30I have followed and executed every single command ...I have followed and executed every single command above, but system still can't reboot.<br />mmm@DESKTOP-8BG3OFE:~$ sudo reboot<br />[sudo] password for mmm:<br />System has not been booted with systemd as init system (PID 1). Can't operate.<br />Failed to connect to bus: Host is down<br />Failed to talk to init daemon.<br />mmm@DESKTOP-8BG3OFE:~$<br /><br />any other missing commands?<br />Thxmuhindrahttps://www.blogger.com/profile/15281730159292094509noreply@blogger.comtag:blogger.com,1999:blog-291117001383316504.post-5257564874065375422022-04-15T01:16:30.771+05:302022-04-15T01:16:30.771+05:30I ran all the commands as suggested. But it did no...I ran all the commands as suggested. But it did not fix the problem. For me snap version returns the following:<br />snap 2.44.3+20.04<br />snapd unavailable<br />series 16<br />Windows Subsystem for Linux -<br />kernel 4.4.0-19041-Microsoft (amd64)<br /><br />Any help to resolve the issue will be greatly appreciated.Anonymoushttps://www.blogger.com/profile/15425158524368814358noreply@blogger.com