The core problem, as mention in the comments, is that WSL doesn't use Systemd, even in distributions where it is the default. In the case of systemctl and attempting to start ssh, you are seeing both.
System has not been booted with systemd as init system (PID 1). In general, when you see either of the following two messages: So this looks like a good one to use for that purpose. Surprisingly, after 5 years or so of WSL, there doesn't seem to be a good, general-purpose "Systemd" question here on Ask Ubuntu. Enabling Systemd in WSL on older releases. Manually running the appropriate command. See below for more details as well as alternative solutions, which include: This can often (but not always) be done on Ubuntu on WSL using: sudo service start 
The most common use of systemctl is to start services. If(-not(test-path $downloadLocation))Įxpand-Archive $newName.Note that there is now a new solution for enabling Systemd on recent WSL releases on Windows 11. $fileDownload = "$downloadLocation\$releaseName" $releaseName = ($LatestBundle -split "/") $downloadLocation = "C:\temp\WindowsTerminal"
$LatestBundle = "$(($ -match "msixbundle"))" This is a dirty way of doing it automagically $webData = invoke-webrequest "" -UseBasicParsing The downside of the method is you have to manually check and re-do this everytime there is a new version.
Extract the “CascadiaPackage_XXXX_圆4.msix” and rename that. However if you want to Windows Terminal on a Server (and let’s be honest, that’s a much more likely use case?) you can do this: If you DO have access to te Windows Store, you can just go to and install it. Since most servers either don’t have a Windows Store, or no access to a Windows Store, it was a bit silly from MSFT to release Windows Terminal ONLY to be installed via Windows Store.
0 kommentar(er)
