From PowerShell on Windows, run wsl --distribution Ubuntu. Use the exact distribution name reported by your installation; running wsl alone starts the default distribution, which may not be Ubuntu.

Find the installed name

wsl --list --verbose
wsl --distribution Ubuntu

If the list contains a versioned name, such as Ubuntu-24.04, substitute that exact name. To start in the Linux home directory:

wsl --distribution Ubuntu ~

You are now using the distribution’s Linux shell inside the terminal. Type exit to return to PowerShell. Use Bash directory navigation when moving around the Linux filesystem.

If Ubuntu is not installed

On a supported Windows system, open PowerShell as administrator and run:

wsl --install -d Ubuntu

Restart if prompted, launch the distribution and complete its first-run user setup. Check Microsoft’s installation guide for Windows requirements or organization-managed devices.

Common mix-ups

  • Wrong distribution: list distributions and pass the exact name instead of assuming the default is Ubuntu.
  • Command not found: WSL may not be installed or available in that Windows environment.
  • Linux command entered in PowerShell: launch WSL before using Bash syntax. PowerShell and Bash are different shells.

For a terminal that closes immediately after a Windows script, see keeping PowerShell open.

Sources and verification

Commands checked against Microsoft WSL documentation. Installation and distribution launch were not executed on Windows for this revision.

Next steps inside Ubuntu

After opening the intended distribution, check its Linux filesystem space before installing larger tools. If service commands fail, use the systemctl environment checklist. For a separate Ubuntu machine on your network, follow the Ubuntu SSH guide; WSL networking has additional environment-specific requirements.

Install software in the selected distribution

For repository lookup failures, use the APT troubleshooting guide. For a downloaded package, follow the local .deb installation steps. If updates cannot resolve their server names, compare the host and distribution using the DNS diagnostic checklist.