WSL Linux Distros Easy Install on Windows 10

Yes, installing Linux distributions on Windows 10 via the Windows Subsystem for Linux (WSL) is now remarkably easy—typically just a single command or a few clicks in the Microsoft Store. You no longer need to dual-boot, run a virtual machine, or fiddle with bootloaders; WSL gives you a genuine Linux environment running directly on Windows.

Background: From Insider Preview to Mainstream

WSL was first introduced as a beta feature in Windows 10 build 14316 (April 2016), aimed at developers who needed Linux tools without leaving Windows. The original WSL (now called WSL1) used a translation layer that mapped Linux system calls to Windows kernel calls, which worked for many command-line tools but had compatibility gaps. In 2019, Microsoft released WSL2, a complete redesign that runs a real Linux kernel inside a lightweight virtual machine. WSL2 dramatically improved file system performance and compatibility, making it suitable for Docker, databases, and other system-level software. Since Windows 10 version 2004 (May 2020), WSL2 has been the default when you install a distribution, and the installation process itself has been streamlined to a single command.

How to Install a Linux Distro in WSL

There are two primary ways to install a Linux distribution on Windows 10 with WSL:

One-command install (recommended): Open PowerShell or Command Prompt as Administrator and run wsl --install. This command enables the required Windows features, downloads the latest WSL2 kernel, and installs the default distribution (usually Ubuntu) automatically. After a reboot, you’ll be prompted to create a UNIX username and password.
Manual installation via Microsoft Store: Search for your preferred distribution (e.g., Ubuntu, Debian, Kali Linux, openSUSE, Alpine) in the Microsoft Store, click Install, then launch it from the Start menu. This method gives you more choice but requires that WSL is already enabled (you can enable it with dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart and then reboot).

For Windows 10 versions before 2004, you must manually enable the “Windows Subsystem for Linux” feature and the “Virtual Machine Platform” feature (for WSL2) via Control Panel or PowerShell, then reboot, then install a distro from the Store. If you’re on an older build, updating Windows is the best first step.

Which Distro Should You Choose?

Your choice depends on your needs:

Ubuntu – The most popular, best-documented, and default in WSL. Great for beginners and general development.
Debian – Stable and minimal, good for servers and users who prefer a more conservative rolling release.
Kali Linux – Penetration testing and security tools preinstalled. Not recommended for everyday use.
openSUSE – Offers both Leap (stable) and Tumbleweed (rolling) versions, good for enterprise and system administration.
Alpine Linux – Extremely small and fast, ideal for containers and resource-constrained environments.
Fedora – Available via the Store (though not officially from Microsoft), brings the latest software and a Red Hat ecosystem.

You can also install multiple distributions side by side; each runs as a separate instance with its own file system and settings.

Common Problems and How to Fix Them

Even with a smooth installation, you may encounter issues:

WSL2 requires a virtual machine platform: If you get an error about “Virtual Machine Platform” not enabled, run wsl --set-default-version 2 and ensure the feature is turned on in Windows Features.
Installation hangs at “Installing, this may take a few minutes”: This often happens when the Windows Update service is disabled. Start the “Windows Update” service and try again.
WSL not recognized as a command: If wsl is not found, you’re on an older Windows 10 build. Update to at least version 1903 (for WSL1) or 2004 (for WSL2).
Cannot access the internet inside WSL: Try restarting WSL with wsl --shutdown and then relaunch your distro. Also check your corporate firewall or VPN settings.
File system performance is slow: If you’re working with files in your Windows home directory (e.g., /mnt/c/Users/…), performance can be poor. Keep project files inside the Linux file system (e.g., ~/projects) for best speed.

WSL vs. Virtual Machines vs. Dual Boot

WSL is not the only way to run Linux on Windows. Here’s how it compares:

WSL2: Lightweight, starts in seconds, integrates seamlessly with Windows (you can run Linux commands from PowerShell, share environment variables, and access Windows files from Linux). It uses a VM under the hood, but you don’t manage it—it’s transparent. Ideal for developers, system administrators, and anyone who needs command-line tools.
Full Virtual Machine (e.g., VirtualBox, VMware, Hyper-V): Runs a complete Linux desktop with its own kernel, drivers, and GUI. Heavier on resources, slower to boot, but gives you an isolated environment and the ability to run a graphical desktop. Good for testing distros, running servers, or using Linux as a daily driver.
Dual Boot: Install Linux on a separate partition and choose which OS to boot at startup. Best performance and full hardware access, but you can’t run both OSes simultaneously, and switching requires a reboot. Good for gamers or users who need native graphics performance.

For most people who just need Linux tools, WSL2 is the easiest and most convenient option. If you need a GUI or full desktop experience, a VM might be better. If you’re a serious Linux user who wants maximum performance, dual boot is still the way.

Cost and System Requirements

WSL is completely free—both the feature and the distributions available in the Microsoft Store are free to download and use. You only need a licensed copy of Windows 10. The system requirements are modest:

Windows 10 version 2004 or higher (build 19041 or later) for WSL2.
64-bit CPU with virtualization support (VT-x/AMD-V) enabled in BIOS/UEFI.
At least 4 GB RAM (8 GB recommended, especially if you run multiple distros or Docker).
Several gigabytes of free disk space for the Linux file system and installed packages.

If you have an older 32-bit CPU, WSL will not work, but that hardware is quite old now.

Safety and Security Considerations

WSL is a legitimate Microsoft feature, and the distributions come from official sources (e.g., Canonical for Ubuntu, Debian project for Debian). However, you should still practice good security hygiene:

Keep your WSL distro updated with sudo apt update && sudo apt upgrade (for Debian/Ubuntu) to patch security vulnerabilities.
Be careful when running commands with sudo—they have full root access inside the Linux environment, but they cannot affect Windows itself (WSL runs in a user context).
Access to Windows files from WSL is read/write, so a malicious script could modify your Windows files. Only run scripts from trusted sources.
WSL2 uses a virtual network adapter; it’s isolated from your main network by default, but you can configure port forwarding. If you run services, be aware they may be accessible from your local network.

Alternatives to WSL

If WSL doesn’t meet your needs, consider:

Git Bash – A simple Unix-like shell for Windows, but not a full Linux environment. Good for basic Git and command-line tasks.
MSYS2 / Cygwin – Provide a POSIX compatibility layer and a package manager, but they don’t run Linux binaries natively.
Docker Desktop – Uses WSL2 under the hood, but gives you containers for running Linux applications in isolation.
Cloud Linux VMs – If you need a persistent Linux server, you can rent a cheap VPS and SSH into it.

Frequently Asked Questions

Can I install WSL on Windows 10 Home?

Yes, WSL is available on all editions of Windows 10, including Home. WSL2 requires the Virtual Machine Platform feature, which is also available on Home. You do not need Pro or Enterprise.

How do I uninstall a Linux distro from WSL?

You can uninstall the distribution like any other app: go to Settings > Apps > Apps & features, find the distro, and click Uninstall. Alternatively, use PowerShell with wsl --unregister <DistroName> to remove the distro and its file system completely.

Can I run graphical Linux applications in WSL?

Yes, with WSLg (available in Windows 10 version 21H2 and later) you can run GUI apps directly. For older versions, you can use an X server like VcXsrv or Xming and set the DISPLAY environment variable. However, this is less seamless than command-line use.

What is the difference between WSL1 and WSL2?

WSL1 translates Linux system calls to Windows ones, making it faster for file I/O on Windows drives but less compatible. WSL2 runs a real Linux kernel in a lightweight VM, giving near-native performance and full system call compatibility, but file access across the OS boundary is slower. WSL2 is the recommended default.

Can I access my Windows files from WSL?

Yes, your Windows drives are mounted under /mnt/c, /mnt/d, etc. You can read and write to them, but for performance, it’s better to keep project files in the Linux file system (e.g., /home/yourname).

Do I need to reboot after running wsl –install?

Yes, the installer will typically ask you to reboot to finish enabling the required Windows features. After rebooting, you can launch the installed distro from the Start menu.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →