Opinionated setups for Windows dev boxes. Idempotent. CI-tested.

Set up a new Windows dev box in minutes, not hours. Pick a setup, run one command, get back to building. Everything here is safe to re-run.

You want... Go to

A full dev workstation: tools, Windows settings, WSL, and terminal. One command, one restart. Windows Dev Config

A nicer WSL shell: zsh/bash, Starship, CLI tools, and a themed terminal profile. WSL Comfort

One language or toolchain. Workloads

Local AI: PyTorch for your GPU, plus Ollama, llama.cpp, or Foundry Local. AI tooling

🖥️ Windows Dev Config

Installs dev tools, applies opinionated Windows settings, and sets up WSL + Ubuntu — restart included. Nothing to clone, nothing to install first.

Open any PowerShell window — elevated or not — and run:

Dev tools: Windows Terminal, PowerShell 7, Git, GitHub CLI, GitHub Copilot CLI, VS Code, .NET SDK 10, Python 3.14 + uv, Node.js LTS + nvm, Coreutils for Windows, Windows App CLI, Oh My Posh, and PowerToys.

Terminal: PowerShell 7 as the default profile, Oh My Posh in your prompt, Cascadia Mono NF as the default font, and a GitHub Copilot profile in the dropdown.

Windows settings: Dark theme, long paths, File Explorer defaults, Start/Search settings, and Do Not Disturb

WSL: WSL platform + Ubuntu, including the restart and the automatic resume afterwards.

Full Experience

Everything from standard

Windows settings: Developer Mode, Sudo, widgets off, and Edge policies, additional Start/Search/System Tray settings

Remote Desktop: Enabled and firewall settings set

Standard Experience

irm https://aka.ms/devconfig/standard/setup.ps1 | iex

Full Experience

irm https://aka.ms/devconfig/full/setup.ps1 | iex

⚠️ Heads up — it may restart your PC. WSL needs virtualization turned on, so save your work first. Setup picks up where it left off after the reboot.

Every tool and setting, how to undo them, and troubleshooting: Windows Dev Config README.

Also known as Comfort Shell. A polished Windows + WSL shell setup — zsh/bash, Starship prompt, modern CLI tools, themed terminal.

irm https://aka.ms/devconfig/wsl-comfort/setup.ps1 | iex

Interactive by default — pick and choose components as it runs. For unattended installs, pass -NonInteractive:

& ([scriptblock]::Create((irm https://aka.ms/devconfig/wsl-comfort/setup.ps1))) -NonInteractive

Nothing to clone: it downloads the signed scripts, verifies them, and installs WSL first if it's missing. Already have a clone? .\wsl-comfort\install.ps1 works too. The Linux half (comfort-shell-bootstrap.sh) is standalone, so you can also copy it onto any Ubuntu host and run it directly.

Just want one toolchain? Each of these is a single command.

The winget configure will soon move to one-line style. Currently, to run them from a clone of this repo. What each one installs: Workloads.

Detects your GPU, installs the matching PyTorch build (CUDA, ROCm, Intel XPU, or CPU), and proves it works. Add a local model runtime if you want one.

Individual pieces (CUDA, ROCm, Intel AI, PyTorch, llama.cpp, Ollama, Foundry Local), hardware support, and options: AI tooling workloads.

"Unrecognized command: configure" Run winget configure --enable. If winget configure is still not recognized after that, Workloads/_common/assert-winget-configure.ps1 tells you whether App Installer is too old, policy has disabled configuration, or something else needs fixing.

The Visual C++ Redistributable is missing. Install it, then re-run:

x64:

winget install Microsoft.VCRedist.2015+.x64

ARM64:

winget install Microsoft.VCRedist.2015+.arm64

Workloads/_common/enable-winget-configure.ps1 installs it automatically as part of enabling winget configure.

Open a new terminal, or run the matching install.ps1 shim to refresh PATH in the current session.

A scheduled task resumes the run about 30 seconds after you sign back in and finishes the WSL setup. Nothing after a couple of minutes? Run the one-liner again — it's safe to re-run and skips everything already done. More detail in windows-dev-config/README.md.

Run the WSL Comfort one-liner from PowerShell on the Windows side instead. It installs WSL first.

WSL needs hardware virtualization available to the OS. Two common root causes:

On bare metal: virtualization (VT-x / AMD-V) is disabled in BIOS/UEFI. Reboot into firmware settings, enable it, save, and reboot back into Windows. The exact label varies by vendor — check your motherboard or laptop manufacturer's documentation if you can't find it.

Inside a VM: the host hasn't exposed nested virtualization to the guest. For a Hyper-V host, run this from an elevated PowerShell session on the host (with the guest VM powered off):

Set-VMProcessor -VMName <VM_NAME> -ExposeVirtualizationExtensions $true

Other hypervisors have their own equivalent settings — check your hypervisor's documentation.

Hit a bug, a stale doc, or a setup that fails on your machine? Open an issue at github.com/microsoft/WindowsDeveloperConfig/issues. Include your Windows build (winver), the exact command you ran, and the failing output. This helps us triage faster.

Contributions of all kinds are welcome: bug reports, doc fixes, new workloads, voice-and-tone tweaks. Start with CONTRIBUTING.md, then read src/docs/development.md for the CI matrix, the "how to add a language" walkthrough, and how the sign pipeline works.

Note on the repo layout: the src/ tree is the source of truth. The top-level windows-dev-config/, Workloads/, and wsl-comfort/ folders are Authenticode-signed release copies regenerated by the sign pipeline, so please don't edit them directly. Full details in src/docs/development.md.

The single source of truth for every flow (paths, build/run commands, ids, language metadata) is src/manifest.yml. The Command Palette extension, the CI harness, and the per-flow shims all read from it, so keep it in sync when you add or rename a flow.