Skip to main content
The 2026 Annual Developer Survey is live— take the Survey today!.

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 1
    As of September systemd is available in WSL Commented Oct 8, 2022 at 8:29
  • 1
    @Henke Right - All good points. While I probably could have gone into more detail on why I recommended removing the ~/.motd_shown, it's really so that it's easy to confirm that the problem is really resolved when you exit and restart. Otherwise, the MOTD might not be shown again until the next day. I suggest leaving it in place (but it's fine to remove it entirely), just temporarily delete it to make sure it triggers again for confirmation. Commented Nov 29, 2022 at 16:16
  • There's no need to restart the entire computer. You can restart the WSL subsystem alone by running wsl --shutdown on the Windows side to shutdown the entire WSL subsystem and kill all WSL processes, then start a new WSL shell. (Remove ~/.motd_shown first if you want to test the MOTD message.) Commented Jul 30, 2023 at 18:58
  • @DevenT.Corzine Of course - Agreed that there's no need to restart the whole computer; but I never said to restart the computer itself ;-). When I say "exit and restart" in this case, I just mean exit the shell and restart. There's not even any reason to restart the subsystem itself in this case with wsl --shutdown. Commented Jul 30, 2023 at 21:37
  • @DevenT.Corzine Updated the answer for clarity :-) Commented Jul 30, 2023 at 22:36