WSL Reaches 1.0 as a Standalone Microsoft Store App

On November 22, 2022, Microsoft announced that the Windows Subsystem for Linux, distributed through the Microsoft Store, had reached version 1.0 and general availability — dropping its “Preview” label and becoming available on both Windows 10 and Windows 11.

Why moving WSL to the Store mattered architecturally

Prior to this change, WSL’s core components were bundled into the Windows OS image itself, meaning WSL updates were tied to Windows’s own update and release cadence. Moving WSL to Microsoft Store distribution decoupled it from that cycle entirely — WSL improvements could now ship whenever they were ready, without waiting for the next major Windows feature update.

What version 1.0 specifically included

The 1.0 release bundled opt-in systemd support, the ability to run Linux GUI applications directly on Windows 10 (not just Windows 11, where WSLg had originally launched), and hundreds of smaller bug fixes and improvements accumulated through the preceding preview period.

How the Store version relates to the built-in version

Following this release, the Microsoft Store version became the default installation path for anyone running wsl --install, with existing users able to move to it via wsl --update — while a version of WSL still ships as part of the Windows OS image for compatibility, the Store version became the actively developed, recommended path going forward.

Why this represented the completion of a multi-year simplification arc

From WSL1’s original 2016 developer-preview reveal, through the single-command install introduced in 2021, to this final decoupling from Windows’s own release cycle, WSL’s distribution model consistently moved toward faster iteration and lower setup friction — this release effectively completed that particular arc, even as WSL’s underlying technical capabilities continued to expand afterward.

Why Windows 10 parity mattered as much as the version number itself

A significant part of this announcement’s practical impact was bringing Windows 10 users fully current with features that had, in some cases, been Windows-11-exclusive until this point — GUI application support via WSLg being the most visible example. This mattered because Windows 10 remained (and for years continued to remain) a substantial share of the installed Windows base, meaning a feature gap tied to Windows version specifically excluded a genuinely large population of potential WSL users, not a negligible edge case.

What “hundreds of smaller bug fixes” actually represented

Beyond the headline features, reaching 1.0 also meant the accumulated result of a lengthy preview period during which the Store-distributed WSL had been used and reported on by a self-selected population of more technically engaged early adopters — general availability extended that same accumulated stability and polish to the far larger population of users who wait for a “stable, non-preview” label before adopting new software, a genuinely different and more risk-averse user population than the preview channel’s early testers.

The practical mechanics of moving to the new version

Existing users on the older inbox WSL component could move to the Store version via wsl --update, without needing to reinstall or reconfigure their existing distributions — the underlying distro filesystems and their installed packages carried over, since the update affected the WSL platform layer itself rather than any individual distribution’s own content.

Reaching 1.0 didn’t mean the version number stopped moving

Dropping the Preview label at 1.0 didn’t freeze WSL’s release cadence — the Store-distributed package has continued shipping frequent, independently numbered releases in the years since, each tracked publicly through the microsoft/WSL GitHub repository’s own release history rather than tied to any Windows feature-update schedule. That public, incrementally versioned release process is itself a direct continuation of what decoupling from the Windows OS image was meant to enable in the first place.

Related:

Sources: