==> (FIX) Here is a fix for those that has issues starting WSL after using this script <===

[Kevin Kuusela]

1. Open up powershell and write wsl -d DISTRONAME -u root
2. Delete /usr/sbin/start-systemd-namespace and /usr/sbin/enter-systemd-namespace (rm -rf XXX)
3. Edit the file /etc/bash.bashrc using your favorite text editor
   and comment out source /usr/sbin/start-systemd-namespace
   It should look something like:

# Start or enter a PID namespace in WSL2
# source /usr/sbin/start-systemd-namespace

Tada you should now be able to start the WSL again! You can remove those two lines as well if you want.

[OskyEdz]

Not strictly running the script, but after following the guide previous to this script; I get the following error trying to start wsl as you discribed.

>wsl -d DISTRONAME -u root
/usr/sbin/enter-systemd-namespace: line 10: /usr/sbin/daemonize: No such file or directory

[Kevin Kuusela]

@OskyEdz you can open the windows file explorer and go into the WSL disk and do the above instead of using the WSL cli.

[aki-k]

@codekuu I'm not sure how you think removing this setup is fixing it? There's a real fix in comment #36 (comment) for Ubuntu-22.04. For Ubuntu-20.04 this script "just works".