Tiny11 Windows 11 26H2: How to Build a Clean, Stripped OS Image

Deploying Tiny11 Windows 11 26H2 solves the aggressive system overhead introduced in Microsoft’s latest update cycle. Default enterprise and consumer installations now regularly load between 3.8 GB and 4.6 GB of RAM at idle, driven by background Copilot telemetry daemons, persistent Edge WebView2 host containers, and sponsored AppX packages. For homelabs, staging VMs, older hardware, and minimal production workstations, this overhead is unacceptable.

The solution is not downloading dubious pre-activated ISOs from untrusted file hosts. Instead, administrators can build a custom, secure Tiny11 Windows 11 26H2 image using official open-source automation scripts based on Microsoft’s native Deployment Image Servicing and Management (DISM) engine.

What Makes Windows 11 26H2 Bloated Out of the Box?

When you perform a standard installation of Windows 11 26H2, the NT kernel loads an extensive chain of non-essential services before any user workload launches:

• Edge WebView2 Runtimes: Background processes running continuously to supply dynamic widgets and taskbar search feeds.
• Staged Consumer AppX Provisioning: OEM-sponsored software and entertainment applications registered in the default user profile skeleton.
• Diagnostic Tracking (DiagTrack): Connected User Experiences and Telemetry services actively queuing logging events.
• Windows Recall & AI Subsystems: Background snapshot indexes that consume CPU cycles and non-paged memory pools.

A properly debloated Tiny11 installation removes these non-essential layers at the image level while preserving core servicing libraries (WinSxS), leaving Windows Update and driver installation fully operational.

Prerequisites for Building Tiny11 Windows 11 26H2

To compile your custom image securely without third-party binary injection, prepare the following components:

• Official Windows 11 26H2 ISO: Downloaded directly from Microsoft’s official portal.
• Automated Builder Script: Clone the official open-source repository from NTDEV tiny11builder on GitHub.
• Storage Space: At least 25 GB of free NVMe or SSD space for mounting and image recombination.
• Windows Assessment and Deployment Kit (ADK): Required for the oscdimg.exe utility to compile the UEFI bootable ISO.

Infrastructure Note: When testing unattended deployment scripts and custom OS images for client environments, staging builds on dedicated cloud servers saves local drive endurance. Testing environments for this guide were verified on a high-speed NVMe KVM instance via Erahost Cloud Infrastructure.

Step-by-Step: Compiling Tiny11 26H2 via PowerShell

Follow these precise steps in an elevated terminal to generate your ISO:

Step 1: Mount the Official 26H2 ISO

Mount your downloaded ISO image by right-clicking and selecting Mount, or execute via PowerShell:

Mount-DiskImage -ImagePath "C:\ISOs\Windows11_26H2_English_x64.iso"

Note the assigned virtual drive letter (for example, E:).

Step 2: Initialize the Builder Script

Extract the tiny11builder directory to an SSD directory such as C:\tiny11. Open PowerShell as Administrator, adjust execution rights, and run the compilation script:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
cd C:\tiny11
.\tiny11creator.ps1

Step 3: Target Drive Selection and Index Extraction

The script prompts for the mounted drive letter. Enter E (without a colon). Next, select the SKU index corresponding to your target edition:

• Index 1: Windows 11 Home
• Index 6: Windows 11 Pro (recommended for networking and Hyper-V support)

Step 4: Image Stripping and Component Scrubbing

The builder executes the following DISM routines automatically:

dism /Mount-Image /ImageFile:C:\tiny11\scratch\install.wim /Index:1 /MountDir:C:\tiny11\mount
dism /Image:C:\tiny11\mount /Remove-ProvisionedAppxPackage /PackageName:...
dism /Unmount-Image /MountDir:C:\tiny11\mount /Commit

The script cleans out Cortana, News, Weather, Solitaire, Xbox telemetry hubs, and Edge update agents while keeping the servicing stack, Microsoft Store, and Windows Security (Defender) intact.

Step 5: ISO Rebuilding via oscdimg

The tool automatically bundles the clean tree into a bootable UEFI-compliant ISO image (tiny11_26h2.iso) inside your working folder.

Benchmark Comparison: Default 26H2 vs. Tiny11 26H2

After a fresh installation on an identical testbed (AMD Ryzen 5, 16 GB DDR4, NVMe SSD), the performance differences are immediate:

Servicing and Security: What You Need to Know

• Monthly Cumulative Updates: Function normally via Windows Update without breaking OS integrity. Because Tiny11 utilizes native DISM package removal rather than raw file deletion, update pipelines remain intact.
• Microsoft Store Access: Remains operational, allowing users to reinstall specific tools (like Terminal or Calculator) on demand.
• Local Account Security: Bypasses forced Microsoft Account bindings without registry corruption.

Related Guides and System Optimization

Following this Tiny11 Windows 11 26H2 deployment workflow ensures a lightweight, stable, and telemetry-free environment. Explore our related resources:

• Clean bloatware on live systems: Windows Utilities & Deep Clean Workflows
• Bypass legacy CPU hardware blocks: POP4.2 Guide: How to Run Windows 11 on Older CPUs
• Explore system utilities: Operating Systems Management & In-Depth Guides