Tiny11’s builder, a community-favorite script for slimming down Windows 11 installs, just got a major update: it can now surgically remove Copilot, the new Outlook for Windows, and Microsoft Teams from the operating system image before you ever hit the desktop. The update, announced by project maintainer NTDev, also adds explicit compatibility with the upcoming Windows 11 25H2 release and employs DISM’s recovery compression to produce even smaller installation ISO files. For power users, IT administrators, and anyone tired of seeing inbox apps they never asked for, this is a significant step toward a truly minimal Windows experience.

But stripping out tightly integrated cloud services and AI assistants isn’t without consequences. While the gains are real — less disk usage, fewer background processes, and no unwanted prompts — the approach can break system functionality, complicate updates, and introduce supply-chain risks if you’re not careful. Here’s everything you need to know about the revamped Tiny11 builder, why it’s stirring up the community, and how to use it (or avoid its pitfalls) intelligently.

What Tiny11 Removes and Why It Matters

The builder’s updated package list is exhaustive. According to the GitHub repository, the script now omits a long roster of Windows 11 inbox apps, including:
- Clipchamp, News, Weather
- Xbox apps (the Xbox Identity provider is retained to allow optional reinstallation)
- GetHelp, GetStarted, Office Hub
- Solitaire, People, Power Automate, To Do, Alarms
- Classic Mail and Calendar, Feedback Hub, Maps, Sound Recorder
- Your Phone (Phone Link), Media Player, Quick Assist
- Tablet PC Math, Edge, OneDrive
- And most notably, Copilot, the new Outlook for Windows, and Microsoft Teams (both consumer and home variants)

NTDev’s XDA-cited announcement highlighted the removal of the “new Outlook” client with a frank note calling it “IMO absolutely sucks btw,” reflecting a sentiment shared by many users who find the web-wrapper replacement for the classic Mail app sluggish and intrusive. Teams and Copilot, meanwhile, represent Microsoft’s aggressive push into AI and collaboration — services that consume system resources, auto-update frequently, and often launch without explicit user consent.

By excising these from the base image, Tiny11 shifts control back to the installer. You decide whether to add them later, rather than having them forced on you during setup. For disk-constrained devices, virtual machines, or enterprise environments that provision their own communication tools, this is a pragmatic win. The official list underscores the breadth of Microsoft’s default software bundle and explains why debloating efforts remain so popular.

How the Tiny11 Builder Works Under the Hood

Tiny11 isn’t a pre-compiled tool that magically alters Windows; it’s a transparent PowerShell script that manipulates a genuine Microsoft ISO. The workflow is straightforward: you supply an official Windows 11 image, and the script uses built-in deployment tools — DISM for image servicing and oscdimg.exe from the Windows Assessment and Deployment Kit (ADK) to produce a new, leaner bootable ISO.

Version 2.4 of the builder (the release that introduced these features) adds full support for Windows 11 25H2 builds, meaning it can handle both WIM and ESD image formats across different architectures. The maintainer also integrated the DISM recovery compression flag, which applies stronger compression during the image build phase, shaving additional megabytes off the final ISO without affecting runtime performance on the installed system. The script itself relies solely on Microsoft-signed utilities; there are no third-party binaries, reducing the attack surface for anyone who audits the code before running it.

Crucially, the builder offers two profiles:
- Regular Tiny11: This mode removes the listed apps but preserves the Windows Component Store (WinSxS) and servicing infrastructure. The resulting OS can still receive monthly updates, add optional features, and install language packs through Windows Update.
- Tiny11 Core: An extreme variant that strips WinSxS and other servicing components to achieve an even tinier image. Core is unserviceable — you cannot apply feature updates or add components back without rebuilding the image from scratch. It is intended for disposable virtual machines, test rigs, or embedded scenarios where long-term patchability isn’t required.

This distinction is vital. Many horror stories from earlier Tiny11 experiments came from users who accidentally picked Core for a daily driver and later found themselves unable to patch known vulnerabilities or restore missing functionality.

The Practical Upsides: Leaner, Cleaner, Faster

When applied correctly, the benefits of a Tiny11-built image are immediate and tangible. First, the installation footprint shrinks significantly. Without Copilot’s integrated AI services, Teams’ background processes, Outlook’s web runtime, and dozens of other apps, a fresh install can save several gigabytes of disk space — a gift to budget laptops with 64GB or 128GB eMMC storage.

Second, the default desktop is refreshingly empty. There are no auto-pinning Office web apps, no pre-loaded game promotions, and no constant prompts to “try the new Outlook.” For organizations that deploy custom taskbars and carefully manage user experience, this eliminates the post-install cleanup scripts that often miss updates or leave registry artifacts.

Third, background activity drops. Fewer inbox apps mean fewer scheduled tasks, less telemetry traffic, and fewer services waking up the CPU. Community testers have reported noticeably snappier boot times and lower idle memory usage on older hardware after installing Tiny11 — an outcome that aligns with the reduced dependency tree.

Finally, the builder gives administrators deterministic control. Instead of running an uninstall PowerShell script after deployment (which can fail or partially remove components), they can produce a clean image that never contained the unwanted apps in the first place. This approach is more reliable when cloning images for mass deployment.

The Measurable Risks and Caveats

Tiny11’s power comes with serious trade-offs that must be weighed before you download the script.

Serviceability Gaps. The most critical risk stems from the Core profile, which breaks Windows Update’s ability to service the operating system. Even the regular Tiny11 profile, while serviceable, removes some packages that might be required by future updates or optional features. Microsoft doesn’t test its cumulative updates against heavily debloated images, so uncharted compatibility issues can surface months later, leaving you with a system that refuses to install a critical security patch.

Broken Features and Dependencies. Windows 11’s shell, search, and file association mechanisms intertwine with several of the removed apps. Tearing out Edge and Copilot can disable web search results from the Start menu or break links that expect the browser. Removing Mail and Calendar disables default mailto: protocol handlers, breaking email links in third-party apps. The classic Your Phone app removal severs seamless phone integration. These breakages aren’t bugs per se; they’re consequences of dismantling a tightly coupled system. Users should verify that their essential workflows don’t depend on any of the culled components.

Reinstallation Friction. Adding back a removed inbox app isn’t always a one-click affair. While many can be reinstalled from the Microsoft Store or via winget, some packages have dependency chains that don’t resolve cleanly outside the original provisioning framework. Community reports mention cases where the new Outlook or Dev Home applications spontaneously reappeared after a Windows update, suggesting complex retention logic in Microsoft’s servicing stack. If you later need Teams for a work contract, you might wrestle with installation failures that require rebuilding the image.

Security and Supply-Chain Risks. This is the biggest red flag for casual users. Pre-built Tiny11 ISOs floating around the web are not signed by Microsoft, and a malicious actor could easily bundle malware. The project’s maintainer explicitly urges users to build the ISO themselves from an official source using the provided scripts. Doing so limits exposure to the script itself (which is open to inspection) and the trusted Microsoft tools it invokes. Still, supply-chain discipline is paramount: always verify SHA-256 checksums of the base ISO and only obtain it directly from microsoft.com.

Legal and Support Entanglements. Microsoft’s support channels typically refuse assistance for systems running modified installation media. Corporate environments may violate vendor agreements or internal compliance policies if unapproved, debloated images are used on enterprise hardware. Before rolling Tiny11-modified installs in a business setting, IT security, legal, and procurement teams must sign off.

A Safe Approach: Best Practices for Using Tiny11

If you decide the gains outweigh the risks, follow a disciplined, conservative workflow to minimize surprises.

  1. Source an official ISO. Download Windows 11 directly from Microsoft’s media creation tool or volume licensing portal. Never use a torrent or third-party mirror.
  2. Audit the script. Clone the Tiny11 builder repository (currently maintained on GitHub) and read through the PowerShell code. Its reliance on DISM and the ADK means no opaque binaries, but you should still understand what it’s doing.
  3. Choose the regular profile. Unless you’re building a short-lived VM or a kiosk that will never be updated, select the serviceable Tiny11 mode. Avoid Core for any machine that needs to stay secure.
  4. Test in a sandbox. Deploy the custom ISO to a virtual machine first. Install your critical applications, run Windows Update, and check for anomalies. Test hardware-specific functions like Bluetooth, audio, and webcam if you plan to use it on physical hardware.
  5. Back up relentlessly. Before installing on a daily driver, create a system image backup and a recovery drive. If an update breaks something months later, you’ll need a quick rollback path.
  6. Plan for reinstallation. Document the exact winget commands or download links for any removed apps you might need later. For enterprise deployments, package these as post-installation scripts that run on demand.

For those who find ISO rebuilding too daunting, consider lighter-touch alternatives. Tools like Win11Debloat, O&O AppBuster, or simple PowerShell AppX removal commands can strip many inbox apps after installation without altering the servicing stack. These won’t match Tiny11’s completeness, but they carry far less risk.

Community Feedback: Successes and Stumbles

The Windows enthusiast community has been quick to test the new builder, and the reports paint a nuanced picture. Many users celebrate the ability to run Windows 11 on hardware that felt sluggish under the default load. One Reddit thread detailed a 2015-era laptop that went from “barely usable” to “snappy” after installing a Tiny11 image without Edge, OneDrive, and Teams. Virtualization fans report that Core variants consume under 4GB of disk space, making them ideal for ephemeral testing environments.

But there are also cautionary tales. Several users in the Tiny11 subreddit complained that microphone access disappeared after upgrading to a newer cumulative update — a side effect that traced back to aggressive removal of a speech-recognition-related package. Others found that after removing the Xbox Identity provider (a step some went beyond the script to attempt), certain Microsoft Store games refused to authenticate. These edge cases underscore the importance of sticking to the maintainer’s curated removal list and avoiding impulse deletions.

Is Tiny11 Right for You? A Decision Framework

Use this quick checklist to decide whether the new Tiny11 builder belongs in your toolbox.

Consider Tiny11 if:
- You need a minimal Windows image for virtual machines, kiosks, or lab rigs.
- You’re comfortable building ISOs, auditing scripts, and manually troubleshooting update issues.
- Disk space is at an absolute premium, and you’re willing to sacrifice some convenience.
- You want complete control over the inbox apps from the moment of installation.

Avoid Tiny11 Core (or perhaps all profiles) if:
- You rely on automatic, unattended Windows updates for security and compliance.
- You cannot afford downtime caused by a broken feature or update conflict.
- You lack the expertise or time to rebuild and redeploy an image if something goes wrong.
- You use enterprise-managed devices with software asset management or vendor support agreements.

Final Analysis: A Powerful Tool for the Right User

The Tiny11 builder’s new ability to excise Copilot, the new Outlook, and Teams is a milestone in the ongoing effort to reclaim Windows 11 from software bloat. By bringing 25H2 support and recovery compression into the fold, NTDev has made the tool more relevant than ever as Microsoft prepares its next feature update. For the skilled practitioner, the script offers a transparent, auditable path to a lean, mean Windows installation that boots faster, idles lighter, and respects user choice.

Yet the caveats are not boilerplate warnings; they are real limitations that have bitten real users. The trade-off between cleanliness and serviceability is inherent, and the Core variant’s radical pruning is only suitable for throwaway environments. As with any powerful utility, success depends on knowing exactly what you’re doing — and what you’re giving up. If you approach Tiny11 with eyes wide open, a trusted base ISO, and a solid backup strategy, you’ll likely join the ranks of satisfied minimalists. If you’re unsure, start with post-install debloating tools and leave image rebuilding for another day.

One thing is certain: the demand for a cleaner Windows isn’t going away, and Microsoft’s continued bundling of cloud-connected apps ensures that projects like Tiny11 will remain community essentials for years to come.