Microsoft Ships Coreutils for Windows, Putting Rust-Based Unix Command-Line Tools Natively on the OS

Overview

Microsoft has released Coreutils for Windows, a set of Unix-style command-line utilities that run natively on Windows rather than through a Linux compatibility layer. According to Microsoft Learn, the project is “a Microsoft-maintained set of UNIX-style command-line utilities that run natively on Windows — the same commands and pipelines you use on Linux, macOS, and WSL.” The utilities were announced at the company’s Build 2026 developer conference, and the first release was published on June 2, 2026, as reported by BleepingComputer.

The move gives Windows developers tools like ls, cp, grep, and find under their familiar Unix names without installing third-party ports or dropping into the Windows Subsystem for Linux. It also marks another step in Microsoft’s expanding use of Rust: the utilities are built on the same open-source reimplementation of GNU coreutils that already ships in modern Linux distributions.

What We Know

Coreutils for Windows is built on the uutils project. According to Microsoft Learn, “the utilities are implemented in Rust on top of the uutils/coreutils project — the same cross-platform reimplementation of GNU coreutils that ships in modern Linux distributions.” The Windows-focused build “bundles coreutils, findutils (find, xargs), and a GNU-compatible grep together as a single package,” the documentation states.

Rather than shipping dozens of separate executables, the tools are delivered as one program. Microsoft Learn describes the package as “a single multi-call binary that exposes each utility under its standard name (cat.exe, grep.exe, find.exe, and so on)”. BleepingComputer reports that Microsoft implemented this with a single coreutils.exe binary and NTFS hardlinks, so that invoking a command such as ls.exe or cp.exe points to the same executable, which then determines which utility to run based on the name it was called by. The first published release, tagged v2026.5.29 and titled “Our first release of Coreutils for Windows,” lists its contents as “The Rust rewrite of GNU Coreutils, uutils/coreutils,” “Their accompanying FindUtils implementation, uutils/findutils,” and “our newly written Grep implementation,” according to the GitHub release notes.

The stated goal is workflow portability. The documentation says the project aims “to remove friction when moving between Linux, macOS, WSL, containers, and Windows,” so that “the same commands, flags, and pipelines work the same way,” per Microsoft Learn. heise online quotes the project’s framing that “developers should be able to use the same commands, options, and shell pipelines on Windows, Linux, macOS, in the Windows Subsystem for Linux (WSL), and in containers.”

The package is open source under the MIT license and can be installed through Windows Package Manager. Both Microsoft Learn and the GitHub repository document the install command as winget install Microsoft.Coreutils. Each command supports the standard --help flag for syntax and options, according to Microsoft Learn.

Because many Unix command names collide with long-standing Windows built-ins, Microsoft built in compatibility measures. The GitHub release notes say the installer adds “a shim to ensure your existing DOS sort & find invocations continue to work” and “a PowerShell wrapper allowing you to use glob patterns the way you do on other OS”. Microsoft Learn explains that the package “includes integrated ports of the original DOS sort and find, so existing CMD scripts that rely on /switch-style syntax keep working alongside the UNIX-style versions,” according to Microsoft Learn.

Not every Unix utility made the cut. BleepingComputer reports that the included commands are “cat, cp, find, grep, hostname, ls, mv, pwd, rm, sleep, tee, and uptime,” among others, while commands such as dir, more, paste, and whoami were excluded because they conflict with existing Windows commands. The same outlet notes that utilities relying on POSIX-specific functionality — “chmod, chown, chroot, nohup, tty, and who” — were not released, and that kill and timeout were omitted because “Windows does not support POSIX signals.”

What We Don’t Know

Microsoft’s Build 2026 messaging presented Coreutils for Windows as a finished tool, but the GitHub repository still carries the line “This project is in preview,” and the initial release notes caution users to “expect some bugs in this first version.” How quickly the project will move past the preview label, and how aggressively Microsoft will expand the set of supported commands, is not yet detailed in the published materials.

Shell behavior also remains a practical caveat. The repository warns that “several commands share names with built-ins in CMD and PowerShell.” Whether the Coreutils version actually runs, it adds, “depends on the shell, the PATH order, and (for PowerShell) the alias table,” according to GitHub. heise online reports that PowerShell 7.4 is the minimum requirement for the tools.

Analysis

The release continues a broader migration of foundational command-line tooling to memory-safe Rust implementations. The uutils rewrite of GNU coreutils already underpins recent Linux distributions; Canonical, for instance, shipped Rust coreutils and sudo-rs by default in Ubuntu 26.04 LTS. Microsoft adopting the same upstream for a native Windows build means the two largest desktop ecosystems now lean on a common Rust codebase for their basic file and text utilities.

For Microsoft, Coreutils for Windows fits the developer-platform theme it pushed throughout Build 2026, where the company positioned Windows as a first-class home for cross-platform development. By reducing the gap between Windows shells and the Unix tooling developers use elsewhere, the project aims to keep scripts and muscle memory intact across operating systems — provided the preview-stage rough edges around shell conflicts and command coverage get smoothed out.