# Microsoft launches WSL Containers and tightens the race against Linux

> WSL Containers reached GA on September 29, 2026. Linux software runs on Windows 11 without Docker Desktop, with wslc, an API and enterprise controls.
> By José Maldonado · Technology · 2026-10-08

Nine days ago Microsoft moved a piece that had been on the board for years. Logan Iyer, corporate vice president of Windows Platform and Developer, announced on September 29, 2026, that [**WSL Containers**](https://blogs.windows.com/windowsdeveloper/2026/09/29/wsl-containers-now-generally-available/) is now a stable feature available to everyone, according to the official Windows Developer blog. As a result, anyone programming with containers no longer needs workarounds to run Linux software inside Windows 11, because the system ships its own container engine integrated into the Windows Subsystem for Linux.

Until now the usual path involved installing Docker Desktop or setting up a workflow with a WSL distribution and a separate daemon. That recipe worked, but it added a commercial layer and another resident program in exchange for something the system already half knew how to do. With this stable version, Windows 11 includes a client called wslc.exe with its container.exe alias, plus an API so Windows applications can use Linux containers as part of their logic. The announcement comes a week before October moves forward, and marks the moment when Linux inside Windows stops being a stopgap and becomes a platform.

The move has a business reading that should not be overlooked. The same version that simplifies life for the individual programmer adds Intune controls and Defender for Endpoint telemetry over the containers. Microsoft wants you to run Linux workloads on your Windows laptop without leaving your company's security framework. And it leaves on the table a promise that excites more than one, compatibility with compose files, which is still missing today.

## What changes with the arrival of WSL Containers?

The core novelty is simple to explain even if it sounds like plumbing. WSL Containers combines two pieces that did not previously exist as a closed product. On one hand, you have wslc.exe, a client with the commands you already know from other engines to build, start and inspect Linux containers. On the other hand, you have the WSL container API, distributed as a NuGet package so a Windows program can pull Linux containers through code, with networking, file mounts, GPU and input and output redirection.

To use it you need WSL version 2.9.3 or higher, and the update is obtained with the usual terminal command documented in the [official WSL containers guide](https://learn.microsoft.com/en-us/windows/wsl/wsl-container?tabs=csharp). Check your version with the version command before diving in, because older engine distributions do not expose the new client. Once updated, the classic test command starts an ephemeral Ubuntu that greets you and deletes itself.

The difference is important compared with the preview stage. During the months of testing, the community asked for visibility into what was running and tools to move files and networks without fighting the daemon. Microsoft responded with a list of additions covering the full container lifecycle. You can now restart a running container, copy files in and out via a tar, see the environment status at a glance and connect or disconnect containers from specific networks.

**[Security flaw: OpenAI swarms stalked databases](https://observatorioblockchain.com/en/cybersecurity/enjambres-openai-hackeando-bases-datos-marzo/)**

## Getting to know the new version

The list of additions sounds technical, but each command solves a daily pain. The changelog published alongside the [general availability announcement](https://blogs.windows.com/windowsdeveloper/2026/09/29/wsl-containers-now-generally-available/) details the additions that arrived from the preview to GA.

*   restart to restart a running container without recreating it
*   cp to copy files in and out via a tar
*   system info to see the environment status at a glance
*   network connect and disconnect to move containers between networks
*   events to follow container activity in real time
*   health checks and configurable stop times at creation

It is worth noting that two options raise the bar for serious uses. Support for mounts during creation and execution lets you bind host folders to the container from the first start. And the configurable storage path lets you move the default session data to the disk you prefer, something you will appreciate when images start eating your system drive.

Another important point is tolerance when scheduling stops. When creating or starting you can set a timeout for stopping, even infinite with the value minus one. It seems like a minor detail until a database migration process needs a few extra minutes to shut down with dignity.

## How to try it today on your machine?

The short path fits in an afternoon without surprises. Update WSL from PowerShell with the update command and confirm that the client responds to the built-in help. Then start an ephemeral Ubuntu container that prints a greeting, list the available images and bring up a test web server mapping port 8080. If opening localhost in your browser shows the welcome page, the whole pipe works.

```
wsl --update wslc run --rm -it ubuntu:latest bash -c "echo Hola desde WSL Containers" wslc image ls wslc run -it --rm -d -p 8080:80 --name web nginx wslc container ps wslc container stop web
```

The beauty of the container.exe alias is that your fingers barely notice the change. Anyone coming from other engines reuses gestures and flags without relearning anything, because the interface deliberately mimics the usual commands. And if you prefer programming to typing, the NuGet package exposes session, container and process objects with output events in C#. The C++ projection is still in preview and may break compatibility, so use it only for experimenting.

That means existing tutorials work almost unchanged. The official examples show how to check for missing components, create a session with four CPUs and four gigabytes, download an image with progress and read a process's output. Everything happens from your Windows application, with no intermediate windows or phantom services to watch.

**[Abstract, the blockchain from the creators of Pudgy Penguins, shuts down](https://observatorioblockchain.com/en/blockchain/abstract-blockchain-pudgy-penguins-cierra/)**

## Intune and Defender: the big win for enterprises?

The enterprise part is what turns a programmer's whim into a tool approved by security. The Microsoft Intune integration adds two master keys for administrators. The first lets them enable or disable the entire WSL containers feature on managed machines. The second defines a list of allowed registries, so developers only download images from approved sources that meet the organization's requirements.

The Defender for Endpoint add-on for WSL extends its gaze inside the containers. The sensor exposes process, file and network activity for each container and links it to the Windows host, so the security team investigates an incident without opening a separate console. The WSL enterprise documentation explains how to deploy these policies across a fleet, and the Intune dashboard already shows the feature-specific settings.

After all, this was the pending toll. No bank or government was going to bless Linux containers on Windows laptops without centralized governance. With GA, the happy programmer and the calm auditor sign the same page for the first time.

## The roadmap with compose and consomme networking

No stable version brings everything, and Microsoft openly acknowledges what is missing. The community's most voted request is compose support, and it will be the focus of the next iterations. The stated goal is for your current compose.yaml file to work without touching a line. The team says the work has already begun and promises news soon.

Area

Status in GA

What comes next

wslc client

Stable, with container.exe alias

Compose support with current files

API for apps

C Sharp stable, C Plus Plus in preview

Stabilize the native projection

Networking

Consomme mode for enterprises and home

General compatibility improvements

Cross files

Up to 2x in Windows file access

Keep cutting the bottleneck

Governance

Intune and Defender integrated

Harden registry controls

The second front looks at the foundations. The team is investigating networking and cross-system file performance improvements, and part of that work is already noticeable today. Access to Windows files from Linux environments reaches double its speed, which eases the classic bottleneck of compiling across systems. The new consomme networking mode improves compatibility in home and corporate scenarios with strict filters.

It should be remembered that these improvements benefit the entire ecosystem that lives on WSL. Classic distributions, the new containers and other technologies built on top share the same ground. Every point of speed gained in the basement shows up on every floor of the building.

**[Windows on ARM scales to Tier 1: what does it mean for your next laptop?](https://observatorioblockchain.com/en/technology/windows-arm-tier-1-proximo-portatil/)**

## Why does this feature change the role of Linux on Windows?

The ecosystem is already moving around the new engine. Visual Studio Code uses wslc as its development container driver, the containers extension manages it from the editor and Aspire treats it as a first-class runtime. The community contributes a text panel to govern them, a desktop application with lightweight Kubernetes and a wrapper to invoke the client from inside the distributions. All that in nine days says a lot about the hunger that existed.

The underlying reading is strategic and Microsoft writes it without concealment. Linux on Windows is evolving from a development environment into an execution platform for AI and cloud-native workloads, under the same security and governance frameworks as Windows. There is still a road to travel, with compose pending and networking to polish, but the direction is clear. If you program with Linux and live in Windows, this October 2026 is the time to update and try it.
