A major update to the open-source Tiny11 Builder landed in September 2025, equipping the PowerShell tool with explicit removal routines for Copilot, the new Outlook client, and Microsoft Teams—three of the most persistently integrated cloud components in Windows 11—and rewriting the entire build pipeline into a single script that now leverages DISM’s recovery compression to produce dramatically smaller ISO images. The timing is deliberate: on October 14, 2025, Microsoft ends mainstream support for Windows 10, forcing millions of users to choose between an unsupported system, paid Extended Security Updates, or a jump to Windows 11. For those who must adopt the newer OS but want control over what ships on their PC, Tiny11 Builder’s refresh arrives as a pragmatic, if technically involved, middle ground.

NTDEV, the project’s maintainer, characterized the release as “a much more complete and flexible solution—one script fits all,” while acknowledging it as “a steppingstone for an even more fleshed-out solution.” The builder does not produce a pre-cooked, unofficial Windows variant. Instead, it ingests an official Microsoft Windows 11 ISO, services the offline image via DISM, surgically removes a long list of inbox apps and telemetry hooks, applies registry and policy tweaks to block forced Microsoft Account flows during OOBE, and then repacks the result into a bootable ISO compressed with the more aggressive LZX/LZMS algorithm. Because the tool works at the image level, any installed system starts clean—no post-install debloat scripts or manual uninstalls required.

Why Tiny11’s Approach Resonates as Windows 10 Support Ends

Windows 11 has accumulated a growing roster of inbox applications, cloud-first integrations, and AI-powered features that run by default on millions of desktops. For privacy-minded enthusiasts, administrators building deterministic images, and users running older hardware that barely meets Windows 11’s requirements, these additions translate into tangible friction: wasted disk space, background processes that consume CPU cycles and memory, telemetry streams, and persistent nudges to adopt Microsoft services. Community tools that modify the installer—rather than relying on reversible post-setup cleanup—have proven the most durable way to enforce a minimal base image, and Tiny11 remains one of the most prominent projects in that space.

At its core, the tool performs four deliberate steps. It mounts a Windows 11 WIM or ESD from official media, uses DISM to strip selected packages and components, writes configuration changes to the registry hive, and optionally injects an autounattend answer file to bypass the online-first setup that demands a Microsoft Account. The result is a customized installation that omits the targeted inbox apps, yet preserves Windows Update, defender definitions, and most servicing capabilities—provided the user chooses the standard tiny11maker path rather than the experimental Core variant.

What Changed in the September 2025 Refresh

NTDEV’s update modernizes three critical areas of the builder.

Single PowerShell Pipeline for x64 and Arm64

The previous tooling relied on a mix of batch files and PowerShell snippets that could behave unevenly across languages and architectures. The new release consolidates everything into one script, tiny11maker.ps1, with an experimental tiny11Coremaker.ps1 for extreme stripping. The pipeline now handles both x64 and Arm64 Windows images from the same code path, simplifying maintenance and improving reproducibility.

Explicit Removal of Copilot, New Outlook, and Teams

The refresh introduces targeted removal logic for Microsoft’s recent AI and mail integrations. Copilot—which ships as a deeply embedded sidebar and is increasingly difficult to excise through normal Settings toggles—can now be stripped at build time. The new Outlook client, which Microsoft has been aggressively pushing as a replacement for the classic Mail and Calendar apps, is also removed. Teams, the collaboration client that automatically reinstalls itself through store and servicing mechanisms, is explicitly targeted. Removing these components reduces the system’s surface area for cloud connectivity, background updates, and telemetry, and addresses one of the most common complaints from Windows 11 users who feel the OS forces services they never asked for.

Recovery/LZX Compression Slashes ISO Size

Tiny11 now applies DISM’s /Compress:recovery flag, which invokes the LZX/LZMS algorithms normally reserved for system recovery partitions. The trade-off is straightforward: more CPU time and memory usage during the image rebuild, in exchange for a substantially smaller final ISO. For users burning installation media onto USB drives with limited space, or keeping local images on low-capacity SSDs, this change directly reduces the footprint of the Windows distribution.

Proactive Blocking of Silent Reinstalls

The update includes registry tweaks and policy settings designed to prevent Windows Update or the Microsoft Store from quietly re-provisioning removed apps after the OS is installed. NTDEV acknowledges that this is “an ongoing battle”—Microsoft’s servicing pipeline and store mechanics evolve, and no mitigation can guarantee permanent blocking. Still, the inclusion of these measures reflects the community’s experience with components like Microsoft Edge, Outlook, and Dev Home reappearing after major updates.

Tiny11 Core: An Ultra-Compact, Non-Serviceable Option

For testbeds, virtual machines, and single-purpose appliances, tiny11Coremaker strips the image further by removing WinSxS and many servicing hooks. This aggressively reduces the on-disk footprint but deliberately breaks Windows Update and cumulative patching. NTDEV and community documentation explicitly warn against using Core images on any internet-facing or production machine.

The Full App Cull: What Tiny11 Removes

The exact removal roster varies slightly between builder versions and configuration flags, but the September 2025 refresh targets a broad set of inbox components commonly flagged as bloat:

  • Clipchamp, News, Weather, Xbox family apps, Get Help, Get Started
  • Office Hub, Solitaire, People, Power Automate, To Do, Alarms
  • Mail and Calendar (classic), Feedback Hub, Maps, Sound Recorder, Your Phone / Phone Link
  • Media Player, Quick Assist, Internet Explorer remnants, Tablet PC Math
  • OneDrive, Microsoft Edge (in many configurations)
  • Copilot, the new Outlook client, and Microsoft Teams (newly added)

The maintainer notes that future updates may bring finer-grained controls over which apps to delete and which to retain, but the current list reflects a consensus view of the communities that gather around NTDEV’s GitHub repository and its forks.

How to Use Tiny11 Builder

The process remains a deliberate, multi-step workflow rather than a one-click consumer tool. Users should start by downloading an official Windows 11 ISO directly from Microsoft. The Tiny11 Builder repository—available on GitHub under the NTDEV account—provides the tiny11maker.ps1 script. On a build machine, users must have PowerShell access and, if ISO creation is desired, the Windows ADK’s oscdimg.exe utility. After setting an appropriate execution policy, mounting the source ISO, and launching the script, they select the target edition, language, and whether to build a standard or Core image. The script services the offline image, applies compression, and outputs a bootable ISO. From there, standard tools like Rufus can write the ISO to USB media. During installation, disconnecting from the network prevents the OOBE from attempting online account enforcement.

This workflow is explicitly technical. It assumes comfort with PowerShell, DISM, and basic Windows imaging concepts. Casual users who are uncomfortable with command-line tooling should approach with caution.

Real-World Benefits for Windows 11 Users

The advantages of a Tiny11-derived installation flow directly from what is removed. The final ISO and the installed system footprint can be several gigabytes smaller, a meaningful gain on devices with 128GB or 256GB SSDs. Background churn from apps like Teams, Edge, and OneDrive disappears, leaving a quieter process list and fewer automatic updaters competing for resources on low-spec machines. For users who object to Copilot, cloud-first mail clients, or Microsoft Account requirements, the build-time removal provides a clean, reproducible method of reclaiming control rather than relying on fragile post-install workarounds that updates can undo. Kiosks, laboratory VMs, and embedded systems benefit from a deterministic base image with a minimal attack surface.

Risks, Trade-Offs, and What Tiny11 Cannot Solve

Every removal tool introduces consequences, and Tiny11’s appeal must be weighed against several hard trade-offs.

Updateability and Security Posture

The standard tiny11maker keeps Windows Update and most servicing channels intact, but the Core variant disables them. A Core-based installation will not receive critical security patches and is unsafe for general-purpose use. Even serviceable builds may behave differently during Microsoft’s cumulative update releases; platform updates can reintroduce components or cause compatibility problems. The maintainer and the community describe this as a “cat-and-mouse” dynamic, where each major servicing change may necessitate a rebuild.

Compatibility and Driver Breakage

Stripping inbox components can surface unexpected failures. Drivers that depend on certain multimedia packages, games that expect Xbox identity providers, and enterprise software that calls into Edge WebView2 can crash or malfunction on heavily slimmed images. Community threads document both smooth experiences and frustration where reverting to a vanilla Windows 11 install resolved issues that appeared only on Tiny11 Core systems.

Building a custom Windows image from an official ISO for personal use occupies a gray area in Microsoft’s licensing terms, but redistributing modified ISOs or offering them as a service almost certainly runs afoul of the license. Organizations cannot expect vendor support from Microsoft for systems provisioned with third-party modification tools; any troubleshooting starts from the assumption of a clean, unmodified OS.

Supply-Chain Trust

The Tiny11 source code is open and hosted on GitHub, but forks, prebuilt ISOs shared on forums, and binary executables from previous releases have occasionally raised alarms. Community incidents involving opaque binaries during older builds underscore the importance of downloading the builder from the official NTDEV repository and building locally against Microsoft-supplied ISOs.

Microsoft Countermeasures

Windows Update, the Microsoft Store, and component re-provisioning mechanisms can—and do—attempt to reinstate removed apps. Tiny11’s September refresh includes blocking measures, but the maintainer acknowledges this is an ongoing effort. Users should expect that a future servicing update may restore Edge, Outlook, or other components, requiring updated build scripts or follow-up interventions.

Practical Recommendations for the Windows 10 Transition

For those considering Tiny11 as a bridge past the Windows 10 end-of-support deadline, a conservative, test-driven approach is essential. Prefer the serviceable tiny11maker over the Core variant for any machine that connects to the internet. Build locally from an official Microsoft Windows 11 ISO; never download prebuilt Tiny11 ISOs from untrusted sources. Validate the result inside a virtual machine first, checking driver compatibility, Windows Update behavior, and critical application functionality before deploying to physical hardware. Keep vanilla Windows 11 install media and full backups on hand—if an update breaks a workflow because a required component is missing, an escape path is mandatory. Monitor the NTDEV GitHub repository for updates that patch reinstallation behaviors or address new servicing challenges, as noted in the project’s README and release notes.

Larger organizations and mission-critical systems require a different calculus. For those environments, the only supported paths remain a full Windows 11 upgrade or enrollment in the Extended Security Updates program. Tiny11 is a community tool, not a vendor-blessed servicing model.

The Community and Ecosystem Around Tiny11

Tiny11 is not a single, frozen artifact. A constellation of forks and community builds adapts the core scripts to newer Windows releases, language packs, and edge configurations like 24H2, 25H2, and Arm64 devices. Coverage from outlets such as Tom’s Hardware, Windows Central, and TechRadar has highlighted both the utility and the caveats of the September refresh, particularly its timing relative to Windows 10’s retirement. The project’s GitHub repository remains the authoritative source for code changes, release notes, and guidance, while subreddit threads and forum discussions catalog real-world compatibility quirks and troubleshooting steps.

NTDEV’s public statements suggest the builder will continue evolving toward more granular control over removals and more robust resistance to Microsoft’s re-provisioning mechanisms. For now, the tool provides a tangible, immediately usable alternative for a specific audience: technically comfortable users who want a lighter, less cloud-centric Windows 11 and are willing to invest the effort to build, test, and maintain their own images.

A Tool for Control, Not a Cure-All

As the Windows 10 end-of-support deadline accelerates upgrade decisions, Tiny11 Builder’s September 2025 refresh equips users with a PowerShell pipeline that explicitly strips Copilot, Outlook, and Teams, compresses the final ISO with LZX, and blocks known reinstallation paths. These capabilities make it more capable and versatile than earlier iterations. Yet the most important takeaway is not the feature list but the necessary caution: Tiny11 is a precision tool that rewards testing, demands a recovery plan, and punishes uninformed deployment. For the enthusiasts, administrators, and privacy-focused users who understand its trade-offs, it offers a real and practical way to shape Windows 11 into something closer to what they want—without surrendering the security patches that keep a machine viable after October 14, 2025.