{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicn2a2abl7xcw65g37m53qi2rsglwkxrxqvx5wpcp66es644jfwne",
    "uri": "at://did:plc:i3hyx5sw7cz7ofijrwp4tqua/app.bsky.feed.post/3mnkowvqm74k2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreid4jsrnwqui3fx3iyufoku2xnrsi2p4pd6cktwhtpvncrrxkx3xfy"
    },
    "mimeType": "image/png",
    "size": 345318
  },
  "description": "Is this a \"Linux-ification\" of Windows? Not quite. It's more of a pragmatic bridge.",
  "path": "/en/microsoft-brings-linux-style-coreutils-natively-to-windows/",
  "publishedAt": "2026-06-05T17:45:14.000Z",
  "site": "https://www.sredevops.org",
  "tags": [
    "Microsoft Build 2026",
    "uutils",
    "Microsoft GitHub repository",
    "Bobby Borisov via Linuxiac",
    "uutils/coreutils Project",
    "Microsoft Build 2026 Announcements"
  ],
  "textContent": "Is this a \"Linux-ification\" of Windows? Not quite. It's more of a pragmatic bridge.\n\nCoreutils for Windows won't make you forget you're on Windows, and it won't replace the need for a full WSL instance when you're doing heavy-duty Linux systems engineering. However, for the developer who just wants to `grep` a log file or `find` a config without fighting the shell, it is a massive quality-of-life improvement.\n\nFor years, the relationship between Microsoft and the Linux ecosystem was one of mutual suspicion and occasional hostility. Fast forward to 2026, and the irony is palpable: Microsoft is now officially shipping Unix-style utilities to make Windows feel a little more like the environments developers actually live in.\n\nAnnounced at Microsoft Build 2026, **Coreutils for Windows** is a new, Microsoft-maintained suite of command-line tools designed to run natively on Windows. No WSL required, no heavy virtualization layers—just your familiar commands, running directly on the Windows kernel.\n\n## The Rust-powered foundation\n\nRather than attempting a messy port of aging GNU C code, Microsoft has gone the modern route. Coreutils for Windows is built upon uutils, a cross-platform, high-performance reimplementation of GNU Coreutils written in **Rust**.\n\nBy leveraging Rust, Microsoft is tapping into the language's inherent memory safety and concurrency strengths, which is a smart move for system-level utilities. The package is distributed as a single, multi-call binary and includes Microsoft-maintained builds of:\n\n  * `uutils/coreutils`\n  * `uutils/findutils`\n  * A specialized Microsoft fork of `uutils/grep`\n\n\n\nThe goal is to reduce the \"context-switching tax\" paid by DevOps engineers and SREs who bounce between local Windows workstations, macOS laptops, and Linux-based cloud environments.\n\n## Installation and setup\n\nGetting started is straightforward, assuming you aren't still clinging to the legacy CMD prompt. The package is distributed via **WinGet** , making it easy to integrate into automated setup scripts or developer onboarding workflows.\n\n\n    # Install the coreutils package via WinGet\n    winget install Microsoft.Coreutils\n\n\n_**Note:** To get the most out of this, you will need **PowerShell 7.4 or later**. If you are still running Windows PowerShell 5.1, you might want to upgrade before you start expecting modern behavior._\n\n## The \"curated\" experience: Limitations and conflicts\n\nBefore you go rewriting all your `.bat` scripts, let's manage some expectations. This is not a complete, 1:1 replacement for a Linux distribution. It is a \"Windows-focused subset.\"\n\n### Command conflicts and aliases\n\nBecause Windows has its own way of doing things, several common commands will collide with existing PowerShell or CMD built-ins and aliases. If you try to use `ls`, `cat`, `cp`, `mv`, `rm`, or `pwd`, you might find yourself in a tug-of-war between the native Windows behavior and the new Coreutils implementation. You'll need to be mindful of your environment's execution policy and alias precedence.\n\n### What's missing?\n\nMicrosoft has been quite selective about what they include. While the \"essentials\" are there, many power-user tools have been left on the cutting room floor.\n\n**Explicitly excluded utilities:**\n\n  * `dd` (Because direct disk manipulation on Windows is a recipe for disaster)\n  * `dircolors`\n  * `shred`\n  * `sync`\n  * `uname`\n\n\n\n**Missing POSIX-specific tools:**\nIf your workflow relies heavily on permission management or process inspection, you'll notice the absence of `chmod`, `chown`, `chroot`, `mkfifo`, `tty`, `users`, and `who`. Attempting to map POSIX permissions to the NTFS filesystem is a complex beast, and it seems Microsoft has decided to punt that particular headache for another day.\n\n## The bigger picture: WSL containers\n\nThe release of Coreutils for Windows isn't happening in a vacuum. Alongside this, Microsoft introduced **WSL containers**.\n\nWhile Coreutils aims to make the Windows CLI more familiar, WSL containers aim to make Linux containerization more native. Unlike the Coreutils package, WSL containers are currently in the works and are expected to enter public preview in the coming months. They promise a way to build and run Linux containers through a dedicated CLI and API, providing enterprises with policy-based control over image sources and host interaction—essentially bringing the \"managed\" feel of cloud-native environments to the local Windows desktop.\n\nCoreutils for Windows is available now via the Microsoft GitHub repository\n\n* * *\n\n**References & Credits:**\n\n  * Original reporting by Bobby Borisov via Linuxiac\n  * uutils/coreutils Project\n  * Microsoft Build 2026 Announcements\n\n",
  "title": "Microsoft brings Linux-style coreutils natively to Windows",
  "updatedAt": "2026-06-05T17:45:15.922Z"
}