wingetCollections
  • Auto
  • Search
  • Awesome Collections
  • Awesome Programs
  • My Favorite Collections
  • My Collections
  • Account / Settings
  • Terms of Service
  • Privacy
  • About

© 2026 winget.ragerworks.com

Loading...
Install Coreutils for Windows using Winget - wingetCollections
  1. Go back
  2. Packages
  3. Coreutils for Windows
Coreutils for Windows logo

Coreutils for Windows Microsoft Corporation

command-line-tool coreutils gnu-coreutils
Use this command to install Coreutils for Windows:
winget install --id=Microsoft.Coreutils -e

Coreutils for Windows is a suite of UNIX-style command-line utilities designed to bring familiar Linux, macOS, and WSL tools natively to Windows. It enables users to execute the same commands, flags, and pipelines they use on POSIX systems directly on Windows, fostering consistency across environments.

Key Features:

  • POSIX Compatibility: Implements core GNU Coreutils functionality for Windows, supporting standard flags and syntax.
  • Cross-Platform Consistency: Ensures scripts written for Linux or macOS work without modification on Windows.
  • Native Operation: Runs as a single multi-call binary with minimal overhead, avoiding the need for virtualization or emulation.
  • Integrated PowerShell Support: Enhances compatibility with interactive shells via PSReadLine integration.
  • Installable via winget: Easily install using winget install Microsoft.Coreutils.

Audience & Benefit: Ideal for developers, system administrators, and professionals working across Linux, macOS, WSL, and Windows. It eliminates the need to rewrite scripts or adjust workflows when switching environments, promoting efficiency and productivity in cross-platform development.

README

Coreutils for Windows

UNIX-style core utilities for Windows. The same commands and pipelines you use on Linux, macOS, and WSL - natively.

Install · Shell conflicts · Windows caveats · Contributing

A Microsoft-maintained build of uutils/coreutils, findutils, and grep packaged as a single multi-call binary for Windows. The goal is to make moving between Linux, macOS, WSL, containers, and Windows frictionless: the same commands, flags, and pipelines work the same way, so existing scripts carry over without translation.

Each command supports the standard --help flag for full syntax and options.

This project is in preview.

Install

Install Coreutils for Windows with WinGet:

winget install Microsoft.Coreutils

Or grab the latest build from our Release Page.

Creating custom alias

  • PowerShell: Set-Alias ll 'ls' or a function in your $PROFILE for arguments, e.g. function ll { ls -la --color=auto @args }
  • CMD: doskey ll=ls -la $*

> [!WARNING] > Using PowerShell aliases will cause binary stream compatibility. Some utilities will not work when piped (e.g. xargs, find, ...)

Shell conflicts

> [!NOTE] > Any command not mentioned is included in this suite. The following only lists conflicts.

> [!NOTE] > You can remove additional utilities using coreutils-manager disable . > See coreutils-manager --help for other management commands.

> [!WARNING] > PowerShell 7.4 or later is required. > PowerShell 7.6 or later is recommended for ~ support.

Several commands share names with built-ins in CMD and PowerShell. Whether the Coreutils version runs depends on the shell, the PATH order, and (for PowerShell) the alias table.

Legend: ✅ ships and works · ⚠️ ships but conflicts with a built-in · 🛑 not shipped

Versions
2026.6.16
2026.5.29
Website
github.com
License
Last updated
6/20/2026
Download latest version
CommandCMDPowerShell 7.4+Notes
cat✅⚠️
cp✅⚠️
date⚠️⚠️
dir🛑🛑Conflicts with the built-in DOS command
echo⚠️⚠️
expand🛑🛑Conflicts with the built-in DOS command
find✅✅Integrated port of the original DOS command
hostname✅✅Superset of the Windows built-in
kill🛑🛑Unavailable due to lack of signals on Windows; Implementing a form of SIGTERM/SIGKILL may be possible in the future however
ls✅⚠️
mkdir⚠️⚠️
more🛑🛑Conflicts with the built-in DOS command (consider edit as an alternative)
mv✅⚠️
pwd✅⚠️
rm✅⚠️
rmdir⚠️⚠️
sleep✅⚠️
sort✅⚠️Integrated port of the original DOS command
tee✅⚠️
timeout🛑🛑Relies on kill's functionality
uptime✅⚠️
whoami🛑🛑Conflicts with the built-in Windows command

Windows caveats

DifferenceDetail
CRLF line endingsWindows text files often use CRLF (\r\n). Most utilities handle this transparently, but byte-oriented behavior can still observe the \r; for example, uniq may treat the final line as different from a preceding duplicate if the input uses CRLF and the final line has no trailing newline.
No /dev/nullUse NUL instead, for example find . -name "*.log" > NUL
No POSIX signalsSignals such as SIGHUP, SIGPIPE, and SIGUSR aren't available. Ctrl+C (SIGINT) works as expected.
Path separatorsBoth / and \ are accepted. Some utilities produce \-separated output, which can affect downstream piping.
File permissionsWindows uses ACLs, not POSIX permission bits. Permission-based predicates (for example find -perm) may behave differently or be unavailable.
Symbolic linksReading existing symbolic links works without elevation. Creating new symbolic links requires Developer Mode (Settings > System > Advanced) or an elevated terminal.

PowerShell Command Parsing

The installer integrates itself with interactive PowerShell sessions via PSReadLine. It ensures that quoted expressions behave somewhat like they do under UNIX shells or CMD: echo *.txt will then print a number of file names, while echo '*.txt' will print "*.txt" literally.

There are two shortcomings, however:

  • PowerShell's escape character is still `, not \ While you may write find . \( -foo -bar \) with Bash, you still need to write find . `( -foo -bar `) in PowerShell.
  • The integration rewrites interactive input, but it does not remove PowerShell's aliases Get-Command ls, Get-Help ls, etc., will still show ls, etc., as PowerShell built-ins or aliases. Due to limitations around PSNativeCommandPreserveBytePipe we cannot integrate ourselves in a more robust way with PowerShell.

Intentionally dropped

Commands that exist upstream but aren't shipped here because they rely on POSIX-only concepts, would break existing Windows scripts, or simply aren't useful on Windows.

  • dd: Perhaps useful in the future.
  • dircolors, shred, sync, uname: Not particularly useful on Windows.
  • chcon, chgrp, chmod, chown, chroot, groups, hostid, id, install, logname, mkfifo, mknod, nice, nohup, pinky, runcon, stdbuf, stty, tty, users, who: POSIX-only concepts unavailable on Windows.

Contributing

Bug reports and pull requests are welcome. See CONTRIBUTING.md for details on the repo layout and how changes flow between this repo and the upstream uutils projects.