How to Build a Windows 11 25H2 ISO Without Copilot Using tiny11builder

Microsoft bundles Copilot deeply into Windows 11 starting with 25H2. While you can toggle it off after install, a cleaner approach is to prevent Copilot (and other unwanted inbox apps) from ever landing on the system. That’s where tiny11builder comes in. This open-source PowerShell script lets you service official Windows images and strip out Copilot, Outlook, Teams, and more before deployment.

What You’ll Need

• Official Windows 11 25H2 ISO/ESD (any language, x64/arm64)
  → Download directly from Microsoft’s Windows 11 page.
• Windows ADK (only if you want a bootable ISO)
  → Provides oscdimg.exe which tiny11builder uses to finalize the ISO.
• tiny11builder
  → GitHub: ntdevlabs/tiny11builder
• Admin access to PowerShell 5.1+
  → Needed to run the script with DISM servicing commands.
• Ample resources
  → Fast SSD and plenty of RAM recommended. Recovery compression saves space but increases build time and memory load.
• Optional VM
  → Always test the custom ISO in a virtual machine before real deployment.

Method 1 — Build a 25H2 ISO With Copilot Pre-Removed (Recommended)

This method ensures Copilot never provisions on your devices.

1- Mount or extract the Windows ISO/ESD you downloaded.

2- Install Windows ADK if you plan to build a bootable ISO.

3- Download and extract tiny11builder locally.

4- Open PowerShell as Administrator and allow script execution: Set-ExecutionPolicy Bypass -Scope Process

5- Run the script and point it to your ISO/ESD files: powershell -f C:\Path\to\tiny11maker.ps1

6- Select your edition (SKU) and choose the standard “tiny11” option.

• Avoid Core unless you specifically want a lab-only, non-serviceable image.

7- Confirm removal set → Copilot, Teams, and new Outlook are among the defaults.

8- Enable recovery compression when prompted for a smaller final ISO.

9- Let the script build and generate the ISO. It will also inject an autounattend.xml for OOBE tweaks (like bypassing Microsoft Account enforcement).

10- Test in a VM. Verify updates, Copilot absence, and app/driver compatibility.

11- Deploy to hardware once validated. Document the script version used for reproducibility.

Method 2 — Disable Copilot After Installation (Less Durable)

If you already installed 25H2, you can still suppress Copilot:

1. Go to Settings > System > Copilot → toggle it off.
2. In Settings > Apps > Optional features, uninstall Copilot/AI components.
3. Validate. Some shell stubs (Win + C, Start menu references) may persist.
4. Recheck after each cumulative or feature update — Copilot may return.

Method 3 — Maintain Clean Builds Over Time

• Keep tiny11builder up to date; new versions expand removal lists and safeguards.
• Periodically rebuild your ISO with the latest Windows media.
• Avoid random third-party ISOs — tiny11builder builds from official Microsoft sources with transparent logs.

Optional: tiny11 Core (Labs & VMs Only)

• Produces an ultra-small, non-serviceable image.
• Windows Update and feature servicing will not work.
• Best reserved for throwaway VMs, kiosks, or constrained testbeds.

Notes & Caveats

• Not supported by Microsoft — customized images may break support contracts.
• Licensing/activation remains unchanged; you still need valid keys.
• Settings references may linger (e.g., Copilot toggles), though the features are gone.
• Always keep a recovery path — backup ISOs, and know how to restore stock media.

✅ Bottom line: Pre-removing Copilot with tiny11builder gives you a cleaner baseline, prevents reinstalls through updates/Store, and simplifies deployment. For ongoing use, keep your build process documented and rebased against each new Windows 11 release.