Windows 11’s inbox app pile just got a new nemesis: Tiny11’s updated builder can now strip Copilot, the new Outlook client, Teams, and a long roster of built‑ins from a Windows 11 image — and the change is explicitly framed as a “25H2‑ready” rebuild that shrinks install size and prevents much of the usual bloat from migrating during upgrades. (github.com)
Windows 11 ships with dozens of inbox apps and tightly integrated services that many users never open but that still consume storage, background memory, autoupdate cycles, and — for some people — a level of unwanted telemetry and UI clutter. For power users and administrators who want a lean, deterministic image, that default state has long been a headache and an invitation for community projects that rebuild or scrub the install media itself. Tiny11 is one of the best‑known community approaches: a script‑driven builder that takes an official Microsoft ISO, removes selected packages and components, and outputs a smaller, debloated installer. (github.com)
The recent refresh to Tiny11’s builder — promoted by its maintainer NTDev — adds several substantive items: explicit removal routines for Copilot, the new Outlook for Windows client, and Teams; general compatibility with Windows 11 25H2 images; and optimizations that produce smaller final ISOs via recovery compression during image processing. These are not cosmetic tweaks: they change what a fresh install contains from the bottom up. (github.com, ntdev.blog)
Teams and Outlook are particularly sensitive: many users need them for work, whereas others consider the inbox variants unnecessary. By making them optional at build time, Tiny11 shifts the decision from Microsoft’s installer to the user or administrator building the image. (github.com, betanews.com)
There are also specific, reproducible complaints in community channels: for instance, users who installed Core variants reported that microphone access or certain system features were lost after applying certain tweaks or updates. Those posts are a reminder that extreme debloating can have irreversible or difficult‑to‑fix side effects on consumer hardware.
But the downsides are real and measurable. The biggest risks are reduced serviceability, the potential to break integrated features, and the supply‑chain hazard of unofficial ISOs. The right decision is context sensitive: Tiny11 is excellent for controlled deployments, VMs, experimenters, and small‑disk systems; it is a poor match for workstations that must remain fully supported, patched, and recoverable without rebuilding images. Administrators and careful users should adopt a conservative approach: build from official ISOs, prefer the serviceable Tiny11 profile for end‑user machines, and test thoroughly before wider rollouts. (ntdev.blog)
Tiny11’s latest update is a useful reminder: many of the annoyances in modern desktop OSes are solvable, but the cure is rarely risk‑free. For enthusiasts who prize control and minimalism, the new builder’s ability to nuke Copilot, the new Outlook, Teams, and many other inbox apps is a powerful, pragmatic tool. For everyone else, the right path is to weigh the performance and privacy gains against loss of serviceability, support considerations, and potential reinstall friction — and to test thoroughly before committing to a debloated baseline. (github.com, ntdev.blog)
Source: xda-developers.com One of the best ways to remove Windows 11 bloatware can now hit Copilot, Outlook, and Teams
Windows 11 ships with dozens of inbox apps and tightly integrated services that many users never open but that still consume storage, background memory, autoupdate cycles, and — for some people — a level of unwanted telemetry and UI clutter. For power users and administrators who want a lean, deterministic image, that default state has long been a headache and an invitation for community projects that rebuild or scrub the install media itself. Tiny11 is one of the best‑known community approaches: a script‑driven builder that takes an official Microsoft ISO, removes selected packages and components, and outputs a smaller, debloated installer. (github.com)The recent refresh to Tiny11’s builder — promoted by its maintainer NTDev — adds several substantive items: explicit removal routines for Copilot, the new Outlook for Windows client, and Teams; general compatibility with Windows 11 25H2 images; and optimizations that produce smaller final ISOs via recovery compression during image processing. These are not cosmetic tweaks: they change what a fresh install contains from the bottom up. (github.com, ntdev.blog)
What Tiny11 now removes (and what that means)
The app and component list
Tiny11’s published removal list is comprehensive. The builder now explicitly omits a long set of inbox apps and services, including but not limited to:- Clipchamp, News, Weather
- Xbox apps (with Xbox Identity Provider sometimes left to enable optional reinstall)
- GetHelp, GetStarted, 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
- Edge, OneDrive, Copilot, and the new Outlook client
- Microsoft Teams (consumer/home variant and related packages may be culled)
Why removing Copilot, Outlook, and Teams is notable
Copilot and the “new Outlook” represent Microsoft’s push toward AI‑driven and web‑backed experiences. Because they tie into cloud services and newer frameworks, they also add bloat both on disk and in background services. Removing them from the base image reduces surface area (less code to auto‑update), conserves disk space, and eliminates the in‑box prompt paths that often nudge users into cloud‑centric flows.Teams and Outlook are particularly sensitive: many users need them for work, whereas others consider the inbox variants unnecessary. By making them optional at build time, Tiny11 shifts the decision from Microsoft’s installer to the user or administrator building the image. (github.com, betanews.com)
Technical underpinnings: how the builder works
Microsoft tooling, PowerShell, and DISM
Tiny11’s builder is a PowerShell script that operates against an official Microsoft Windows 11 ISO. It leverages standard Microsoft servicing tools such as DISM for image servicing and oscdimg.exe from the Windows ADK to produce bootable ISOs. The maintainer stresses a preference for Microsoft tooling rather than third‑party binaries — the script manipulates the Windows image (WIM/ESD), removes packages, and writes a new ISO. (github.com)25H2 support and recovery compression
The update adds explicit support for 25H2 releases and adapts the pipeline to handle both WIM and ESD formats and multiple architectures. One of the space‑saving changes is the usage of DISM’s recovery compression option during deployment, which yields smaller ISOs without changing the base OS behavior for typical desktop use. That compression mode is a practical win for users constrained by storage or those who want lighter install media.Tiny11 Core vs regular Tiny11 (serviceability tradeoffs)
Tiny11’s project contains at least two modes:- Regular Tiny11 — a debloated but serviceable Windows 11 image that preserves servicing paths like the component store (WinSxS) so future updates and features remain manageable.
- Tiny11 Core — an extreme, experimental variant that removes WinSxS and other servicing infrastructure to pack the image down even further. Core images can be unserviceable: you cannot add back components or apply certain updates reliably without rebuilding. This distinction matters: Core is useful for lightweight VMs or test rigs, but it is not a recommended daily driver for systems that must remain patched through official Windows Update workflows. (github.com)
Benefits for users and admins
- Smaller install footprint. Making Copilot, Outlook, Teams and other inbox apps optional reduces disk use and produces significantly smaller ISOs, which is valuable for low‑capacity storage devices or reduced‑bandwidth deployments.
- Cleaner defaults. Fresh installs don’t present Microsoft’s default app clutter to end users; admins can preselect precisely what they want present. (ntdev.blog)
- Reduced background churn. Fewer auto‑updating inbox apps means fewer update cycles, less network chatter, and fewer services running in background memory.
- Choice and control. Users who prefer third‑party solutions or browser‑based services can install only their chosen clients rather than keeping the inbox app and disabling it later. (ntdev.blog)
Real risks and important caveats
The advantages above are real, but the approach carries measurable tradeoffs and hazards. A responsible evaluation must list them clearly.1) Serviceability and Windows Update complications
Removing core servicing components or the Windows Component Store (WinSxS) — as Tiny11 Core does in its extreme variant — can break the standard Windows servicing model. That makes future updates, language additions, or feature patches unreliable or impossible without a full rebuild. Administrators who need to keep systems patched will find this especially problematic. The official Tiny11 notes and community reports repeatedly flag this caveat. (github.com)2) Broken or missing features after removal
Some Microsoft features and integrations expect certain inbox apps or system components to exist. For example, removing Edge and Copilot may impact search or File Explorer UI elements that surface web results. Removing Mail/Calendar affects default handling of mailto: links and OOBE flows for account setup. Users who remove apps must plan for reinstallation and understand the callouts where a missing component may change expected behavior. (github.com, ntdev.blog)3) Reinstallation friction and lost data
Not all removed components reinstall cleanly or preserve user data. Reinstating a removed inbox app sometimes requires a retail install from Microsoft Store, winget, or a manual package installation. In enterprise environments, IT should test the process for reinstalling required tools before wiping them out of a base image. Community threads also show intermittent issues where certain packages (Outlook/Dev Home) can reappear unexpectedly after update—suggesting complex ties between packages and retention logic.4) Security and supply‑chain risk (unofficial media)
Tiny11 modifies official ISOs and produces a new installer outside Microsoft’s signed distribution channels. That approach is functionally powerful but introduces supply‑chain risk if users fetch prebuilt images from untrusted sources. The Tiny11 project itself advocates building from an official Microsoft ISO using the provided PowerShell scripts; this practice reduces tampering risk because the only non‑Microsoft executable the script expects is oscdimg from the ADK. Still, users who download prebuilt third‑party ISOs (or who grab copies from file‑sharing sites) are exposed to malware and tampered installers. Always build from a fresh, official ISO when possible and verify checksums. (github.com, ntdev.blog)5) Legal and support considerations
Using a modified Windows image with corporate hardware can violate organizational policies or breach vendor support agreements. Vendors and Microsoft support channels commonly decline warranty or support for systems that run heavily altered builds. Enterprises should use debloating only after validating with procurement, security, and software asset teams. Community projects like Tiny11 are made for enthusiasts and controlled deployments, not universal enterprise rollouts.Practical guide: safe ways to get the benefit without the risk
For users and admins who want the clean desktop delivered by Tiny11 but want to avoid the biggest hazards, follow a conservative, tested workflow.1. Build from your own official ISO (recommended)
- Download the official Windows 11 ISO from Microsoft.
- Clone the Tiny11 builder repository and review the PowerShell scripts. The maintainer’s repository deliberately uses DISM and the Windows ADK rather than third‑party binaries. (github.com, ntdev.blog)
- Run the builder locally to generate a new ISO. Avoid using third‑party prebuilt images.
2. Use the regular Tiny11 profile, not Core, for production machines
- Choose the serviceable variant of Tiny11 (the normal “tiny11” mode) so you preserve the component store and Windows Update paths. Core is great for experiments and VMs but not for primary devices that must receive security updates. (github.com)
3. Create recovery and restore points before making changes
- Always keep a tested image backup and a recovery drive before deploying a modified install. Test Windows Update and essential applications in a controlled environment (VM or test device) first.
4. Keep a reinstall plan for removed apps
- If your workflow requires Copilot, Teams, or Outlook later, verify how to reinstall them: winget, Microsoft Store, or enterprise deployment packages. Document the steps so a reinstall is predictable and repeatable. Community postings show that sometimes Outlook or Dev Home can reappear or behave unexpectedly after updates — plan accordingly.
5. Consider alternatives where appropriate
If you only want to reclaim disk space or reduce background processes without rebuilding the ISO:- Use curated tools like Talon, Win11Debloat, O&O AppBuster, or PowerShell Appx removal commands to remove inbox apps post‑install. These tools let you remove many apps safely without touching the component store. They’re not identical to Tiny11’s approach but offer a lower‑risk path for many users.
Community reports and real‑world outcomes
Community testing shows a range of practical outcomes. Enthusiasts praise Tiny11’s speed and compactness — some low‑power devices run markedly cooler and more responsive — but there are consistent warnings from users who tried extreme modes and later struggled with missing functionality or updates. Several forum posts and threads document both success stories (significant boot and runtime improvements) and failure modes (audio/microphone issues or broken drivers after aggressive pruning), underscoring the need to test before mass deployment.There are also specific, reproducible complaints in community channels: for instance, users who installed Core variants reported that microphone access or certain system features were lost after applying certain tweaks or updates. Those posts are a reminder that extreme debloating can have irreversible or difficult‑to‑fix side effects on consumer hardware.
How to evaluate if Tiny11 is right for you
- Choose Tiny11 if you:
- Need very small, self‑contained images for VMs or kiosks.
- Want full control over what a fresh install contains and have the technical knowledge to rebuild and maintain images.
- Are comfortable rebuilding images from Microsoft ISOs and validating updates manually. (github.com)
- Avoid Tiny11 Core for daily machines if you:
- Rely on automatic Windows Update and peace‑of‑mind security patching.
- Need vendor or Microsoft‑backed support for desktop machines.
- Lack backups or the ability to rebuild quickly.
Final analysis: powerful tool, not a universal cure
Tiny11’s update that removes Copilot, the new Outlook, and Teams is a meaningful advance for users who want lightweight, bespoke Windows installs. The builder’s shift to PowerShell, explicit 25H2 compatibility, and the addition of recovery compression are sensible engineering improvements that make building smaller images easier and more reliable. That capability gives users practical benefits: less disk use, fewer in‑box services, and a cleaner initial user experience. (github.com)But the downsides are real and measurable. The biggest risks are reduced serviceability, the potential to break integrated features, and the supply‑chain hazard of unofficial ISOs. The right decision is context sensitive: Tiny11 is excellent for controlled deployments, VMs, experimenters, and small‑disk systems; it is a poor match for workstations that must remain fully supported, patched, and recoverable without rebuilding images. Administrators and careful users should adopt a conservative approach: build from official ISOs, prefer the serviceable Tiny11 profile for end‑user machines, and test thoroughly before wider rollouts. (ntdev.blog)
Quick checklist before using Tiny11
- Obtain the official Windows 11 ISO directly from Microsoft.
- Clone and inspect the Tiny11 builder scripts locally. (github.com)
- Select the regular (serviceable) build unless you have a specific Core use case.
- Build the ISO yourself; do not download a prebuilt image from untrusted sources. (ntdev.blog)
- Create backups and a recovery plan before deploying to any machine used for daily work.
Tiny11’s latest update is a useful reminder: many of the annoyances in modern desktop OSes are solvable, but the cure is rarely risk‑free. For enthusiasts who prize control and minimalism, the new builder’s ability to nuke Copilot, the new Outlook, Teams, and many other inbox apps is a powerful, pragmatic tool. For everyone else, the right path is to weigh the performance and privacy gains against loss of serviceability, support considerations, and potential reinstall friction — and to test thoroughly before committing to a debloated baseline. (github.com, ntdev.blog)
Source: xda-developers.com One of the best ways to remove Windows 11 bloatware can now hit Copilot, Outlook, and Teams