Microsoft today released public previews of two features that fundamentally change how developers can work with Linux on Windows: WSL Containers and Coreutils for Windows. The updates mean you can now build and run Linux containers without third-party software and use familiar Unix commands straight from the command line — no Linux distribution required.

What actually just landed

WSL Containers is a new built-in component of Windows Subsystem for Linux that ships as part of the WSL platform itself. It includes the wslc.exe command-line tool, which lets you pull images, start containers, mount folders, and inspect running workloads using familiar Docker-like syntax: wslc run, wslc build, wslc ps. Behind the scenes, wslc boots a lightweight virtual machine, starts containerd and dockerd, then talks to that Docker Engine instance over a Hyper-V socket. The result is a native container runtime that doesn't need Docker Desktop, Podman, or any other third-party stack.

Notably, the isolation model differs from what you’re used to. Each wslc session gets its own dedicated VM (with two vCPUs and 2 GB of RAM, configurable), so one misbehaving container session won’t starve another. That’s more granular than Docker Desktop’s shared-VM approach, though containers inside a session still share a kernel. Microsoft also ships an SDK as a NuGet package, letting Windows applications programmatically create and interact with Linux containers — a capability that lays groundwork for deeper IDE integrations.

The preview is live now, with general availability pencilled in for autumn 2026. Compose support isn’t included yet, but a feature request from the WSL product manager on GitHub suggests it’s a high-priority gap.

Alongside this, Microsoft released Coreutils for Windows — a package that installs real Unix commands like grep, find, cp, cat, and ls directly onto Windows. You grab it with a single winget command:

winget install Microsoft.Coreutils

Under the hood these are Rust-based ports from the uutils project (MIT-licensed, so they avoid the copyleft entanglements that once made Microsoft nervous). That’s the same codebase Ubuntu will adopt as its default coreutils starting with version 25.10. So, in a twist, Windows and Ubuntu are converging on identical userland tools from the same open-source foundation.

What it means for you

Developers are the obvious winners. If you write code that targets Linux servers, you can now pull images, test containers, and run build scripts without leaving Windows or installing Docker Desktop. The command line inside VSCode, Windows Terminal, or a CI script can stay consistent across macOS, Linux, and Windows. WSL Containers reimplements the Docker CLI interface so closely that most muscle memory transfers; wslc run -it ubuntu bash just works.

IT admins and platform teams get new enterprise controls. Group Policy can restrict which container registries images may be pulled from — a setting that’s enforced at the service boundary, so it covers the CLI, SDK, and any future plugins. Microsoft Defender for Endpoint’s WSL plugin now parses container events, though it currently requires a private preview sign-up. Intune dashboards aren’t ready yet, but the roadmap points toward a managed container experience. For now, if your developer workstations run Windows 11, you should start evaluating how WSL Containers fits into your endpoint hardening and container-image compliance policies.

Everyday Windows users who don’t write code may not notice much. Coreutils is handy if you dabble in scripting, but it’s not a replacement for WSL itself. The real Linux kernel, GUI app support (WSLg), and full POSIX system-call compatibility still live inside a WSL 2 distribution. Coreutils just gives you a few Unix tools without the overhead of a full Linux environment.

How we got here

The path from “Linux is a cancer” to shipping a real Linux kernel inside Windows is well documented, but a few milestones set the stage for today’s previews:

  • 2001–2010: Microsoft’s patent offensive and “Get the Facts” marketing campaign position Linux as a legal and cost risk.
  • 2014: CEO Satya Nadella tells the world “Microsoft ❤️ Linux.”
  • 2016: Windows Subsystem for Linux (WSL 1) debuts as a system-call translation layer.
  • 2018: Microsoft joins the Open Invention Network, opening 60,000 patents royalty-free to the Linux ecosystem.
  • 2019: WSL 2 introduces a full Linux kernel running in a lightweight VM, dramatically improving compatibility.
  • 2020–2025: WSLg enables Linux GUI apps; WSL becomes open-source; Azure Linux distro underpins much of Microsoft’s own cloud.
  • Build 2026: WSL Containers and Coreutils for Windows enter public preview.

Today’s releases are the natural extension of a decade-long strategic about-face: Windows no longer fights Linux — it hosts it as a first-class citizen.

What to do right now

Try WSL Containers
1. Ensure you have the latest Windows 11 preview build with WSL installed (wsl --install if you haven’t yet).
2. Open a terminal and run wslc --help to see available commands.
3. Pull a test image: wslc run -it alpine sh.
4. Explore the container API via NuGet if you build Windows applications.

Install Coreutils
1. Run winget install Microsoft.Coreutils.
2. Test a command: grep --version. It should return the Microsoft-build version string.

Fix the alias collision
PowerShell resolves its own aliases before searching PATH, so typing ls still runs Get-ChildItem. Microsoft’s documentation suggests adding a function to your $PROFILE that explicitly calls the Unix executable. For example:

function ls { Microsoft.PowerShell.Coreutils\ls.exe $args }

Repeat for cat, sort, echo, and any other command you want to redirect. CMD users get the Unix versions by default because CMD doesn’t have aliases, though watch out for clashes with legacy DOS commands like sort and find — Microsoft bundles both the DOS and Unix versions, so scripts that rely on /switch syntax won’t break.

Plan for enterprise rollout
If you manage developer workstations, start testing the Group Policy registry restriction (HKLM\Software\Policies\Microsoft\WSL\Container) and review how containers will sit alongside existing Docker Desktop deployments. Remember, wslc and Docker can coexist — they just shine in different scenarios.

Outlook

General availability is expected in late 2026, and the most requested feature — Compose support — is already tracked on GitHub. Microsoft is also working on deeper integration with VS Code, Dev Home, and Azure services, promising a smoother path from local container development to cloud deployment. For now, both WSL Containers and Coreutils for Windows are in preview, so expect occasional rough edges, but the direction is clear: Windows is becoming a Linux development platform in its own right, not just a host for a virtual machine.