A new script called nano11 can compress a full Windows 11 installation into a 2.29GB ISO — a fraction of the original 7GB — by surgically removing everything from Xbox games and Solitaire to Windows Update and Defender. Created by NTDev, the developer behind the popular tiny11, nano11 is an open-source PowerShell pipeline that leverages Microsoft’s own DISM tools and recovery compression to achieve extreme size reductions. But this radical diet comes with severe trade-offs: the resulting system is intentionally unserviceable, can’t receive security patches, and is meant only for ephemeral virtual machines and test labs. Here’s a deep dive into how it works, why it’s technically impressive, and why you shouldn’t run it on your main PC.

The Birth of an Ultra-Compact Windows 11

The frustration with Windows 11’s ever-growing disk footprint has spawned a cottage industry of community-driven debloat projects. NTDev’s tiny11 became a go-to for enthusiasts seeking a leaner OS without sacrificing serviceability — it removes inbox apps and applies compression while keeping Windows Update functional. Nano11 is the next, more extreme evolution. As NTDev puts it, the script includes “all the essentials, none of the fluff,” and is explicitly labeled as experimental and not intended for daily drivers. The project documentation warns that it removes the Windows Component Store (WinSxS) and core services, making the image unserviceable via standard update mechanisms. The 2.29GB figure comes from a build that started with a stock Windows 11 Insider build 26200 ISO weighing in at 7.04GB.

How nano11 Shrinks Windows 11 to 2.29GB

Nano11 isn’t a new edition of Windows; it’s a reproducible, scripted process that combines three technical levers. First, it mounts an official Windows 11 ISO offline and uses DISM (Deployment Imaging Service and Management Tool) to strip out packages, features, drivers, languages, fonts, and inbox apps. This removal step is aggressive — in its most extreme profile, it also neutralizes the servicing stack and WinSxS, which are normally responsible for handling updates and feature installations.

Second, the script re-exports the image using recovery-style compression with LZMS/LZX algorithms. These algorithms achieve much higher compression ratios than the default XPRESS modes, but at the cost of increased CPU and memory usage during export and potentially longer install times. This is the multiplier that drives the headline-grabbing ISO size.

Third, post-install trims further reduce the live footprint. The builder can disable hibernation, remove the pagefile, and apply CompactOS or other on-disk compressions. Together, these steps can shrink an installed system to just a few gigabytes. The process uses oscdimg.exe from the Windows ADK to generate a bootable ISO, ensuring the result is still recognizable as a standard Windows installer.

The Harsh Reality: What nano11 Removes

Nano11’s removal list reads like a catalog of everything most users expect from a modern desktop OS. In its most extreme builds, expect the following to be gone:

  • Inbox apps: Xbox, Solitaire, Clipchamp, Mail & Calendar, Media Player, Feedback Hub, Photos, Maps, GetHelp, and other preinstalled UWP/Win32 apps.
  • Microsoft cloud hooks: OneDrive integration, Office consumer bits.
  • Browsing runtimes: Microsoft Edge components, legacy Internet Explorer artifacts.
  • Security and servicing: Windows Update hooks, parts of WinSxS, Windows Defender (in some variants), and the ability to add or remove features later.
  • Platform features: BitLocker support, Search, Windows Hello biometrics, IME (input method editors), accessibility extras, and optional language packs.
  • Drivers and media: Most optional drivers (some builds keep only basic VGA, networking, and storage), audio subsystems, optional fonts, and wallpapers.
  • Telemetry and scheduled tasks: Many background diagnostic helpers that inflate the image.

This is not a light “debloat.” It’s a surgical amputation designed to produce the smallest possible runtime environment. Notably, none of these components can be added back later in the extreme mode — they’re gone for good.

Use Cases: Where a 2.29GB Windows Finds a Home

Despite its radical nature, nano11 has a handful of niche but valid use cases. The most obvious is lightweight, ephemeral virtual machines for continuous integration and testing. Rapid spin-up and minimal disk usage are ideal for automated testbeds that are routinely reimaged and don’t need updates. Malware analysts and sandbox enthusiasts also appreciate a minimal image that reduces noise from consumer features and simplifies environment control.

Legacy hardware demonstrations or offline kiosks can benefit from a tiny OS that never connects to the internet or requires cloud integration. Educational labs teaching Windows image servicing, DISM workflows, and compression techniques find nano11 a valuable, reproducible teaching tool. For any scenario where the machine is air-gapped, short-lived, or strictly single-purpose, the trade-offs may be acceptable.

The Security, Serviceability, and Compatibility Trade-offs

For all its technical elegance, nano11’s extreme profile comes with existential risks. The removal of Windows Update means Microsoft’s cumulative and out-of-band security fixes will never reach the machine. Any connected system is exposed to vulnerabilities discovered after the image’s snapshot date — a critical flaw for anything that touches the internet. Without Defender and other security agents, users must install and maintain alternative endpoint protection, a non-trivial burden for most.

Driver gaps can break Wi-Fi, cameras, fingerprint readers, and GPUs. Missing platform services like Search, BitLocker, or biometrics can disrupt workflows and applications that expect these features. The loss of OneDrive integration or Edge may be a plus for some, but it can also create compatibility headaches. Licensing remains unchanged: nano11 does not bypass Microsoft’s activation requirements; a valid license is still needed.

Supply-chain trust is another serious concern. Nano11 scripts repackage official Microsoft ISOs, but the modifications are third-party. Prebuilt ISOs floating around the internet could contain malware or backdoors. The only safe approach is to build from an ISO you’ve downloaded directly from Microsoft, audit every line of the script, and run it in a clean environment. The forked nature of the project — with variants like winwastaken/nano11builder — adds to the confusion; each repository may have different removal logic and trustworthiness.

How to Build nano11 Responsibly

For advanced users willing to experiment, a safe workflow looks like this:

  1. Obtain an official Windows 11 ISO matching your desired SKU from Microsoft.
  2. Acquire the nano11 or tiny11 script from a reputable repository (NTDev’s own releases are preferred) and inspect every command. Look for any unexpected downloads, registry changes, or network calls.
  3. Install the Windows ADK to get oscdimg.exe if you intend to create a bootable ISO.
  4. Run the builder with elevated permissions on a separate build host. Start with the serviceable profile (tiny11-like) rather than the extreme nano/core mode to preserve updateability.
  5. Verify the output ISO by comparing file hashes if you’re rebuilding an image yourself. Never use unverified prebuilt ISOs for anything involving sensitive data.

If you must use nano11 on a network, isolate it behind strict firewalls and deploy alternative antivirus/EDR solutions. Maintain a manual reimaging schedule to apply at least some security patches.

Alternatives to nano11

If the goal is a smaller, faster Windows without sacrificing security, several less radical options exist:

  • Tiny11 (serviceable mode): Strips inbox apps while keeping Windows Update and servicing paths intact. A balanced choice for enthusiasts who want a lighter desktop.
  • Custom unattended deployments: Use Microsoft’s official image customization guidance to remove selected components while preserving updateability — suitable for corporate fleets.
  • Windows 11 LTSC or IoT Enterprise: Licensed editions designed for embedded and kiosk scenarios, offering minimal footprints with vendor support.
  • Lightweight Linux distributions: For older hardware or single-purpose machines where Windows compatibility isn’t required, Linux often provides a smaller and more secure environment.

Expert Verdict: Impressive Engineering, Niche Application

Nano11 is a testament to the flexibility of Microsoft’s imaging tools and the ingenuity of the community. The ability to shrink a modern, feature-laden OS to just 2.29GB using only official utilities is remarkable. For specialized labs, CI pipelines, and air-gapped sandboxes, it’s a valuable tool. The scripts also serve as a hands-on lesson in DISM workflows and compression techniques.

However, the project’s own warnings must be taken seriously. “This is an extreme experimental script designed for creating a quick and dirty development testbed,” the GitHub readme states. The intentional removal of updates and defenses makes any connected system a sitting duck for vulnerabilities. The compatibility gaps, supply-chain risks, and irreversibility of the extreme profile mean that nano11 is not, and was never meant to be, a daily driver OS.

For most users, the more measured tiny11 serviceable path or official Microsoft deployment customization strikes a safer balance between footprint reduction and long-term maintainability. But if you’re an enthusiast with a specific, transient need and a willingness to manage the risks, nano11 offers a fascinating glimpse at just how small Windows can become when you strip away everything but the absolute minimum. Just don’t expect it to be secure, updatable, or anything like the Windows you know.