Skip to main content

Operations

Workflow (manual, NTLite-driven)​

WinTrim doesn't have a build script in the conventional sense — the workflow is: load a base Windows 11 ISO and a preset XML into NTLite, apply the preset, and produce a trimmed ISO. The presets and removal manifest in this repo are the actual artifacts of that process.

Repository layout​

WinTrim/
├── Win11_25H2_English_x64.iso     <-- base image (checked in, ~7.7GB)
├── COMPONENTS_REMOVED.md            <-- detailed removal rationale (~74KB)
├── RemovalManifest_Annotated.xml    <-- machine-readable removal manifest
├── DOCUMENTATION_ARCHITECTURE.md
├── PHASE1_CLEANUP_SUMMARY.md
├── Configs/
│   ├── Base_v1.0.0.xml, Current.xml, Herbs-Win11.xml, ...  <-- NTLite presets (iterative)
│   ├── BaseMin_v1.4.2.iso, Base_v1.5.0.iso, Base_v2.1.0.iso  <-- trimmed image outputs
│   ├── winget-export-*.json / *.ps1  <-- package export snapshots + install scripts
│   └── collection.ps1 / safety.ps1 / tools.ps1 / base_apps.ps1
└── Machine/
    ├── my-machine.dsc.json           <-- DSC machine configuration
    ├── NTLite/
    └── Winget/

Safety notes​

Presets explicitly document removal risk and re-add instructions per component — a preset isn't just "here's what to remove," it's paired with "here's what breaks and how to fix it if you need this component back." Review COMPONENTS_REMOVED.md before applying any preset to a machine that matters.