Tiny11 Builder Rips Out Copilot and New Outlook, Shrinks Windows 11 ISOs Ahead of 25H2

Windows 10’s end-of-life clock is ticking, and with it, a renewed urgency for holdouts to find a path forward—especially those clinging to hardware Microsoft deems incompatible with Windows 11. Enter Tiny11, a community-driven project that has just sharpened its teeth. The latest version of the Tiny11 builder, released in September 2025, guts Windows 11 images of Copilot, the new Outlook client, and Microsoft Teams, while switching to DISM’s recovery compression to churn out ISOs barely larger than a DVD. The timing isn’t coincidental: the builder is explicitly tuned for Windows 11 feature updates like the upcoming 25H2, making it one of the most aggressive anti-bloat tools available as Microsoft phases out Windows 10 support on October 14, 2025. This isn’t a ready-made ISO to download—it’s a PowerShell script, maintained by developer NTDEV, that remixes an official Windows 11 image into something lean, mean, and notably quieter.

A Two‑Front Assault on Bloat: tiny11maker vs. tiny11coremaker

The builder ships with two distinct personalities. The standard mode, called tiny11maker, produces a debloated but serviceable Windows image. It yanks out a long list of inbox apps—Edge, OneDrive, Xbox components, Mail & Calendar, Clipchamp, News, Weather, and more—yet keeps Windows Update and the ability to install or restore features later. This is the recommended route for anyone who wants a slimmer OS without completely severing ties to Microsoft’s servicing pipeline.

Then there’s tiny11coremaker, a “quick and dirty development testbed.” Core mode goes for the jugular, removing a broader swath of components and deliberately sacrificing updateability and serviceability. Once baked, a core image is sealed: no Windows Update, no adding features, no rollback without rebuilding from scratch. It’s intended for throwaway VMs, hardware recovery scenarios, or tinkerers who prize minimal footprint over future-proofing. Use core mode on a daily driver and you’ll likely regret it the moment a critical security patch lands.

The Kill List: What Gets Removed

The September 2025 release doesn’t just prune the usual suspects. It surgically excises some of Microsoft’s most aggressively pushed features:

• Copilot (AI assistant) – Stripped out entirely, with attempts to block reinstallation via servicing updates.
• New Outlook for Windows – The replacement for classic Mail & Calendar; gone.
• Microsoft Teams (consumer) – The chat client that auto-launches and hogs resources.
• Edge and OneDrive – Browser and cloud sync ties severed.
• Xbox apps, Photos, Media Player, Clipchamp, Maps, Feedback Hub, GetHelp, QuickAssist, Your Phone – A swath of inbox cruft.

These aren’t just hidden or disabled; the scripts nuke the packages from the image before you ever boot. The removals are codified in the builder’s PowerShell scripts, so the resulting ISO is effectively “clean by default.” The inclusion of Copilot and Outlook removal is particularly notable because those apps are deeply woven into Microsoft’s modern Windows experience and are frequently force-installed via Store or servicing updates. The builder inserts registry tweaks and package-blocking stanzas to keep them at bay, though the arms race with Microsoft’s servicing stack is never over.

Space Savings That Actually Matter

Tiny11 leverages aggressive compression—historically LZX/LZMS, and now DISM’s /Compress:recovery flag—to shrink the final image. In practice, that means a Windows 11 installation that typically gobbles 20–30 GB on disk can land around 3–4 GB. The ISO itself often fits on a single-layer 4.7 GB DVD. Independent testing by Tom’s Hardware, TechSpot, and others confirms these numbers are achievable with standard (serviceable) builds, provided you follow the script’s default settings. The trade-off is time and memory: recovery compression is slow and RAM-hungry during image creation, but the payoff is a portable, fast-deploying image.

Why Tiny11 Suddenly Matters More

With Windows 10’s October 2025 deadline, millions of PCs face an upgrade wall. Tiny11 crashes through that wall by ignoring Windows 11’s hardware checks—no TPM 2.0, no Secure Boot, no 8th-gen Intel requirement. The result? Ancient laptops, repurposed desktops, and even some netbooks can run a modern Windows 11 kernel with a fraction of the overhead. That’s a sustainability win: fewer devices land in landfills, and users on tight budgets get a capable OS.

Performance benefits are tangible. Stripping out background processes, telemetry collection, and auto-updaters reduces CPU churn, I/O contention, and boot delays. Gamers, in particular, report smoother frame times when the OS isn’t busy phoning home or pre-loading apps you never asked for. For virtual machine labs and rapid-fire deployment scenarios, a sub-4 GB image means faster copies and less storage waste.

The Trade‑Offs Are Real—and Risky

No free lunch. The very features that make Tiny11 attractive also introduce sharp edges.

1. Update Fragility

• Core mode is explicitly non-serviceable. Once deployed, you cannot install cumulative updates or new features. Security patches? Forget it. This makes core images radioactive for anything but isolated test VMs.
• Even standard mode isn’t bulletproof. Microsoft may reintroduce removed components during a feature update (like 24H2 or 25H2), causing installation failures or silent re-bloat. The builder’s blocking heuristics can’t predict every edge case, and some apps may reappear via Store-based servicing. Expect a cat-and-mouse game with each major release.

2. Compatibility Breaks

Removing Edge or OneDrive can break system features that expect them. Certain Settings panes, search indexing, or web-linked services may error out. Some applications ship with implicit dependencies on inbox components, leading to crashes or missing functionality. On exotic hardware, stripped images might omit drivers or OEM tweaks, causing boot loops or device failures—especially on preview or Canary builds.

3. Security Reality Check

A non-serviceable image is a ticking time bomb. Missing one security update is dangerous; missing dozens is catastrophic. Even if you rebuild images periodically, the gap between builds is a period of exposure. Community members strongly recommend never exposing a core-mode machine to the internet. Standard-mode users must still monitor patch status vigilantly.

4. Licensing and Support

Tiny11 modifies a Microsoft image, but it doesn’t grant you a free license. You still need a valid Windows key and activation. Organizations should review their volume licensing agreements before deploying modified images at scale. Official Microsoft support won’t touch a Tiny11 install, and OEMs may wash their hands of warranty claims on altered software. Treat Tiny11 as an unsupported, community solution—no safety net.

A Safe, Sane Workflow for Testing Tiny11

If you’re curious and want to kick the tires, follow these steps dogmatically:

1. Back up everything – Full disk images and off-machine copies of critical data.
2. Start in a VM – VirtualBox, Hyper‑V, or VMware. Validate boot, drivers, app compatibility before touching metal.
3. Download an official Windows 11 ISO – Only from Microsoft’s website. Never use pre‑cooked third‑party ISOs, which are a malware minefield.
4. Clone the tiny11builder repository from GitHub – Read the README thoroughly. The script expects an untouched ISO and administrative PowerShell.
5. Run tiny11maker.ps1 – For most, that means choosing the standard mode. If you opt for core, understand you’re building a sealed test image.
6. Create bootable media – DISM or Rufus can handle the compressed WIM/ESD. Install on a spare drive or VM.
7. Disconnect the internet during OOBE – This prevents Microsoft’s online setup from redownloading components you just stripped. Reconnect only after assessing the system’s state.
8. Validate thoroughly – Check networking, audio, graphics, and your essential applications. Keep a rescue USB handy.

Enterprise and Managed Environments: Not a Silver Bullet

IT departments should approach Tiny11 with extreme caution. Compliance frameworks often mandate patching cadences that core mode can’t satisfy. Standard mode may still cause unpredictable behavior with device management tools like Intune, SCCM, or Group Policy. Inbox component removals can break security baselines that expect certain services to be present. Tiny11 might have niche uses—throwaway lab images, kiosk machines, or demo hardware—but it’s not a supported production path. If you value support contracts, stick to official Windows editions and use Microsoft’s own provisioning tools to strip what you can.

Separating Verified Fact from Hyperbolic Claim

Let’s cut through the noise with a short reality table:

The eye‑popping 100 MB RAM demonstrations by NTDEV are clever feats of minimalism, but they represent heavily stripped, non‑GUI configurations. They’re fascinating proofs of concept, not a recommended operating mode. Don’t confuse them with real‑world performance expectations.

The Long View: An Arms Race Heating Up

Tiny11’s popularity isn’t just about shrinking Windows. It’s a reaction to Microsoft’s deepening integration of AI, cloud services, and mandatory app bundles. The project’s explicit targeting of Copilot and Outlook signals a pushback against features users never requested. As Microsoft tightens its grip on the inbox—tying more services to Edge, Bing, and AI—community builders will keep updating scripts to pry them out. Expect each Windows feature update to bring new challenges, and each Tiny11 release to respond with fresh removal routines and blocking tricks.

For users who want a leaner, more private Windows without stepping outside official support, Microsoft does offer some built‑in relief: enterprise provisioning, app removal via PowerShell, and feature management policies. These are safer, if less thorough, than a community‑built ISO. For the risk‑tolerant, Tiny11’s standard mode offers a compelling middle ground—provided you test fastidiously and never wander far from a working backup.

A Tool, Not a Panacea

Tiny11’s builder is a genuinely impressive piece of technical craftsmanship. It delivers on its promises: smaller images, fewer background processes, and compatibility with hardware Microsoft abandoned. The September 2025 update raises the bar by neutering Copilot and the new Outlook, and the 25H2 readiness puts it squarely in the path of users fleeing Windows 10. But the tool demands respect. Core mode is a sealed box—dangerous for anything that touches the internet. Standard mode walks a tightrope of update fragility. Security and support are your responsibility.

For hobbyists, tinkerers, and anyone nursing an old laptop past the October deadline, Tiny11 is worth a careful experiment. For enterprises and mainstream consumers who value warranty, compliance, and patch predictability, it remains a curiosity rather than a replacement. The conversation Tiny11 sparks, however, is legitimate: many users hunger for an operating system that does what they need, not what Microsoft’s product managers think they should want. That tension will define the next chapter of Windows, whether Microsoft likes it or not.