WSL Container Desktop 2.3.0
What's new in this version — full changelog.
Install (recommended: download only the helper)
- Download Install.ps1 below into a writable folder.
- Open PowerShell in that folder and run:
powershell -ExecutionPolicy Bypass -File .\Install.ps1- The helper downloads and verifies this release's missing
.cerand.msix.
Approve the administrator prompt to trust the displayed publisher certificate.
The app then installs in your original Windows session. - Launch WSL Container Desktop from the Start menu.
Internet access is needed only for missing assets. For offline installation, put this release's
.cer and .msix beside the script first. Saved scripts stay pinned to their original release;
download a fresh helper from the latest stable release to install a newer version.
-ExecutionPolicy Bypass applies only to this PowerShell process; it does not change your
machine's policy. It avoids the default RemoteSigned block on this unsigned downloaded script.
Alternatively, unblock only the helper, then right-click Install.ps1 > Run with PowerShell:
Unblock-File -Path .\Install.ps1Manual installation (without a script)
- Download the
.msixand.cerassets below into the same folder. - Open that folder, then open an elevated PowerShell (Run as administrator).
cdinto the download folder and run (adjust the file names to this release):
Import-Certificate -FilePath .\WSLContainerDesktop-Signing.cer -CertStoreLocation Cert:\LocalMachine\TrustedPeople
Add-AppxPackage -Path .\WSLContainerDesktop_2.3.0_x64.msix -ForceUpdateFromAnyVersion- Launch WSL Container Desktop from the Start menu.
The first command trusts the app's self-signed publisher certificate (CN=Michael Hacker)
so Windows accepts the sideloaded package; the second installs (or updates) the app.
Updating
Once installed, the app checks for new releases when it starts and offers Update now,
which downloads, installs and reopens it. You can also update manually by repeating the
steps above with a newer release.
Self-signed, self-contained package (bundles the .NET and Windows App SDK runtimes, so nothing else is required). Not a Microsoft product and carries no warranty - see the repository README.