"Developers constantly move between platforms, but familiar commands don't work consistently, forcing workarounds, lost speed and context switching," announced Microsoft.
What Microsoft announced at Build 2026
At its Build 2026 developer conference, Microsoft announced the release of Coreutils for Windows, a package that brings many commonly used Linux command-line utilities to Windows as native applications. The project is based on the open‑source uutils project, a cross‑platform reimplementation of the GNU coreutils written in Rust. Microsoft published Coreutils for Windows on GitHub as a Microsoft‑maintained package that combines uutils/coreutils, findutils, and a GNU‑compatible grep implementation into a single binary.
How Coreutils for Windows is packaged and installed
Microsoft opted for a single executable design: one coreutils.exe that contains the functionality of many individual commands. The installer creates NTFS hardlinks such as ls.exe, cp.exe, cat.exe, and rm.exe, all pointing to c:\Program Files\coreutils\coreutils.exe. Running fsutil hardlink list coreutils.exe shows dozens of command names — including cat.exe, cp.exe, cut.exe, base64.exe — all referencing the same file on disk. Microsoft provides a WinGet installation command: winget install Microsoft.Coreutils.
Which utilities are included — and which Microsoft withheld
Coreutils for Windows ships many familiar commands: cat, cp, find, grep, hostname, ls, mv, pwd, rm, sleep, tee, and uptime are among the utilities explicitly named by Microsoft. However, Microsoft intentionally left out several utilities that conflict with existing Windows commands — for example, dir, more, paste, and whoami are not shipped because they would collide with built‑in Command Prompt and PowerShell functionality.
Microsoft also did not release a number of Unix utilities that rely on POSIX semantics unavailable on Windows. Those include chmod, chown, chroot, nohup, tty, and who. The company further said it did not release kill or timeout, citing the lack of POSIX signal support in Windows, though Microsoft noted those commands may be possible in the future.
Microsoft cautioned that there may be differences between Linux behaviour and how commands operate on Windows due to line feed handling, file permission models, and overall POSIX support.
Compatibility behavior across shells and PATH
Microsoft published a compatibility table showing how each utility behaves in different Windows shells. Whether the Coreutils version of a command is executed depends on the shell in use, the order of directories in the system PATH, and the PowerShell alias table. In short, identical command names can map to different binaries or aliases depending on environment configuration, so users may not always see the Coreutils implementation unless PATH and aliases are arranged to prefer it.
What this means for developers, enterprise IT, and open‑source maintainers
- Developers: Microsoft framed the project around making existing commands and tools work across platforms so scripts can be used on Windows "without modification or other tools." For developers who move between Linux, macOS, Windows, and Windows Subsystem for Linux (WSL), Microsoft positions Coreutils for Windows as a way to reduce context switching and avoid workarounds.
- Enterprise IT and procurement: The single‑binary, hardlink approach and the interaction with PATH and PowerShell aliases mean IT teams must consider how Coreutils will coexist with built‑in Windows commands. Conflicts (for example, dir and whoami) were explicitly avoided by Microsoft, but administrators will still need to manage PATH ordering and alias tables to ensure predictable behaviour in scripts and automation.
- Open‑source maintainers and the uutils project: Microsoft’s release is explicitly based on the uutils open‑source work and is published as a Microsoft‑maintained package on GitHub that bundles multiple repos. That arrangement places Microsoft in a role as a distributor and maintainer for this combined package, while the upstream uutils work remains the technical foundation.
Bottom line
Coreutils for Windows is a pragmatic effort to bring a familiar toolbox to Windows users without shipping separate executables for every command. By combining uutils/coreutils, findutils, and a GNU‑style grep into a single coreutils.exe and exposing commands through NTFS hardlinks, Microsoft aims to let scripts travel across platforms more easily. The release was presented alongside other developer‑focused announcements at Build 2026 — notably WSL containers — as part of a broader push to make Windows more developer‑friendly. Still, Microsoft’s own warnings about line feeds, file permissions, POSIX gaps, and shell/PATH interactions make clear that the compatibility is not identical to Linux; some Unix behaviours and utilities remain unavailable today, and Microsoft explicitly left room to add features such as signal‑based commands in the future.
Original story: https://www.bleepingcomputer.com/news/microsoft/microsofts-coreutils-project-brings-linux-commands-to-windows/
