Microsoft has made WSL Containers generally available, letting developers build and run Linux containers directly on Windows through the Windows Subsystem for Linux, BleepingComputer reported Tuesday. The feature comes with a new command-line tool, an API for Windows applications and management hooks for Microsoft's security and device-management products.

What Happened

Users get the feature by running wsl --update, and Help Net Security said it is also available from Microsoft's GitHub releases page. Containers are managed with a new tool, wslc.exe, which also answers to the alias container.exe so developers can use familiar container-style commands. A WSL Containers API lets Windows applications start and communicate with Linux containers programmatically, which BleepingComputer said opens up scenarios such as local AI workloads.

The general availability release adds container restarts, copying files in and out, health checks, commands to connect and disconnect networks, real-time container events, mounts and configurable storage locations. VS Code Dev Containers, Aspire and the VS Code Containers extension can now use WSL Containers as their runtime. Microsoft says the feature offers up to twice as fast access to Windows files from Linux environments, though Help Net Security noted no testing details were given.

RelatedClaude Code Desktop Preview Flaw Could Have Exposed Developers’ Cloud Keys, Researchers Say

For administrators, Microsoft Defender for Endpoint's existing WSL plugin now covers containers, showing process, file and network activity inside them and linking it to the Windows host. Microsoft Intune gets two settings: one to switch WSL Containers off entirely and another to restrict developers to pulling images from approved registries.

Compose-style support, which would let teams run wsl compose up against existing compose.yaml files without changes, is still in development. Help Net Security reported that Microsoft calls it the top feature request for WSL Containers.

Why It Matters

Windows developers have long depended on third-party tools, most commonly Docker Desktop, to run Linux containers locally. A first-party runtime built into WSL and delivered by a routine update removes a separate install and, for many organizations, a separate licensing and support decision.

The enterprise controls may matter more than the command-line tool. Containers running on developer laptops have been hard for security teams to see into, and an unapproved image pulled from a public registry is a common way for malicious code to reach a workstation. Tying container activity to Defender telemetry and letting Intune enforce registry allowlists brings those laptops under the same policies that already govern the rest of a managed Windows fleet.

Limits and Open Questions

The missing Compose support is a practical barrier. Many development teams describe multi-container setups, such as an app with its database and cache, in compose files, and they will need that workflow before moving off existing tools. BleepingComputer's report did not say which Windows versions are supported, and Microsoft has not published benchmark details for the file-access claim.

What to Watch

The release of Compose support is the most likely trigger for broader adoption. Enterprises will also be weighing whether to standardize on WSL Containers, keep Docker Desktop or run both, and how quickly Microsoft adds features that existing tools already offer. Uptake by the VS Code and Aspire communities will be an early indicator of whether developers treat it as a default.