Tiny11’s new release turns the DIY Windows 11 rebuild into an explicit counterpunch against Microsoft’s in‑box AI push, giving enthusiasts and admins the tools to create a stripped, 25H2‑ready Windows 11 ISO that omits Copilot, the new Outlook client, Teams, and a long roster of inbox apps while using LZX/recovery compression to shrink image size. (ntdotdev.wordpress.com) (github.com)
The Tiny11 project — maintained by NTDEV — has long offered a community‑driven route to a leaner Windows 11 by rebuilding an official Microsoft ISO and removing selected inbox apps and servicing paths. The September 2025 refresh moves the builder to a PowerShell‑centric pipeline, broadens compatibility across SKUs, languages and architectures, and adds explicit removals for Microsoft’s recent AI and mail integrations: Copilot, the new Outlook client, and Microsoft Teams. (github.com) (github.com)
This release also doubles down on producing smaller output ISOs via MS‑supported image compression (DISM with recovery/LZX compression), and introduces an experimental Tiny11 Core variant for ultra‑compact, test‑only images that sacrifice serviceability and, in some configurations, core update mechanisms. Those two technical shifts — explicit AI component removal and LZX/recovery compression — are the structural changes that make this update notable for power users, testers, and constrained‑device scenarios. (ntdotdev.wordpress.com) (github.com)
That said, the updated builder is not a universal fix. Organizations and mainstream users must weigh the serviceability and security tradeoffs carefully and prefer the regular Tiny11 profile unless they have a controlled, air‑gapped, or disposable VM use case for Core. The real power here is choice: Tiny11 hands the image‑creation decision back to the user, and with that power comes responsibility — test thoroughly, document changes, and deploy conservatively. (windowscentral.com)
Tiny11 is available on its public repository where the release notes, scripts and usage instructions are published; the developer recommends building your own image from an official ISO rather than using old prebuilt ISOs. (github.com) (ntdotdev.wordpress.com)
Conclusion: For those who value a minimal, deterministic Windows 11 with no Copilot, no bundled Teams, and no forced new Outlook client, Tiny11’s new builder provides a robust, transparent, and technically polished way to produce it — but the safety and support tradeoffs should dictate where and how you use it. (github.com)
Source: TweakTown Tiny11 declares war on AI: build a DIY Windows 11 install with no Copilot, Teams or other bloat
Background / Overview
The Tiny11 project — maintained by NTDEV — has long offered a community‑driven route to a leaner Windows 11 by rebuilding an official Microsoft ISO and removing selected inbox apps and servicing paths. The September 2025 refresh moves the builder to a PowerShell‑centric pipeline, broadens compatibility across SKUs, languages and architectures, and adds explicit removals for Microsoft’s recent AI and mail integrations: Copilot, the new Outlook client, and Microsoft Teams. (github.com) (github.com)This release also doubles down on producing smaller output ISOs via MS‑supported image compression (DISM with recovery/LZX compression), and introduces an experimental Tiny11 Core variant for ultra‑compact, test‑only images that sacrifice serviceability and, in some configurations, core update mechanisms. Those two technical shifts — explicit AI component removal and LZX/recovery compression — are the structural changes that make this update notable for power users, testers, and constrained‑device scenarios. (ntdotdev.wordpress.com) (github.com)
What’s included in the new Tiny11 Builder
Headline changes
- Removal of Copilot, the new Outlook client, and Microsoft Teams from the rebuilt image. This is the most visible change and the one driving much of the recent coverage. (github.com)
- PowerShell rewrite into a single pipeline script (tiny11maker.ps1), improving language/architecture flexibility and simplifying the workflow. (github.com)
- Shift to DISM /Compress:recovery (LZX) for significant ISO size reductions, at the cost of higher memory/CPU use during image creation. (github.com)
- Proactive blocking and registry tweaks intended to reduce the chance Windows Update/Store will reinstall removed inbox apps. (github.com)
- Tiny11 Core: an experimental, non‑serviceable variant intended as a “quick and dirty” testbed — not recommended for production machines. (windowscentral.com)
The removal roster (standard tiny11 profile)
The updated builder publishes an extensive list of inbox components it can omit. The most commonly reported items you can remove include:- Clipchamp, News, Weather
- Xbox apps (with Xbox Identity Provider nuances)
- GetHelp, GetStarted, Office Hub, Solitaire
- PeopleApp, PowerAutomate, To Do, Alarms
- Mail and Calendar (classic), Feedback Hub, Maps, Sound Recorder
- Your Phone (Phone Link), Media Player, Quick Assist, Tablet PC Math
- Edge (with handling for Settings remnants), OneDrive
- Copilot, New Outlook client, Microsoft Teams
(Use the builder’s options to pick what you want removed; the list above reflects the standard script defaults and reported behavior). (ntdotdev.wordpress.com)
Why this matters: technical and cultural context
Windows 11’s default image has become more than a base OS — it’s a curated bundle of apps, cloud prompts, and AI‑centric features that push users toward Microsoft’s services. For many users and administrators this presents three practical annoyances:- Disk and memory footprint: preinstalled inbox apps and services use storage and run background processes that matter on low‑capacity or low‑RAM devices.
- Update and background churn: inbox apps add auto‑update vectors and background tasks that can complicate deterministic deployments.
- Surface area and cloud nudging: components like Copilot and the new Outlook are tightly coupled to cloud services and telemetry paradigms that some users actively want to avoid.
Deep dive: how Tiny11 Builder works (technical overview)
Core tooling and pipeline
Tiny11 Builder operates by taking an official Microsoft ISO (WIM/ESD) and using Microsoft’s own tooling — primarily DISM for servicing and oscdimg.exe from the Windows ADK to create bootable ISOs. The current PowerShell script orchestrates these tools to:- Mount and extract the chosen image edition from the source ISO.
- Service the mounted image: remove packages, scheduled tasks, registry entries and policies corresponding to targeted inbox apps and features.
- Recompress the image with DISM using /Compress:recovery (LZX) to minimize output ISO size.
- Recreate a bootable ISO with oscdimg.exe and optionally include an autounattend.xml to automate OOBE behavior (for example, bypassing Microsoft Account enforcement). (github.com) (github.com)
Tiny11 vs Tiny11 Core
- Tiny11 (regular): aims to keep Windows Update, WinSxS servicing paths, and the component store intact so the image remains updateable and serviceable after installation. This is the recommended profile for production‑like use.
- Tiny11 Core (experimental): strips WinSxS and many servicing hooks to produce dramatically smaller images (examples cited in public posts show ISOs as small as ~2GB and on‑disk footprints of ~3.3GB). Core is designed for VMs, test rigs, or air‑gapped appliances — not consumer/laptop daily drivers. It commonly disables Windows Update and Defender in some configurations; that makes it unsafe for internet‑facing production systems. (windowscentral.com)
Benefits and likely use cases
- Reclaim storage and speed on low‑end devices: Removing unneeded inbox apps reduces disk usage and background processes, which can noticeably improve responsiveness on older hardware.
- Deterministic lab and test images: For developers and QA teams a reproducible, minimal base simplifies test matrices and reduces noise during driver and application validation.
- Kiosk and embedded devices: When you need a single‑purpose machine with minimal attack surface and no extraneous UI prompts, a Tiny11‑built image can be an efficient starting point.
- Privacy‑minded personal installs: Some users prefer to avoid AI assistant integrations and embedded cloud clients entirely; Tiny11 allows those choices at build time rather than through after‑the‑fact removals. (ntdotdev.wordpress.com)
Real risks, caveats, and things to test
Security and updateability (the big one)
Removing servicing components, Windows Update hooks, Defender or other security infrastructure (as seen in some Tiny11 Core configs) materially increases risk. Without reliable update channels, systems will age insecurely and be vulnerable to new threats. For general use, retain the serviceable Tiny11 profile; treat Core as isolated test‑only media. (windowscentral.com)Supportability and warranty implications
Modified images are custom images. Vendor and Microsoft support teams commonly treat heavily altered builds as out of scope for standard warranty or support agreements. In enterprise contexts, custom images should be coordinated through the usual image pipeline (SCCM, MDT, Intune) and validated with procurement and support teams.Reinstallation “whack‑a‑mole”
Microsoft’s Store and servicing behavior can attempt to reinstall removed inbox apps after feature updates. Tiny11 adds registry and blocking tweaks to reduce reappearance, but this remains a moving target; expect to reapply or update build routines as Microsoft changes Store and servicing behavior. (github.com)Hardware/driver quirks
Aggressive pruning can inadvertently remove optional platform components some drivers or OEM customizations rely upon — audio, cameras, or vendor utilities can behave strangely. Always validate device drivers and peripheral functionality in a test VM and on representative hardware.Supply‑chain risk
Building from third‑party prebuilt Tiny11 ISOs can expose you to tampered media. The safest approach is to run the builder locally using an official Microsoft ISO as the source and verify checksums. Never deploy downloaded, unsigned custom ISOs on production devices without auditing.Unverified or hyperbolic claims
Community anecdotes sometimes assert extreme outcomes (for example, claims of running Windows on absurdly low RAM figures). Treat such anecdotes as unverified until reproduced in your environment; report and validate thoughtfully. Tiny11 developer posts and community threads are useful, but do not substitute for lab validation.Practical guidance: how to build a Tiny11 ISO safely (concise, step‑by‑step)
- Download an official Microsoft Windows 11 ISO for your desired edition and build. Verify checksums.
- Clone the Tiny11 Builder repository and inspect the PowerShell scripts (tiny11maker.ps1 and tiny11Coremaker.ps1). Confirm you understand the options. (github.com)
- Install the Windows ADK (if you plan to produce a bootable ISO) to obtain oscdimg.exe. (github.com)
- Open PowerShell as Administrator and set execution policy: Set-ExecutionPolicy Unrestricted -Scope Process. (github.com)
- Run the builder in a controlled environment (VM first): powershell -f C:\path\to\tiny11maker.ps1 -ISO -SCRATCH <scratch_path>. Follow prompts to select SKU, architecture and the desired removals. (github.com)
- Test the resulting ISO in multiple scenarios: clean install in a VM, in‑place upgrade simulation, driver installs, and a full Windows Update cycle to validate the servicing posture.
- For production machines, prefer the regular tiny11 profile (serviceable). Reserve Tiny11 Core for disposable VMs, lab images, or air‑gapped devices. (windowscentral.com)
- Keep a recovery image, backups, and the original official ISO and license keys available for rollback. Document every component removed so you can replicate or restore functionality later.
Testing checklist (short, scannable)
- Boot and POST success on target hardware.
- Network connectivity and driver stability (Ethernet/Wi‑Fi).
- Audio input/output and camera checks.
- Windows Update behavior and Defender presence (if you kept them).
- Reinstallation attempts by Microsoft Store after a feature update.
- Compatibility of enterprise management agents (Intune, SCCM, third‑party AV).
Legal and enterprise considerations
- Rebuilding an ISO does not alter licensing: proper activation and licensing remain required. Modifying images may affect vendor support; consult legal and procurement teams before mass deployment.
- For enterprise baselines, the recommended approach is still to integrate debloating into approved imaging workflows (SCCM/MDT/Intune pipelines) and maintain a controlled patch lifecycle. Tiny11 is a useful community tool, but by itself it does not substitute for formal image management and compliance processes.
The cat‑and‑mouse reality: how long will removal persist?
Expect an ongoing cycle: Microsoft updates servicing and Store behavior; community builders update their scripts; Microsoft may bake deeper provisioning into feature updates; builders respond again. Tiny11’s new registry and uninstall tactics reduce reappearance risk, but long‑term persistence demands maintenance and periodic re‑builds or updated blocking techniques. For admins, that means treating custom image upkeep as an operational task — schedule rebuilds and retesting after each major Windows update. (github.com)Expert takeaways: strengths, tradeoffs, and best practices
- Strengths: Tiny11 Builder is transparent, uses Microsoft tooling, and gives fine‑grained control over what a fresh Windows 11 install contains. The move to PowerShell improves portability across languages and architectures and simplifies reproducibility. LZX compression materially reduces ISO distribution size for constrained environments. (github.com) (github.com)
- Tradeoffs: Aggressive stripping can break update chains, security features, and driver compatibility. The Tiny11 Core variant demonstrates what’s possible at the extreme, but its NO‑SERVICEABILITY posture makes it a lab tool, not a daily‑use OS. (windowscentral.com)
- Best practices: Build from official ISOs locally, keep the serviceable profile for production, test in VMs before touching hardware, document removals and rollback steps, and treat custom images as part of your operational lifecycle rather than a one‑time tweak.
Final verdict
Tiny11’s September 2025 update is a practical, well‑scoped evolution: it turns an ad‑hoc tradition of post‑install debloating into a repeatable ISO‑level workflow that explicitly addresses Microsoft’s recent AI and mail client additions. For hobbyists, testers, embedded projects and labs, the new builder is compelling: it’s transparent, uses MS tooling, and offers substantial space savings thanks to recovery/LZX compression. (ntdotdev.wordpress.com) (github.com)That said, the updated builder is not a universal fix. Organizations and mainstream users must weigh the serviceability and security tradeoffs carefully and prefer the regular Tiny11 profile unless they have a controlled, air‑gapped, or disposable VM use case for Core. The real power here is choice: Tiny11 hands the image‑creation decision back to the user, and with that power comes responsibility — test thoroughly, document changes, and deploy conservatively. (windowscentral.com)
Tiny11 is available on its public repository where the release notes, scripts and usage instructions are published; the developer recommends building your own image from an official ISO rather than using old prebuilt ISOs. (github.com) (ntdotdev.wordpress.com)
Conclusion: For those who value a minimal, deterministic Windows 11 with no Copilot, no bundled Teams, and no forced new Outlook client, Tiny11’s new builder provides a robust, transparent, and technically polished way to produce it — but the safety and support tradeoffs should dictate where and how you use it. (github.com)
Source: TweakTown Tiny11 declares war on AI: build a DIY Windows 11 install with no Copilot, Teams or other bloat
