Install WSL 2 on Windows 11 and prove the Linux environment is current

Windows Subsystem for Linux is useful for development, but a successful installer message does not prove that the intended distribution is running on WSL 2. A machine can retain an older distro, an out-of-date WSL kernel or a disabled virtualization setting. Work from observable state: Windows edition and build, available distributions, installed version and one reproducible Linux command. This also avoids installing a second Ubuntu instance when the first one merely needs repair.

Before you start​

Save open work because enabling required Windows features can restart the PC. Check firmware virtualization in Task Manager's CPU pane and ask IT before changing a managed computer. Back up an existing WSL distro with wsl --export before changing its installation. Record which distro contains your projects; the name shown in a shortcut is not necessarily its registered WSL name.

Do it step by step​

1. Open a regular PowerShell window and run wsl --status, then wsl --list --verbose. Note the default distribution, registered names and VERSION column before touching the installer.
2. If no distro is installed, run wsl --list --online, choose a trusted distribution, and install with wsl --install -d followed by its listed name. Restart only when prompted and complete its first-run Linux username setup.
3. Run wsl --update and then wsl --status again. If an organization controls Store access, follow Microsoft's documented alternate installation path instead of downloading an unofficial kernel package.
4. Run wsl --list --verbose. If the intended distro reports version 1 and you need WSL 2, first export it, then use wsl --set-version with the exact registered name and 2; allow conversion to finish.
5. Launch that distribution, run uname -a and a simple file creation under your Linux home directory. Keep Linux project files in the Linux filesystem for workloads that benefit from its file performance.
6. Close the shell, run wsl --shutdown only after saving Linux work, reopen it and confirm the file remains. Record the distro name and export location for future recovery.

Check the result​

The intended distribution appears as VERSION 2, opens under the expected Linux user and preserves a test file after shutdown and relaunch. wsl --status reports a working installation.

If something goes wrong​

If install reports virtualization unavailable, verify firmware settings and Windows features against Microsoft's requirements. If the distro opens as a different user after import, correct its default-user configuration; do not assume missing files were erased. Capture the actual command error before resetting anything.

Know the limit​

WSL is a development environment, not a backup or a substitute for Windows security updates. Some hardware and enterprise policies restrict virtualization; a distro conversion can take time and requires free disk space. Do not unregister an existing distro during troubleshooting unless a tested export exists. Microsoft WSL installation WSL commands

Decision checkpoint​

Choose WSL 2 when the Linux tools and filesystem behavior actually fit your project. If all you need is a single command-line utility, a native Windows build may be easier to patch and support. For a team repository, record the distro version and required packages in project documentation so a colleague can reproduce the environment. Before upgrading WSL, export the distro and test a project command, then repeat that same command after the change. A successful Linux prompt is only the first test.