Tiny11 Builder gets a graphical interface and more control over Windows 11 customization

• Tiny11 Builder now has a WinUI 3 graphical interface that replaces the old script-driven workflow with a guided image-building process.
• The app offers Tiny11, Tiny11 Core, and Custom modes for different levels of removing Windows 11 components.
• The new version supports x64 and ARM64 images, including Windows 11 26H2, and adds progress tracking, saved configurations, and build-resume options.
• Tiny11 Core disables Windows Update and Microsoft Defender and removes recovery support, making it unsuitable for everyday computers.

Tiny11 Builder now has a graphical interface that makes it easier to create customized Windows 11 installation media without manually running PowerShell scripts. The new WinUI 3 app introduces a six-step wizard, three build modes, advanced remove options, and tools to monitor and resume image creation.

The application, currently at version 0.1.1 (available for download on GitHub), uses a separate C# image-building engine instead of wrapping or running the original Tiny11 PowerShell scripts. The existing scripts remain unchanged.

What the new Tiny11 Builder app does

The new tool replaces the script-driven workflow with a graphical interface for creating customized Windows 11 installation ISO files.

Users can download Microsoft’s latest publicly available Windows 11 ISO, select local installation media, choose an edition, configure the image, and review the changes before starting the build.

The wizard also provides detailed progress tracking, live logs, operation history, and the ability to cancel at safe boundaries. Users can save and restore recipes, resume eligible interrupted builds, and verify the resulting ISO with an SHA-256 hash.

Another addition is automatic detection of compatible Microsoft deployment tools, reducing the need to configure the image-building environment manually.

Tiny11, Tiny11 Core, and Custom modes

The application includes three build modes, each targeting a different level of customization.

• Tiny11 applies the original-style set of options to remove components, including bundled apps, Microsoft Edge and WebView2 binaries, OneDrive, and selected hardware-check and storage settings. It retains Windows Update, Microsoft Defender, Windows Recovery Environment (WinRE), Microsoft Store, and shared runtimes.
• Tiny11 Core removes additional Windows component-store files, removes WinRE, and disables Windows Update and Microsoft Defender Antivirus. These changes prevent normal future servicing, so this mode is intended for test virtual machines rather than everyday computers.
• Custom starts without removing any components. Users can choose individual groups or inspect preinstalled apps, system apps, optional features, language capabilities, packages, services, drivers, and WinSxS component folders.

Custom mode also provides disable-only options for supported features and services.

The presets follow the original scripts’ general approach but aren’t exact copies. For example, regular Tiny11 cleans superseded components without resetting the component base, preserving the ability to uninstall existing updates. Core uses a different process that makes removing components irreversible through normal servicing.

How the new app differs from the original scripts

The original Tiny11 project provides two primary PowerShell scripts, tiny11maker.ps1 and tiny11coremaker.ps1. These two scripts use Microsoft’s DISM (Deployment Image Servicing and Management) deployment tools to modify Windows installation images and create an ISO file.

Related

How to use DISM and SFC to fix problems on Windows 11

The regular script removes selected apps and components while preserving servicing capabilities. The Core script removes more components, including WinSxS payloads and WinRE, and disables Windows Update and Defender.

The new graphical version of the tool keeps these general approaches but adds a graphical workflow and more control.

The biggest difference is that the app implements its own image-building engine. It isn’t simply a graphical front end for the original scripts.

Compatibility and important limitations

The app accepts Windows 11 client images starting with build 22621, including 23H2, 24H2, 25H2, and 26H2, as well as newer preview builds. It supports x64 and ARM64 images.

Related

How to download Windows 11 26H2 ISO file for arm64 and Copilot+ PCs

However, accepting an image doesn’t guarantee that every combination of items to remove will produce a bootable installation. The developer says the implementation still needs virtual-machine validation across representative Windows releases and channels.

The application also requires administrator privileges, compatible Microsoft deployment tools, and an NTFS workspace with approximately 40GB to 90GB of free space.

The tool works on a separate copy of the installation image. It isn’t a live-system debloater, and it refuses to overwrite an existing output ISO.

Users can review the Tiny11 Builder project page for source code, packaging instructions, screenshots, and usage details.

Pureinfotech’s Take

The graphical interface is a welcome addition, but “Custom” mode is arguably the more important improvement. A fixed list of components that you can remove doesn’t work for everyone, and the ability to choose which components to keep or remove makes the tool more flexible.

I’d still be careful with Tiny11 Core. Removing recovery support, disabling security and update services, and preventing normal servicing are significant trade-offs. A smaller ISO doesn’t automatically make the operating system better, especially on a computer you depend on every day.