What is the Windows Subsystem for Linux (WSL)?

Operating system (OS) virtualisation can achieve incredible things. By abstracting the hardware layer, virtualisation makes the operating system believe that it is running natively on hardware, when in fact it is housed inside another operating system.

This opens up a world of possibilities. With virtualisation, for example, you can run more than one fully functional operating system on a single machine, or one that differs from the host operating system, such as Windows on a Linux system, or the other way round.

This is exactly what Microsoft did with the Windows Subsystem for Linux (WSL), which lets you run the Linux kernel, file system and graphical Linux applications on a Windows 10 or Windows 11 computer. On 19 May 2025, Microsoft made WSL open source: the code is available on GitHub, and anyone can contribute to its development. (The WSL 2 kernel and WSLg, which serves graphical applications, were already open before; the lxcore.sys driver that powers WSL 1 and the components that handle \\wsl.localhost access remain closed for now.)

How does the Windows Subsystem for Linux work?

The Windows Subsystem for Linux (WSL) is a collection of Microsoft components designed to run native 64-bit Linux ELF64 (Executable and Linkable Format) binaries on the Windows 10 or Windows 11 operating system.

It is an abstraction layer that lets Windows users install and run a Linux distribution smoothly on their Windows system, without dual booting or a separate virtual machine.

Today the whole installation can be done with a single command: running wsl --install in PowerShell opened as administrator turns on the required Windows features and installs the Ubuntu distribution by default (this can be changed with the -d option). Newly installed distributions run with WSL 2 by default.

The original architecture (WSL 1) consists of a user-mode session manager service, minimised processes called Pico processes that run the Linux processes, and Pico drivers (lxcore.sys) that emulate the Linux kernel. This design routes Linux system calls to the Windows kernel, which serves them. WSL 2, on the other hand, runs a real Linux kernel (more on this below).

After installation, users can install and run programs from the Ubuntu package repository, use Linux command-line utilities (such as grep), navigate the Linux file system and run shell scripts.

Who is the Windows Subsystem for Linux for?

The primary users of the Windows Subsystem for Linux are developers who work in a Windows environment and also use Linux. For example, web developers who often use Linux and other open source tools, such as those from GitHub, but have only limited access to full Linux systems for development and experimentation. Use cases include:

  • Development: WSL lets developers use familiar Linux tools and programming languages, such as Ruby and Python, inside Windows. They can run Linux-based development environments, such as Docker and Kubernetes.
  • Server management: with WSL, you can manage Linux servers. This is useful if you are a sysadmin, or if you need to manage a Linux server from a Windows computer. With WSL, you can manage servers with the Linux tools and applications you are used to, without a remote desktop connection.
  • Education: learning Linux is another great use for WSL, since you can learn about Linux without having to install a separate Linux operating system. In WSL, you can follow Linux tutorials and documentation and set up a Linux development environment.
  • Productivity: anyone familiar with Linux environments can improve their workflows with a WSL instance, since they can use familiar Linux tools and applications on their Windows computer too, saving time and energy.

These uses are partly down to how easy the Windows Subsystem for Linux is to install, but the tight integration with Windows also helps a lot.

WSL 1 vs. WSL 2

Microsoft offers two different versions of the Windows Subsystem for Linux: WSL 1 and the newer WSL 2. Both provide tight integration between Windows and Linux, need few resources and start quickly. According to Microsoft’s comparison, however, there is a difference in how they work with other vendors’ hypervisors: WSL 1 works with current versions of VMware and VirtualBox, while WSL 2 works with VMware 15.5.5 and later, but is not supported with VirtualBox because of significant limitations.

The primary difference between WSL 1 and WSL 2 is that the latter runs inside a managed virtual machine (VM). Since the VM is managed by the system, IT staff do not have to deal with the configuration and operations tasks that usually come with virtual machines.

Another important difference is that WSL 2 uses a full Linux kernel. Microsoft builds this kernel from the latest stable branch on kernel.org, tuned for WSL, and its source code is open. Updates are shipped by Microsoft: WSL is now updated as a separate package distributed through the Microsoft Store, so there is no need to wait for the next Windows update, and it can also be updated manually with the wsl --update command.

Microsoft recommends using WSL 2 because of its better performance compared with WSL 1 and its 100% system call compatibility. WSL 1 can be the better choice if the project files have to be stored on the Windows file system, or if you work on the same files with both Windows and Linux tools (for example, when cross-compiling), because file access between the two systems is faster in WSL 1.

Why use WSL instead of Linux in a VM?

While Linux instances can also run inside a VM on Windows, WSL offers two advantages. First, it needs fewer computing resources – processor, memory and storage – than a full VM. Second, WSL lets Windows and Linux environments run at the same time, so developers can use Windows applications and Linux utilities on the same files when needed.

WSL 2 (thanks to the WSLg component) has made it possible for graphical Linux applications to behave like native Windows applications. Users can launch them directly from the Windows Start menu, pin them to the taskbar and switch between them with Alt+Tab. The clipboard is shared too: cut and paste works between Windows and Linux applications. WSL 2 now also supports systemd, and version 2.0 brought mirrored networking mode and DNS tunnelling, among other things.

Benefits and limitations of WSL

One of the main benefits of using WSL is that Linux applications can be run simply on a Windows PC, without a separate virtualisation application. Another benefit is that it supports several Linux distributions, such as Ubuntu, openSUSE, Kali, Arch Linux and Debian, even side by side.

Microsoft also fully supports WSL on Windows 10 (version 2004 or later) and Windows 11. So if a problem comes up while using WSL, you can rely on Microsoft’s documentation and support to solve it. It is important to note, however, that general support for Windows 10 ended on 14 October 2025, so it is best to use WSL on Windows 11 by now.

WSL does have certain limitations, though. WSL 1 is not a full Linux environment but a compatibility layer that runs Linux binaries on Windows, so not every Linux feature is available in it. WSL 2 does run a real Linux kernel, but its hardware access is limited: it does not support serial ports, for example, and USB devices can only be attached with USBIPD-WIN, which has to be installed separately. WSL 2 distributions are stored on a virtual disk with an ext4 file system, and with the wsl --mount command physical ext4 disks can also be mounted. Not every distribution is available in the Microsoft Store, but any distribution can be imported from a TAR file.

In addition, WSL is not always as fast as a native Linux installation. In WSL 1, Linux system calls have to be translated into Windows system calls, which adds overhead. WSL 2 runs a real kernel in a lightweight virtual machine; here it is mainly file access between the two operating systems’ file systems that is slower, which you can avoid by storing the project files on the same system whose tools you work with.

One of the most important Windows features?

Overall, there are plenty of development environments that would benefit greatly from WSL, along with many other use cases. There are limitations too, though. Will the Windows Subsystem for Linux work for you? That depends on your own use cases. If you would like to try WSL, follow Microsoft’s simple guide.

Let’s talk about your project

Tell us briefly how we can help, and we will get back to you as soon as we can.

Get in touch