openskills.info
Windows Subsystem for Linux logoCourse Preview

Windows Subsystem for Linux

Windows Subsystem for Linux (WSL) runs Linux distributions and their command-line or graphical applications alongside Windows. It gives Windows users a Linux filesystem and tool environment without a separately managed traditional virtual machine or a dual-boot setup.

itWindows and Microsoft infrastructure

Windows Subsystem for Linux

Windows Subsystem for Linux (WSL) runs Linux distributions beside Windows applications on one Windows machine. A distribution supplies the Linux user space: its shell, package manager, libraries, tools, services, and filesystem. Windows supplies the WSL host integration and, with WSL 2, manages a utility virtual machine containing a Microsoft-built Linux kernel.

WSL is useful when Windows remains the desktop operating system but development, automation, administration, or data tools expect Linux. It removes the need to maintain a conventional general-purpose virtual machine for many local workflows. It does not turn Windows into Linux, and it does not reproduce a remote production host in every detail.

Architecture and execution flow

The Windows-side wsl.exe command installs, starts, selects, updates, exports, imports, and stops distributions. Starting a distribution creates or resumes its Linux environment, then launches the requested Linux process. The process uses the distribution's packages and filesystem while WSL connects terminal input, files, networking, graphics, and process invocation across the Windows–Linux boundary.

WSL supports two architectures:

  • WSL 1 translates Linux system calls through a Windows compatibility layer. It has no managed Linux virtual machine and provides fast access to files stored on Windows, but it does not provide full Linux system-call compatibility.
  • WSL 2 runs distributions as isolated containers inside a managed utility virtual machine with a real Linux kernel. It provides full system-call compatibility, supports systemd and Linux GUI applications, and is the default for new distributions.

The architecture is chosen per distribution. WSL 1 and WSL 2 distributions can coexist, and a distribution can be converted between them. WSL 2 is the usual choice. WSL 1 remains relevant when a workflow must repeatedly access project files stored on the Windows filesystem or when virtualization constraints prevent WSL 2.

Continue the course

This section is part of the paid course.

See pricing to subscribe, or log in if you already have access.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources