Skip to main content

WinTrim Overview

WinTrim is a Windows trimming and configuration toolkit built around NTLite — it maintains presets, annotated removal manifests, machine profiles (DSC/winget), unattend XMLs, and PowerShell/winget scripts to produce debloated Windows 11 images and their post-install configuration.

:::note This project is mostly artifacts, not code Unlike most DRS projects here, WinTrim's substance isn't source code — it's a large, carefully annotated collection of NTLite preset XMLs, a removal manifest documenting exactly what each removed component breaks and how to re-add it, and machine configuration files. The repository even includes a full base Win11_25H2_English_x64.iso alongside multiple in-progress preset ISOs (BaseMin_v1.4.2.iso, Base_v1.5.0.iso, Base_v2.1.0.iso) — this is a working image-trimming project, not a documentation exercise. :::

Who it's for​

Herb, directly — building customized, debloated Windows 11 images for operator-managed machines. This isn't packaged for other operators; it's personal infrastructure tooling with unusually thorough documentation of why each removal decision was made.

The core concept​

Win11_25H2_English_x64.iso  (base image, checked in)
        │
        ▼  NTLite + hand-authored presets (Configs/*.xml)
Trimmed image (BaseMin, Base_v1.5.0, Base_v2.1.0, ... — multiple iterations)
        │
        ▼  paired with
RemovalManifest_Annotated.xml  <-- documents what each removal breaks + re-add steps
Machine/*.dsc.json, Machine/Winget/*  <-- post-install configuration

Several preset iterations exist side by side (Base_v1.0.0.xml, Current.xml, 6-1-26.xml, Herbs-Win11.xml, and more) — this reads as active, iterative experimentation rather than a single finalized preset, consistent with its Planning/40% status despite operational_completeness = 75% (the underlying NTLite/removal work is well ahead of the DRS release paperwork).

Why this shape​

Trimming a Windows image is inherently risky — remove the wrong component and something breaks in a way that's hard to diagnose later. COMPONENTS_REMOVED.md (74KB) and the annotated removal manifest exist specifically to make every removal decision traceable and reversible, which is the same safety-first instinct seen in AptDiskwright: don't just do the risky thing, document exactly what it does and how to undo it.