A new community script called Nano11 can carve a standard Windows 11 installation down to a bare-bones 3.25GB after aggressive compression, with the install ISO itself weighing just 2.28GB. That’s a fraction of the typical 20–30GB footprint — but the extreme diet comes at a heavy price: updates are broken, security features are gutted, and hardware compatibility is a roll of the dice. The project, an offshoot of the better-known Tiny11 by developer NTDEV, was recently detailed by HotHardware and has sparked both fascination and caution within Windows enthusiast circles.

The Shrinking of Windows 11

Microsoft’s latest OS ships with a sprawling disk footprint. A clean install of Windows 11 routinely chews up 20–30GB, stuffed with bundled apps, legacy components, and a deep well of drivers. For virtual machine tinkerers, developers, and users of low-storage devices, that bulk is a nuisance. Over the past two years, a cottage industry of “tiny” Windows builds has emerged, with NTDEV’s Tiny11 becoming the poster child. Nano11 pushes the concept further, automating the stripping process with a script that removes nearly everything that isn’t strictly required to boot.

How Nano11 Achieves Its Radical Size Reduction

The Nano11 workflow, as outlined by HotHardware and corroborated by developer documentation, follows a two-stage compression strategy. First, the script surgically removes components: Windows Defender, Windows Update and servicing stack, Microsoft Edge, recovery tools, WinSxS component store, and a massive list of built-in drivers. What remains is a skeleton OS. Second, Microsoft’s own compact.exe tool, with the LZX algorithm, compresses every system binary on disk. LZX is the most aggressive NTFS compression method available, reducing file sizes by up to 40–50% in many cases. Deleting the pagefile and hibernation file then delivers the final, headline-grabbing numbers.

The Numbers Behind the Demo

The specific figures reported for NTDEV’s Nano11 build are tied to a Windows 11 LTSC English ISO. After running the script, the ISO shrank to 2.28GB. A fresh installation from that ISO occupied 8.32GB. Post-compression with compact.exe and removal of the pagefile, the used disk space dropped to 3.25GB. Those numbers are neither fabricated nor magical — they are the logical outcome of stripping all but essential binaries and then applying Microsoft’s own space-saving technology. However, they do not represent a usable, general-purpose operating system. The demo was an experimental exercise, and NTDEV himself labels such builds as “extreme” and not for daily driving.

Why the Tiny Footprint Is Both Real and Misleading

Technically, the compression claims hold water. The compact.exe /EXE:LZX command is documented by Microsoft and is the same mechanism that powers CompactOS, a feature designed to shrink Windows 10/11 footprints on devices with small SSDs. When LZX compression is applied to an already stripped-down OS, the remaining files — mostly DLLs, executables, and a few configuration bits — compress remarkably well because Windows images are laden with redundancy. The Tiny11 ecosystem has repeatedly demonstrated install sizes around 3–4GB, so Nano11’s results are consistent with those precedents.

The catch is context. The demo optimizes for one metric: installed disk usage. It disregards every other attribute that makes Windows a reliable, secure, and maintainable platform. The installation was performed in a controlled environment, with no drivers beyond the basic virtual hardware, no additional software, and no attempt to apply updates. In the real world, disk space is only one factor; a machine that can’t receive patches or run standard applications is a non-starter for most users.

What Nano11 Removes — and What You Lose

Nano11’s script prunes Windows to the bone. The removal list includes:

  • Windows Update and Recovery components – Without these, cumulative security patches cannot be installed. Even attempting to add updates later can fail or resurrect previously stripped components, leading to unpredictable behavior.
  • Windows Defender and security services – The entire antivirus and threat protection stack is gone, leaving the system naked unless you manually install a third‑party solution.
  • Tens of thousands of device drivers – Bare‑metal installations will struggle to recognize anything beyond the most generic hardware. Manual driver injection becomes a necessity, and without update services, acquiring and installing drivers is a chore.
  • WinSxS (Component Store) – This directory holds multiple versions of system files for servicing; removing it breaks the servicing model entirely, making future updates impossible.
  • Edge, Store, and telemetry components – While many users won’t miss these, their absence means losing access to Store apps and some modern Windows features.

The practical consequences are severe. A Nano11 machine cannot be made compliant with corporate security policies. It cannot be trusted to handle sensitive data. And troubleshooting becomes a nightmare because standard Windows recovery tools are missing. For any environment that demands reliability, these are deal‑breakers.

The Risks: Security, Stability, and Licensing

Running a Nano11‑style image on a production system flirts with disaster. The removal of Defender and update channels leaves the OS perpetually vulnerable to known exploits. Malware authors actively target unpatched Windows systems; a build that can never receive a fix is a sitting duck. Even if you layer on a third‑party antivirus, the underlying OS kernel and services remain unpatched, a risk no amount of aftermarket security can fully mitigate.

Stability is another casualty. Stripping out drivers and the servicing stack can cause subtle incompatibilities that manifest as application crashes, audio issues, or network failures. Games, creative software, and even office suites may balk at the missing components.

Licensing and supply‑chain integrity add another layer of concern. While the Nano11 script itself is a legitimate automation tool, the resulting ISO is still a modified version of Microsoft’s copyrighted software. Redistributing such images without authorization runs afoul of licensing terms. More practically, users who download pre‑built Nano11 ISOs from third‑party sites expose themselves to tampered binaries. The recommended approach — and one that every knowledgeable community guide insists upon — is to start with an official Microsoft ISO and run the script locally.

Where Nano11 Fits: Use Cases That Make Sense

The extreme slimming does have niches. Ephemeral test virtual machines, continuous integration workers, and forensic analysis sandboxes are perfect candidates. In these settings, VMs are spun up, tasks are executed, and the environment is destroyed. Serviceability is irrelevant because the machine’s lifespan is measured in hours. A 3.25GB image deploys faster, consumes fewer host resources, and can be replicated instantly.

Similarly, embedded and semi‑disconnected environments — digital signage, kiosks, or lab instruments — might tolerate a locked‑down, unpatched OS if the attack surface is already physically controlled. But even there, the risks of driver incompatibility and missing components complicate deployment. For any machine that will ever touch the internet or handle user‑generated data, Nano11 is a liability.

Best Practices for the Curious

If you’re tempted to try Nano11, follow these hardened guidelines from the community:

  • Start from an official Microsoft ISO. Never use a pre‑built third‑party image. Download the ISO directly from Microsoft’s media creation tool and verify its hash.
  • Test exclusively in a VM first. Spin up a Hyper‑V, VMware, or VirtualBox instance and pound on it for weeks. Install your typical applications, attempt driver installations, and simulate real workloads. Only after you’ve identified every missing piece should you even consider bare metal.
  • Snapshots and backups are non‑negotiable. Before making any change, take a VM snapshot or a full disk image. Rollback will be your salvation when something invariably breaks.
  • Consider less destructive alternatives. Microsoft’s CompactOS feature, accessed via compact /CompactOS:always, can shrink a full Windows 11 install by 2–5GB without removing any system components. It keeps updating and Defender intact. Combining CompactOS with manual removal of optional features (like language packs or OneDrive) often yields enough savings without breaking patchability.
  • If security matters, don’t strip Defender or Update. Instead, focus on cleaning out the bloatware: pre‑installed apps from the Microsoft Store, Xbox services, and unnecessary scheduled tasks. Tools like the open‑source Bloatynosy or Windows10Debloater can help, but always review what they remove.

Alternatives: Tiny11, AtlasOS, and CompactOS

Nano11 sits at the far end of the size‑optimization spectrum, but there are more moderate options. NTDEV’s own Tiny11 project offers multiple versions that preserve more functionality. Tiny11 Core, for example, produces a ~2GB ISO and a ~3.3GB install but still keeps basic driver support and a handful of services. It’s a better starting point for those who want a small footprint without a completely broken OS.

AtlasOS and RevisionOS take a different approach, aiming to reduce overhead for gaming rather than absolute storage size. They tend to keep update mechanisms functional (though some test with updates delayed). All such community builds, however, share the fundamental risk of unsupported Windows modifications.

The Larger Question: Why Is Windows So Bloated?

Nano11’s existence raises uncomfortable questions for Microsoft. Why does a modern OS ship with so many duplicate drivers, dormant services, and app bundles that a script can cut 90% of the footprint? The answer lies in compatibility and convenience. Microsoft must support hundreds of thousands of hardware combinations out of the box, deliver seamless updates, and cater to a broad audience that expects everything to “just work.” That engineering trade‑off produces a massive, highly redundant disk image.

For now, the number “2.28GB” is an eye‑opener, not a recommendation. It proves that Windows can be stripped to its essentials, but it also proves that those essentials are fragile. As NTDEV and other developers continue to experiment, we may eventually see a middle ground — a Windows version that’s both small and serviceable. Until then, Nano11 remains a tantalizing but treacherous tool for those who truly know what they’re sacrificing.