Installing WSL Goes From a Multi-Step Process to One Command
The wsl --install command, shipped via KB5004296 in mid-2021, collapsed WSL's previously multi-step manual setup process into a single line.
A real Linux kernel and userland running alongside Windows — architecture, integration, and daily use.
The wsl --install command, shipped via KB5004296 in mid-2021, collapsed WSL's previously multi-step manual setup process into a single line.
WSL dropped its Preview label in the Microsoft Store on November 22, 2022, decoupling its update cycle from Windows and letting improvements ship independently.
Microsoft and Canonical's September 2022 announcement closed one of WSL's longest-standing gaps: software expecting systemd as PID 1 finally worked.
Windows 11's October 5, 2021 launch made Linux compatibility via WSL2 part of the platform's core story, not an optional add-on developers had to seek out.
At Build 2019, Microsoft revealed WSL2, an entirely different architecture running a genuine Linux kernel inside a purpose-built lightweight virtual machine.
Announced at Build 2020 and previewed to Insiders in spring 2021, WSLg let a Linux GUI application's window appear on the Windows desktop like any native app.
WSL distros ran without systemd for years, breaking software expecting PID 1 init. Here is why that gap existed and how it was architecturally closed.
WSL's cross-OS file access translates between Linux and Windows filesystem semantics at the protocol level, and that translation has a real performance cost.
The specific GPU paravirtualization mechanism, built jointly by Microsoft and NVIDIA, that lets WSL2 run CUDA workloads at near-native performance.
WSL2's VM claims memory dynamically as Linux needs it and has historically been slow to release it back, plus what .wslconfig actually lets you control.