Microsoft’s push to embed Copilot AI and cloud‑centric apps into Windows 11 has met a direct countermeasure: the September 2025 release of Tiny11 Builder now lets anyone craft an installation image that explicitly strips out Copilot, the new Outlook client, Teams, and dozens of other inbox apps before a single byte hits the disk. The community‑driven project, maintained by developer NTDEV, has transformed its earlier ad‑hoc debloating scripts into a polished PowerShell pipeline, bringing LZX compression into the mix to shrink ISO sizes dramatically.

For power users, IT admins, and anyone weary of an operating system that doubles as a service‑pushing billboard, the update is a game‑changer. But it also sharpens the trade‑offs between minimalism and maintainability, especially with an experimental “Core” variant that sacrifices future updates for even more radical space savings.

What’s New: AI Removal Takes Center Stage

The September refresh marks the first time Tiny11 explicitly targets Microsoft’s recent in‑box AI integrations. Where earlier versions dropped only classic bloatware, the new builder adds robust removal logic for Copilot, the replacement Outlook client (often called “new Outlook”), and Microsoft Teams. These three apps have become symbols of the operating system’s shift toward a persistent cloud and AI layer, and their inclusion in the default image now has a clear off‑switch.

But the update isn’t just about what gets removed. The entire toolchain has been rewritten as a single PowerShell script—tiny11maker.ps1—improving compatibility across Windows 11 editions, languages, and architectures. The workflow now encourages users to supply an official Microsoft ISO, select their desired removals from a granular list, and let the script handle the rest. Under the hood, it leverages DISM for image servicing and oscdimg.exe from the Windows Assessment and Deployment Kit to produce a bootable, UEFI‑ready ISO.

Another structural change is the adoption of LZX (recovery) compression via DISM’s /Compress:recovery switch. This can shrink an output ISO by 30–40% compared to standard compression, but it demands more memory and CPU time during the build process. The result is a significantly smaller image that still boots and behaves like a regular Windows 11 install—minus the unwanted cargo.

Finally, the builder now includes registry tweaks and provisioning blocks designed to prevent Windows Update or the Microsoft Store from silently reinstalling removed apps after a feature update. While not foolproof, these mitigations represent a more proactive stance against what the community calls “re‑bloating.”

The Removal Roster: What You Can Strip

The builder presents a long list of inbox components it can omit. The most notable entries in the standard profile include:

  • Copilot
  • New Outlook client
  • Microsoft Teams
  • Clipchamp, News, Weather
  • Xbox apps and related services
  • GetHelp, GetStarted, Office Hub, Solitaire
  • PeopleApp, PowerAutomate, To Do, Alarms
  • Classic Mail and Calendar, Feedback Hub, Maps, Sound Recorder
  • Your Phone (Phone Link), Media Player, Quick Assist, Tablet PC Math
  • Microsoft Edge (with handling for deep Settings remnants)
  • OneDrive

Users can fine‑tune this list using script options; the builder simply exposes a set of checkboxes during execution. The explicit focus on AI and collaboration tools—Copilot, Outlook, Teams—positions the September release as a direct response to what many enthusiasts see as an unwelcome expansion of Microsoft’s service footprint.

Why This Matters: More Than Just Disk Space

Windows 11’s default installation image has become a curated bundle of apps, cloud prompts, and AI features that push users toward Microsoft’s ecosystem. For those in enterprise environments, test labs, or simply seeking a quieter desktop, this creates three concrete pain points:

  • Footprint creep – Preinstalled inbox apps consume storage and run background processes that matter on low‑capacity or low‑RAM devices. Removing them can free gigabytes and reduce idle CPU activity.
  • Update noise – Every inbox app is an independent update vector. In tightly controlled deployments, unexpected background downloads from the Store can break determinism and compliance.
  • Cloud entanglement – Copilot and the new Outlook are deeply integrated with online services and telemetry. For privacy‑conscious users or air‑gapped systems, their mere presence represents an undesired surface area.

Tiny11 returns image composition to the builder. Instead of accepting Microsoft’s defaults and spending hours surgically removing apps post‑install, admins can produce a clean baseline image in one step. This control is especially valuable for kiosk mode, embedded appliances, virtual machines, and lab rigs where reproducibility matters.

How It Works: A Technical Deep Dive

At its core, Tiny11 Builder is an orchestration layer over Microsoft’s own tools. The script mounts a Windows image (WIM or ESD) from an official ISO, then uses DISM to service it—removing packages, scheduled tasks, registry entries, and policies tied to the target apps. It can also apply an optional answer file (autounattend.xml) to automate OOBE, such as bypassing the Microsoft account requirement.

After servicing, the image is recompressed using DISM with the recovery/LZX algorithm. Finally, oscdimg.exe repackages everything into a bootable ISO. All steps happen locally, using source media that the user must supply along with a valid license.

Tiny11 vs. Tiny11 Core

The builder now ships with two profiles:

  • Tiny11 (standard) – Keeps Windows Update, the component store (WinSxS), and servicing stacks intact. This image remains updateable and can receive future quality and feature updates. It is the recommended profile for any system that will connect to a network or be used as a daily driver.
  • Tiny11 Core (experimental) – Strips WinSxS and many servicing hooks. The result is an ultra‑compact image (ISO sizes around 2 GB, on‑disk footprints near 3.3 GB). Core disables Windows Update and Windows Defender in many configurations. As a non‑serviceable image, it is suitable only for disposable VMs, test rigs, or permanently air‑gapped appliances—never for internet‑facing production.

Benefits: Where Tiny11 Shines

  • Low‑end device revival – On older hardware with limited storage or RAM, eliminating background apps and their services can measurably improve responsiveness.
  • Lab consistency – QA teams can spin up identical, minimal environments for driver and application validation without worrying about rogue Store updates.
  • Kiosk and embedded – Single‑purpose systems benefit from a smaller attack surface and absence of unrelated UI prompts.
  • Privacy‑first installations – Users who object to AI assistants or cloud‑tied mail clients can build an image that never includes them.

Real Risks and Caveats

Security and Updateability

The biggest concern is the Core variant’s removal of servicing infrastructure. Without Windows Update, a system cannot receive security patches and will become increasingly vulnerable. Even the standard Tiny11 profile can be broken if users over‑aggressively prune components that Windows Update relies on. Always validate that the resulting image can install cumulative updates before deploying.

Support and Warranty

Any custom‑built image is unsupported by Microsoft and likely by OEMs. Enterprises should route such efforts through approved imaging pipelines (SCCM, MDT, Intune) and confirm with their legal and procurement departments that modified images do not violate licensing or support agreements.

Re‑bloating After Feature Updates

Microsoft’s servicing model can re‑provision inbox apps during a feature update. Tiny11’s registry blocks reduce this risk, but they are not guaranteed permanent. Admins must treat image upkeep as an operational task—rebuild or reapply mitigation scripts after each semi‑annual channel release.

Driver and Hardware Quirks

Stripping certain platform components can break drivers that silently depend on them. Audio, camera, or OEM‑specific utilities have been known to malfunction on heavily pruned builds. Thorough testing on target hardware is mandatory.

Supply‑Chain Risk

Pre‑built Tiny11 ISOs found on forums or torrents are a security gamble. The only safe method is to run the builder yourself against a checksum‑verified official ISO. Never deploy an unsigned, third‑party image in production.

Building Your Own Tiny11 ISO: A Step‑by‑Step Guide

  1. Download an official Windows 11 ISO for your desired edition and build from Microsoft’s site. Verify the SHA‑256 hash.
  2. Clone the Tiny11 Builder repository and review the scripts (tiny11maker.ps1 and tiny11Coremaker.ps1) to understand available options.
  3. Install the Windows ADK to obtain oscdimg.exe if you plan to produce a bootable ISO.
  4. Launch PowerShell as Administrator and temporarily set the execution policy: Set-ExecutionPolicy Unrestricted -Scope Process.
  5. Run the builder in a clean VM first: powershell -f C:\path\to\tiny11maker.ps1 -ISO -SCRATCH <scratch_path>. Follow the prompts to choose SKU, architecture, and removal list.
  6. Test the output ISO in multiple scenarios: clean install, in‑place upgrade simulation, driver installation, and a complete Windows Update cycle.
  7. For production machines, stick with the serviceable Tiny11 profile. Reserve Core for disposable lab images.
  8. Maintain rollback capability—keep the original ISO, license key, and a backup of your custom image. Document every component you removed.

Testing Checklist

Before putting any custom image into production, verify:

  • Boot and POST success on target hardware
  • Network connectivity (Ethernet and Wi‑Fi) and driver stability
  • Audio input/output and camera operation
  • Windows Update and Windows Defender behavior (if retained)
  • Re‑installation attempts by the Microsoft Store after a feature update
  • Compatibility with enterprise management tools (Intune, SCCM, third‑party AV)

Rebuilding an ISO does not change your licensing requirements; proper activation is still mandatory. However, modified images can complicate vendor support. For organizations, the best practice remains integrating debloating into existing deployment workflows using tools like Microsoft Deployment Toolkit or Configuration Manager, where changes are tracked and auditable. Tiny11 is a valuable community resource, but it is not a substitute for formal change management and security compliance processes.

The Cat‑and‑Mouse Game Continues

History shows that Microsoft adjusts servicing and Store behavior, community builders respond, and the cycle repeats. Tiny11’s new registry and uninstall tactics are a creative step forward, but long‑term persistence requires vigilance. Expect to rebuild or patch your custom image after every major Windows 11 feature update. For admins, that means scheduling regular image refresh cycles just as you would for driver packs or application updates.

Strengths, Trade‑offs, and Best Practices

Strengths: The builder is transparent, uses Microsoft‑signed tooling, and delivers fine‑grained control. The PowerShell rewrite improves cross‑language and cross‑architecture support. LZX compression meaningfully reduces distribution size, and the explicit focus on AI components aligns with a clear community demand.

Trade‑offs: Aggressive stripping can sever update paths, break security features, and cause driver incompatibilities. The Core variant is a fascinating technical demo but is absolutely not a daily driver.

Best practices: Always build from an official ISO on a trusted machine. Choose the serviceable profile for any system that will touch the internet. Test in a VM first, document everything, and treat your custom image as a living artifact that requires maintenance over time.

The Bottom Line

Tiny11’s September 2025 refresh is a pragmatic, well‑executed evolution. It turns the tedious ritual of post‑install debloating into a repeatable ISO‑creation workflow that targets Microsoft’s most controversial additions head‑on. For hobbyists, lab managers, and privacy‑focused users, the builder is a compelling tool—provided its limitations are respected.

The project does not magically solve Windows 11’s complexity, but it hands a meaningful degree of agency back to the person behind the keyboard. In an era where operating systems increasingly make decisions on your behalf, that might be enough.