In September 2025, the open-source Tiny11 project released an updated PowerShell builder that targets Windows 11 version 25H2. The new scripts let you carve out dozens of preinstalled apps, bypass the Microsoft Account sign-in during setup, and disable telemetry—all from an official Windows ISO you supply yourself. Neowin first reported the release, highlighting its appeal as Windows 10 pushes toward its October 14 end of support.

A Closer Look at the 25H2 Builder

The heart of the project is tiny11maker.ps1, a script that mounts an official Windows 11 25H2 ISO, removes unwanted components with DISM, applies registry tweaks and an unattended answer file, compresses the image, and spits out a smaller, leaner ISO. A more aggressive sibling, tiny11coremaker.ps1 (also called nano11), goes further—stripping Windows Defender, update components, and WinSxS entries—but leaves the resulting system unable to receive updates. The project explicitly recommends the standard maker for any machine you plan to use regularly.

The latest refresh adds targeted removals for Microsoft's current push toward AI and cloud services:

  • Copilot and related registry protections that prevent reinstallation
  • The new Outlook and Teams app packages
  • Xbox features, News & Weather, and many other UWP apps
  • Scheduled telemetry tasks and specific telemetry services (you can toggle these on or off)

Additionally, a new unattended answer file is bundled into the repository. During OOBE, it automatically bypasses the Microsoft Account requirement, letting you create a local user account without any network trickery. The script also applies DISM recovery compression, which the maintainers say reduces final ISO size considerably.

Who Stands to Benefit—and Who Should Stay Away

For home users with older hardware, this is a practical bridge. Windows 11’s TPM 2.0 and CPU generation checks lock out millions of otherwise capable PCs. On those machines, a Tiny11-built image can deliver a modern desktop with dramatically lower RAM and storage demands—sometimes fitting comfortably on 2–4 GB of RAM and a 32 GB drive. And because the builder works from your own genuine ISO, you can keep the machine running without buying new hardware as Windows 10 support expires.

Privacy-conscious users will appreciate the transparent telemetry controls. Instead of hunting through obscure settings menus, the script presents a straightforward choice to disable data-collection tasks. The local account flow also means you never have to link your Windows install to a cloud identity.

For power users and IT pros, the builder offers a repeatable way to create minimal images for virtual machines, test environments, or single-purpose kiosks. The core/nano variants, in particular, produce tiny footprints ideal for ephemeral VMs where long-term updateability isn't a concern.

However, there are hard trade-offs:

  • Security updates vanish if you choose the nano/core script. Those images will quickly become vulnerable without manual, surgical patching. Even the standard maker disables some telemetry—but it leaves Windows Update intact, so you will still receive monthly fixes.
  • Compatibility can be unpredictable. Community reports show that certain Surface devices and older laptops may fail during installation or drop drivers after the stripping process. Expect to manually hunt down storage controllers, Wi-Fi, and GPU drivers.
  • Legal risk looms. Using the builder on your own ISO for personal use sits in a gray area many enthusiasts accept, but redistributing modified ISOs clearly violates Microsoft’s license terms. Prebuilt downloads floating around forums often contain malware or activation cracks. The only safe path: build it yourself from an official, checksum-verified ISO.
  • Microsoft won’t support you. Running Windows 11 on unsupported hardware or from a modified image cuts you off from official channels. If something breaks, you’re on your own.

Put simply, if you need guaranteed updates, enterprise compliance, or a plug-and-play experience, the official upgrade route—or Windows 10’s Extended Security Updates for eligible devices—remains the only sensible choice.

From Windows 10’s Sunset to Tiny11’s Rise

The clock has been ticking since Microsoft announced Windows 11’s hardware floor. TPM 2.0, Secure Boot, and eighth-gen Intel or Ryzen 2000 processors locked out a sizable chunk of the installed base, while the operating system itself piled on cloud-connected features that many users found intrusive. Tiny11 first emerged as a community answer to that unease: a transparent, script-based method to peel away Microsoft’s bloat without relying on mystery tools. Early builds focused on Windows 11 22H2 and 23H2; the jump to 25H2 signals that the project intends to keep pace with feature updates.

The September 2025 update arrives just weeks before Windows 10’s end-of-support deadline, when millions of devices will suddenly stop receiving security patches. Microsoft’s official guidance points users toward new hardware or ESU enrollment, but for home users on a tight budget, Tiny11 offers a third path—one that demands technical skill and risk tolerance.

If You Choose to Build: A Safety-First Workflow

For those willing to accept the trade-offs, follow these steps to minimize exposure:

  1. Download the official Windows 11 25H2 ISO directly from Microsoft. Verify its SHA-256 checksum before proceeding.
  2. Clone or download the Tiny11 builder from NTDEV’s official GitHub repository. Read the README and release notes thoroughly.
  3. Run the script locally on a machine you control. Open PowerShell as Administrator, set the execution policy to the bare minimum for the session (Set-ExecutionPolicy Bypass -Scope Process), and inspect the script contents before execution.
  4. Use only the standard tiny11maker.ps1 for any system you intend to use daily. Skip nano/coremaker unless you fully accept the loss of updates and Defender.
  5. Back up your existing machine with a full disk image. Keep a recovery USB made from an unmodified Microsoft installer nearby.
  6. After building the ISO, burn it to a USB drive with Rufus or the Media Creation Tool. Boot the target PC and run through the installation. When it’s done, immediately check Windows Update, confirm that Defender is present (if you want it), install any missing drivers, and verify activation with your own valid license.
  7. Never share your custom ISO. Builds with pre-injected activation keys or third-party payloads are legally problematic and often dangerous.

Expect glitches. On one test machine, Wi-Fi may work out of the box; on another, you might need to sideload an Intel driver. If the stripped image refuses to boot or throws storage errors, you may have to fall back to the standard Windows installer.

What’s Next for the Debloat Movement

Tiny11’s 25H2 update comes at a pivotal moment. With Windows 10 exiting support, more users will be forced to make a choice: buy compatible hardware, pay for ESU, or turn to community tools. Microsoft’s tightening grip on cloud accounts and AI integration—Copilot is now baked into the taskbar—will likely spur more hobbyist projects like this one. The real test will be longevity. If future Windows updates start re-enabling removed components or blocking the unattended bypass, the Tiny11 maintainers will need to adapt quickly. For now, the 25H2 builder delivers what it promises: a lean, local-account-friendly Windows 11 for the hands-on crowd. Just know what you’re getting into before you hit Run.