How to Install a Linux Distribution on Windows 10/11 with WSL & WSL2

How to Install a Linux Distribution on Windows 10/11 with WSL & WSL2

development tools howto linux linux on windows virtualization windows windows 10 windows 11 wsl wsl2

Abdullah Musa

April 25, 2025

You no longer have to choose between the familiarity of Windows and the sheer flexibility of Linux. By leveraging the Windows Subsystem for Linux (WSL2), you can run a native Linux kernel directly alongside your Windows applications, creating a high-performance hybrid environment that is perfect for modern development and devops workflows.

Hi all, welcome to MusaBase! If you are looking to bridge the gap between Windows and Linux for development or testing, you're in the right place. In this step-by-step guide, we will learn how to install and configure a Linux distribution on Windows 10/11 using WSL or WSL2.

This comprehensive guide is designed to help you set up a high-performance environment without the need for dual-booting. Specifically, we'll cover how to:

• Enable essential Windows features for WSL dependencies
• Install and update WSL to the latest version
• Configure WSL for optimal resource management
• Run native Linux apps directly on your Windows desktop
• Set up an X server for graphical application support
• Run a full Linux desktop environment side-by-side with Windows

By the end of this walkthrough, you'll be able to enjoy Linux services, a powerful Linux terminal, and the seamless ability to run your favorite open-source tools within your Windows workflow.

---

Table of Contents:

• What is WSL/WSL2?
• Prerequisites
• Step 1: Enable Windows Features for WSL & WSL2
• Step 2: Install WSL & WSL2 on Windows 10/11
• Step 3: Launch Linux Shell with WSL/WSL2
• Step 4: Implementing GUI for WSL
• What's Next for You?

---

What is WSL/WSL2?

WSL, short for Windows Subsystem for Linux, allows us to run a Linux distribution alongside Windows without a resource-heavy VM. WSL1 uses a compatibility layer to translate Linux system calls to Windows, while WSL2 boosts performance and compatibility by using a real Linux kernel inside a lightweight VM. WSL2 is available on Windows 10 (version 2004, build 19041 or later) and Windows 11. Installing on Windows 11 is nearly identical and benefits from tighter OS integration.

Feature	WSL1	WSL2
Architecture	Translation layer	Lightweight VM
Performance	Good for file operations	Better overall
Compatibility	Limited	Full Linux kernel

• No dual-booting required: Switch between Windows and Linux instantly
• Resource efficient: Uses minimal RAM compared to traditional VMs
• Seamless integration: Access Windows files from Linux and vice versa
• GPU support: WSL2 supports CUDA, Docker, and GPU acceleration

Note: This guide focuses on WSL2 as it's the current standard with full Linux kernel support and better performance.

---

Prerequisites

• Processor: Intel or AMD 64-bit compatible processor. It must support virtualization technology (Intel VT-x or AMD-V), which should be enabled in your BIOS/UEFI settings.
• RAM: 8GB to 32GB is recommended. While WSL2 can run on less, more RAM significantly improves performance when running multiple Linux services.
• Storage: Approximately 5GB for the WSL2 base, plus additional space for each Linux distribution you install. Using an SSD is highly recommended for faster disk I/O.
• Windows Version:
  • Administrator Rights: You need administrator privileges to install WSL and enable Windows features.
  • Windows 10: Version 2004 (Build 19041 or later) for WSL2 support. You can check your version by typing winver in the Windows search bar.
  • Windows 11: All versions are fully compatible with WSL2 out of the box.

Virtualization Check: Press Ctrl + Shift + Esc to open Task Manager, go to Performance tab, and check if Virtualization is enabled under CPU.

---

Step 1: Enable Windows Features for WSL & WSL2

WSL requires two Windows features on Windows 10/11:

• Windows Subsystem for Linux
• Virtual Machine Platform

We can enable these two features either through:

• GUI (Graphical)
• PowerShell (Admin)

1.1. Enable via GUI

• Press the Windows key or open Start menu and type "Turn Windows features on or off" and open it.

• In the Windows Features dialog, check:
  • Virtual Machine Platform
  • Windows Subsystem for Linux

1.2. Enable via PowerShell (Admin)

• Press the Windows key or open Start menu, type PowerShell in the search box, then right-click and select Run as Administrator.
• In the elevated console, run:

dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

Once the features are enabled (via GUI or PowerShell), restart your PC to complete the installation.

---

Step 2: Install WSL & WSL2 on Windows 10/11

If you're running a supported Windows 10 build (2004, Build 19041 or later) or Windows 11, Microsoft provides a single command to install WSL end-to-end.

• Open PowerShell as an administrator.
• Run the command:

wsl --install

Note: This command requires an active internet connection to download the Linux kernel and distribution.

When we run wsl --install, it will:

• Automatically enable any missing WSL components.
• Download and install the latest Linux kernel.
• Configure WSL2 as the default version.
• Download and install the default Linux distribution, typically Ubuntu.

• After the installation finishes, restart your PC to apply all changes.

---

Step 3: Launch Linux Shell with WSL/WSL2

With the minimal Ubuntu installation complete, let's launch our new Linux environment.

• Open PowerShell as an administrator.
• Run the command:

wsl

After running the command, the WSL system will ask you to set a username and password. Enter these, and it will log you into your Ubuntu Linux system.

First-time Setup Tips:

• Username can be lowercase only (no spaces)
• Password won't show characters as you type (normal Linux behavior)
• You'll need this password for sudo commands

Launch from Start Menu

• From Start Menu: Search for "Ubuntu"
• From Windows Terminal: Available in Microsoft Store
• Command Prompt: Just type wsl

Now, we can launch any Linux application in Windows via the WSL terminal or from the Start menu. Any application we install in Ubuntu will appear there, ready to launch with a single click.

A simple demonstration:

I'm going to run Krita, a powerful digital painting application originally designed for Linux.

Keep in mind this is a bare-minimum Linux system, which initially provides only a command-line interface (CLI).

---

Step 4: Implementing GUI for WSL

Now, even though WSL (and WSL2) lets us run Linux and its apps on Windows, it's fundamentally designed as a command-line interface. That means we can only interact via commands. However, we can still install and run a full Linux desktop environment (for this guide, "Ubuntu") using one of two methods:

• X Server method
• Remote Desktop Protocol (RDP) method

4.1: X Server Method

X Server (Xorg) is a display server that provides a graphical interface for Linux applications. It bridges hardware and graphics software, letting GUI apps render on our Windows screen and accept keyboard/mouse input.

4.1.1. Download X Server

• Download VcXsrv (X Server for Windows) from the SourceForge link.
• Install it.
• URL for VcXsrv:

https://sourceforge.net/projects/vcxsrv/

Now that Ubuntu is installed under WSL, open the Ubuntu terminal from the Start menu by typing "Terminal" in the search box.

• By default, we'll get PowerShell. We can switch to Ubuntu by selecting it from the dropdown menu in the terminal's top left corner.

4.1.2. Update, Hold & Upgrade Packages

• In the Ubuntu terminal, run these commands consecutively:

sudo apt update
sudo apt-mark hold acpid
sudo apt upgrade -y

Note: The apt upgrade may take several minutes depending on your internet speed and number of updates available.

• sudo apt-mark hold acpid: Tells APT to lock acpid at its current version so that it won't be upgraded, removed, or newly installed by any subsequent apt upgrade or dependency operation.
• The acpid package provides ACPI event handling such as power-button and battery events on Linux, but WSL2 doesn't support ACPI hardware events because we are in a virtual machine. When acpid is installed or upgraded inside a WSL2 distro, it fails to bind to ACPI sockets, flooding systemd with errors and crashing services or desktop sessions. Marking acpid on hold prevents its installation or upgrade, which helps avoid these limitless error loops and creates a stable desktop environment on an X Server under WSL2.

4.1.3. Install Ubuntu Desktop & GNOME

• In the terminal, run:

sudo apt install ubuntu-desktop gnome

We can install any supported desktop environment such as KDE Plasma, MATE, etc. But in this article, GNOME desktop session on X Server makes more sense because it's native to Ubuntu.

Note: If you already have systemd enabled (systemd=true) in your /etc/wsl.conf file, then skip the next two steps (4.1.4 and 4.1.5).

4.1.4. Enable Systemd

Ensure systemd is enabled (systemd=true) in the wsl.conf file.

• In the Ubuntu terminal, run:

sudo nano /etc/wsl.conf

• If the line systemd=true isn't present, add it under the [boot] section. Then press Ctrl + O to save and Ctrl + X to exit.
• Please see the images below for clarification:

4.1.5. Update WSL

• In the Ubuntu terminal, type exit to close the WSL session.
• In Windows PowerShell, run these two commands consecutively:

wsl --shutdown
wsl --update

• wsl --shutdown: Will close any running WSL instances.
• wsl --update: Will update the WSL kernel to the latest version if available.

4.1.6. Define Environment Variables

• Reopen the Ubuntu terminal.
• Next, run:

sudo nano ~/.bashrc

• In the bashrc file, navigate to the bottom with the down () arrow keys and add the environment variables below. Then press Ctrl + O to save and Ctrl + X to exit:

export DISPLAY="$(ip route | awk '{print $3; exit}')":0
export XDG_CONFIG_HOME=$HOME/.config
export XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg
export XDG_SESSION_DESKTOP=ubuntu
export XDG_SESSION_TYPE=x11
export XDG_CURRENT_DESKTOP=ubuntu:GNOME
export XDG_DATA_DIRS=/usr/share/ubuntu:/usr/local/share/:/var/lib/snapd/desktop
export GNOME_SHELL_SESSION_MODE=ubuntu
export XDG_RUNTIME_DIR="/run/user/1000"

Export Options:

Each of these environment variables helps GUI applications and desktop-integration tools locate configuration, data, and decide how to start and render your session.

• DISPLAY: Specifies the X Server address and screen number in the format hostname:display.screen.
• XDG_CONFIG_HOME: Base directory for user-specific configuration files (defaults to ~/.config).
• XDG_CONFIG_DIRS: Colon-separated list of system-wide configuration directories to search after XDG_CONFIG_HOME.
• XDG_SESSION_DESKTOP: Short identifier for the desktop session (such as ubuntu, plasma), used by logind and session managers.
• XDG_SESSION_TYPE: Indicates the session transport/protocol (one of x11, wayland, etc.), used by systemd-logind and related tools.
• XDG_CURRENT_DESKTOP: Desktop environment identifiers such as ubuntu:GNOME, KDE, etc. Used by xdg-utils and portals for theming and application integration.
• XDG_SESSION_CLASS: Specifies the session's class (such as user, greeter), determining how systemd-logind manages your session.
• XDG_DATA_DIRS: Colon-separated list of system-wide data directories (for icons, desktop entries, etc.), defaulting to /usr/local/share/:/usr/share.
• GNOME_SHELL_SESSION_MODE: Sets GNOME Shell's session mode (e.g., ubuntu, classic), overriding the --mode flag and selecting which GNOME extensions and panels to load.
• XDG_RUNTIME_DIR: Points to a user-specific runtime directory (usually /run/user/$UID), used for sockets, PID files, and other pre-session transient data.

• Next, in the terminal run these commands consecutively:

sudo mkdir -p /run/user/1000
sudo chmod 700 /run/user/1000
sudo chown $(whoami): /run/user/1000

These three commands ensure that the XDG runtime directory (/run/user/1000) exists, is owned by our user, and has secure permissions so that user-specific runtime files like D-Bus sockets can be created and accessed by desktop services.
Without this directory properly set up, GUI applications and user services relying on $XDG_RUNTIME_DIR will fail to start or communicate.

4.1.7. Launch X Server

Now launch VcXsrv (X Server) that we installed earlier.

• Open the Start menu, type xlaunch, and run the application.
• On the "Select display settings" screen, choose "One large window" or "Fullscreen" based on your needs and click Next.
• On the "Select how to start clients" screen, choose "Start no client" and click Next.
• On the "Extra settings" screen, tick all checkboxes and add the following parameter in the Additional parameters for VcXsrv field at the bottom, then click Next:

-dpms

• On the final screen, click Finish. VcXsrv will start, but you might see a black window until we launch our desktop session.

4.1.8. Launch Desktop Session

• Switch back to the Ubuntu terminal in WSL.
• Run the following command:

dbus-launch --exit-with-session gnome-session

4.2: Remote Desktop Protocol (RDP) Method

This method is simpler to implement. With RDP, we can use any supported desktop environment without extra configuration.

4.2.1. Install Tasksel & XRDP

Tasksel is a tool that installs related groups of packages in one go, similar to APT metapackages. It offers a simple interface for tasks like setting up a desktop environment or web server stack. Meanwhile, xrdp is an open-source implementation of the Microsoft Remote Desktop Protocol server. It allows users to connect to a Linux system from another Linux machine or a Windows device using RDP clients like the Microsoft Remote Desktop Client.

• First, update your distro by running sudo apt update && sudo apt upgrade.
• Then install tasksel and xrdp:

sudo apt install tasksel xrdp

4.2.2. Install a Desktop Environment

• In the Ubuntu terminal, run the following command to launch the Tasksel interface:

sudo tasksel

• This command will open the following interface, from where we can install any Desktop Environment or Web Server stack.
• Use the keyboard's Up () and Down () arrow keys to navigate through the several options.
• Press the Space key to select the Desktop Environment you want.
• Press Tab to go to the bottom's options section, choose OK to confirm the download, and press Enter to continue.

This time I am choosing KDE Plasma for my Desktop Environment, but you can choose any given option you want.

4.2.3. Launch Ubuntu Desktop Session with RDP

• In the terminal, run the following command to get the IP address for RDP:

ip a

• This command will list network interfaces and their IP addresses.
• Note the eth0: interface's IPv4 address and copy it.
• Open the Start menu and search for RDP or Remote Desktop Connection in the search box, then open it.
• In the RDP window, paste the IP address that you just copied and click Connect.
• If all goes well, you'll see a login prompt where you can enter the username and password that you created for Ubuntu under WSL.

---

🎉 Congratulations, your WSL2 environment is ready!

WSL is an incredible tool for command-line tasks and development workflows. However, if you find the GUI performance sluggish for heavy graphical applications, you might want to explore more robust virtualization or native options.

What's Next?

🚀 Native Performance: For 100% hardware power and a lag-free experience, I highly recommend setting up a traditional Arch Linux Dual-Boot alongside Windows.

🖥️ Advanced Virtualization: If you prefer staying on Linux but need to run high-performance virtual machines, check out my guide on installing near-native VMs using QEMU/KVM.

🛠️ Support & Feedback: If you hit any errors during the WSL configuration or if your Linux desktop environment isn't responding, please let me know in the comments. I am more than happy to help.

Keep experimenting and building your perfect development environment. If this walkthrough helped you, don't forget to subscribe.
101 out, I’ll see you in the next one! 🚀

Abdullah Musa April 25, 2025