A desktop monitor displays a Windows setup interface with app icons, a progress bar, and security checks.
Tiny11 Builder 0.2.0 arrived on October 30, 2026. It is the first big update to NTDEV's WinUI-based Windows 11 image builder since the redesign earlier this month. The headline additions are offline update integration and portable Custom recipes. The release also fixes several build failures that could derail an ISO run.

A desktop monitor displays a Windows setup interface with app icons, a progress bar, and security checks. What the tool does, and what it doesn't​

Tiny11 Builder doesn't touch the Windows install you're running. It takes Windows 11 installation media and produces a new, slimmer ISO. The 0.2.0 release was published on GitHub on October 30 under the tag winui-v0.2.0. Neowin notes that the app can download official Windows 11 images from Microsoft, and it also accepts your own ISO. Because it builds a new image, you have to rebuild from original media to get any of these changes. Nothing is patched in place.

The tool offers three modes:

  • Tiny11: Removes unnecessary bundled apps and selected components but keeps Windows Update, Microsoft Defender, Windows Recovery Environment and the Microsoft Store.
  • Tiny11 Core: More aggressive. It removes more components and disables security and recovery features. The project positions it for disposable test VMs. Core can't be updated or serviced.
  • Custom: You choose what goes, either by hand or by loading a recipe.

The release notes say the Tiny11 and Core preset selections are unchanged in this release. If you liked the presets before, nothing about them has shifted.

Offline updates before removals​

This is the most practical addition. You can now feed the builder local CAB or MSU packages. They are integrated in prerequisite order before removals run, privately staged and hash-checked. Pending servicing stays visible in reports and protects files needed at first boot.

Why does the order matter? Update packages often expect certain components to be present. Applying them before stripping the image avoids servicing conflicts. It also lets you bake in a current cumulative update so the first boot isn't a patching marathon. Pending servicing can still exist, though. The tool surfaces it rather than hiding it.

The workspace-space preflight also changed. For a new build it now estimates twice the source ISO's file size, plus any selected update staging. That replaces the older, much larger expanded-image estimate. It's a check, not a guarantee, so leave headroom.

Portable Custom recipes and finer removals​

Custom mode can load a JSON recipe. Imported groups show up checked. When a recipe leaves its paths blank, your own ISO, edition, workspace and output choices are kept. That makes recipes shareable without dragging the author's folder layout along. If you change the source image, your removal selections stay.

Custom also gets deeper inspection of individual files, driver packages, fonts, resources and payload folders. Six Custom-only groups cover:

  1. 32-bit support
  2. Desktop .NET
  3. Input method editors
  4. Speech and OCR
  5. Printer and scanner drivers
  6. Bundled media

Custom can also rebuild the source boot.wim as a single maximum-compressed Setup index. It stays bootable and keeps Setup and native drivers.

The "extreme" recipe​

A bundled recipe, recipes/cd700-custom.json, ships with 37 checked removal groups and an optional 700,000,000-byte whole-ISO limit. It is a starting profile, not a prepared image and not a fourth build mode. The project's own materials say the CD-size target is optional and not guaranteed for every Windows image. Treat it as an experiment.

You can also now inspect the full read-only Tiny11 and Core removal plans. You can export the complete component inventory to UTF-8 text, regardless of filters or selections. That is handy for auditing exactly what a preset will remove.

Fixes worth knowing about​

  • The Core/legacy Setup "cannot read the ProductKey setting" failure is fixed. No product key is inserted to make that happen.
  • DISM now inherits required privileges correctly, including the disabled-privilege case tied to error 1314.
  • Detection of trusted Microsoft image tools covers catalog signatures, timestamped certificates and Windows Kits publishers. Unsigned or tampered tools are still rejected.
  • False final-image failures are gone when enablement releases report different build numbers, such as 22621 becoming 22631.
  • Guarded cleanup of stale Edge Update and WebView installed-program entries is extended for cases where the offline files are already gone.
  • Sidebar navigation and scrolling are improved, and accessibility labels are translated. The interface now ships in English and Simplified Chinese, with validated external JSON catalogs for other languages.

Getting started​

The repository's instructions are short. Download and extract the whole ZIP, picking x64 for Intel/AMD or ARM64 for Windows on ARM. Run Tiny11Builder.exe and approve the administrator prompt. Then pick or download an image, choose your mode and build. The app bundles its own .NET runtime. Image-tool problems point you to Microsoft's ADK page, where you install the Deployment Tools component and apply its servicing updates. Neowin lists the downloads at 90.3 MB for 64-bit and 87.9 MB for ARM64.

The project says Windows 11 images from 22H2 onward are supported. Insider and Canary builds may need compatible image tools, and Windows Server is not supported. Per the release material, the packages are unsigned.

Analysis: power tool, sharp edges​

The additions skew toward repeatability. Recipes, offline updates and inventory export suit people who build images more than once, such as lab admins, VM tinkerers and anyone maintaining a lean test image. That's a sensible direction for a project that began as a pile of PowerShell scripts.

The risks grow with the control. More granular removal means more ways to break something. The project's own documentation says acceptance of a build is not a certification that every build and custom removal combination boots. Removing IMEs, printer drivers or .NET pieces may be fine until the day you need them.

Two broader cautions apply. Neowin's feature list mentions bypassing TPM checks and removing Edge and OneDrive. That is a trade-off: it moves you outside Microsoft's supported configuration. Tiny11 Builder is an independent community project, not supported by Microsoft. Also, as one reviewer noted, standard Tiny11 keeps updates, so a feature update can reinstall apps and settings you removed. A debloated image isn't necessarily a permanently debloated system.

Practical advice​

  • Test every build in a virtual machine first, especially Custom builds with advanced removals.
  • Keep Tiny11 Core for disposable VMs. It disables Defender and can't be serviced.
  • Keep a copy of the original ISO and your recipe JSON so you can rebuild after changes.
  • Check the free-space preflight, then leave extra room if you stage large update packages.
  • Review the read-only removal plans and the inventory export before you commit to a build.

Bottom line: 0.2.0 is a solid maintenance-and-power-user release. It won't change what Tiny11 is, but it makes builds more reproducible and more flexible, and it removes several annoying failure modes.

 

References

  1. Tiny11 Builder 0.2.0 - Neowin Neowin 2026-10-30T16:50:01+00:00
  2. GitHub - ntdevlabs/tiny11builder: WinUI app for building smaller, customized Windows 11 images. · GitHub github.com
  3. Tiny11 Builder - Your slimmed-down Windows 11 ISO in a few clicks - Korben korben.info