A new community script can compress a standard Windows 11 installation into a footprint of just 2.8 GB on disk, but the radical pruning required leaves the operating system unfit for anything beyond disposable virtual machines and test labs. The project, called nano11, builds on the lineage of NTDEV’s Tiny11 family by automating the removal of features, drivers, and servicing components through Microsoft’s own deployment tools, yielding an ISO image barely larger than 2 GB. While the space savings dazzle—stock Windows 11 installations commonly consume 20 GB or more—the trade-offs are immediate and severe: no Windows Update, no built-in antivirus, and shattered compatibility with a wide array of hardware and software.

Where nano11 Comes From

For years, Windows enthusiasts and IT professionals have chafed at the operating system’s ever-expanding disk appetite. NTDEV’s Tiny11 project popularized a methodical approach: mount an official Microsoft ISO, use the Deployment Image Servicing and Management (DISM) tool to strip away optional packages and inbox apps, then re-export the image with aggressive compression. Tiny11 core variants demonstrated that LZX/LZMS compression, originally designed for Windows’ component store, could shrink an install to around 3 GB. nano11 arrives as a fork of that idea, sharpened to an extreme. Its builders focus on producing the smallest possible test image, targeting Enterprise evaluation editions and long-term servicing channel (LTSC) roots to further reduce bloat.

How the Script Achieves a 2.8 GB Installed Size

At its core, nano11 is a batch and PowerShell script that orchestrates five phases: mounting the official ISO’s install.wim, running DISM to remove a long list of components, compressing the image, rebuilding the ISO with oscdimg, and applying optional post-setup tweaks. Unlike many custom ISO projects, nano11 insists on using only Microsoft-signed utilities—no third-party binaries—aiming for auditability and repeatability. The secret sauce is LZMS compression, invoked through DISM’s /Compress:recovery flag or directly via the image export parameters. LZMS trades significant CPU time during image creation for dramatic reductions in the final on-disk footprint, particularly when combined with the removal of the massive WinSxS side-by-side component store.

Reported numbers from the project’s repository and community testers confirm an ISO size just above 2 GB and an installed size around 2.8 GB. That figure assumes a single language, no cumulative updates baked in, and the most aggressive removal profile. For comparison, a fully patched Windows 11 23H2 ISO from Microsoft exceeds 6 GB, and a fresh install routinely lands between 20 and 30 GB after initial setup and driver installation.

What nano11 Removes—and What You Lose

The script’s default removal list reads like a surgeon’s inventory of Windows components. It carves out:

  • Windows Update and servicing stack (in certain builds), rendering the OS unable to receive monthly patches or feature upgrades.
  • Windows Defender and all antimalware binaries, eliminating real-time protection and firewall management.
  • Microsoft Edge, Copilot, and the WebView2 runtime, cutting off the default browser and many hybrid app dependencies.
  • Inbox apps: Mail, Calendar, Media Player, Clipchamp, Xbox services, Teams consumer, and the entire Microsoft Store experience.
  • Language packs, IMEs, and speech recognition for all but the selected locale.
  • Large driver packages for printers, Bluetooth, cameras, and third-party peripherals, plus many display and network adapter drivers.
  • WinSxS backups and recovery environment tools, further trimming the component store.

Each removal buys a specific byte count, but collectively they gut Windows of its everyday usability. Without servicing, the machine remains frozen on whatever vulnerability profile existed at ISO creation. Without Defender, there is no native defense against malware unless a third-party solution is manually installed. Without drivers, even basic networking might fail on bare metal. Without Edge or WebView2, many modern apps—including parts of the Settings UI—may refuse to launch. And without the Store, obtaining even essential utilities like Notepad or Calculator becomes a manual affair.

Where nano11 Makes Sense

nano11 doesn’t pretend to be a daily driver. Its README and community discussions explicitly label it a tool for:

  • Virtual machine testbeds: spinning up disposable Windows instances to test software installers, driver packages, or configuration scripts without chewing through dozens of gigabytes of disk per VM.
  • Resource-constrained hardware labs: repurposing ancient laptops or embedded devices where a full Windows install would not physically fit.
  • Imaging and forensic exercises: creating reproducible, minimal baselines for benchmarking or security analysis.
  • Education: teaching the mechanics of DISM and Windows servicing without the noise of a full OS.

For these scenarios, the speed advantage is tangible. A nano11 VM can boot in seconds from a small dynamic disk, install in under five minutes, and be snapshotted without ballooning storage costs. In CI/CD pipelines that need a Windows runtime for quick tests, the image’s lean size translates directly to shorter download and provisioning times.

Security, Servicing, and the Licensing Reality

Using nano11 in any environment that touches a network, personal data, or compliance requirements borders on reckless. The absence of Windows Update means even a day-one zero-day remains unpatched forever unless you manually re-image with a newer build. Mature organizations mitigate this by keeping nano11 VMs strictly isolated in offline or tightly segmented lab networks, but home users often underestimate the risk. A single drive-by download from a browser or removable media can compromise a machine that has no guardrails.

Supply chain trust is another factor. While the nano11 repository publishes its scripts openly, there is no cryptographic verification that a prebuilt ISO available elsewhere is truly built from those scripts. WindowsForum members are strongly advised to build the image themselves from an official Microsoft ISO downloaded through the Media Creation Tool or Volume Licensing Service Center. Inspecting the script’s source code—which should only invoke DISM, PowerShell, and oscdimg—adds a layer of confidence, but the builder remains community-maintained with no formal support.

Licensing never goes away. nano11 does not circumvent activation; it still requires a valid Windows 11 license. The project’s focus on LTSC evaluation ISOs means many users can explore without a key, but any machine used for production testing must be properly activated under the usual Microsoft terms. Stripping features does not grant a right to free use.

nano11 vs. Tiny11 vs. AtlasOS

nano11 sits within a small but active ecosystem of Windows image customization projects:

  • Tiny11 (by NTDEV) is the broadest and best-documented. Its builder offers granular checkboxes for what to remove, supports all Windows 11 editions, and has a large community of testers. Tiny11 core pushes the boundaries to around 3 GB installed, but even it retains more servicing hooks than nano11’s most aggressive profiles.
  • nano11 differentiates itself by targeting Enterprise LTSC sources and providing a separate post-setup toolkit to toggle Copilot and Edge. Its removal list is more maximalist, and its scripts are intentionally simpler, making it a favorite for fork developers.
  • AtlasOS takes a different path: it is a performance-tuning overlay applied to an existing Windows installation, disabling services and tweaking scheduling rather than rebuilding an ISO. It doesn’t aim for extreme disk savings, instead favoring lower memory and CPU overhead.

For most users curious about minimal Windows, Tiny11 remains the safest starting point. nano11 appeals to those who need to push the envelope even further, fully accepting the breakage that comes with it.

A Conservative Build-and-Test Plan

If you decide nano11 fits a narrow need, the following sequence minimizes risk:

  1. Work only in a virtual machine or on a dedicated test PC with no personal data. Hyper-V, VMware Workstation, or VirtualBox are ideal.
  2. Download the official Windows 11 multi-edition ISO from Microsoft’s website—preferably the same language and edition the script specifies.
  3. Clone the nano11 repository from its public GitHub URL. Open the main script in a text editor and verify it uses only the expected commands: dism /mount-image, dism /remove-package, dism /export-image, and oscdimg. Reject any script that downloads external executables or calls cryptic binaries.
  4. Mount the ISO and run the script as an Administrator, selecting your desired SKU (usually Enterprise or LTSC). The removal and compression process may take 30–60 minutes.
  5. Create a bootable USB or attach the new ISO to a VM and perform a clean install. Do not enter a product key unless required; the evaluation period is typically 90 days.
  6. Test exhaustively: check networking, display resolution, basic applications, and whether any peripherals you need are recognized. Immediately attempt to launch Windows Update—its failure confirms the intended state.
  7. Snapshot the VM or store the ISO alongside a text file documenting the exact script version and command-line options used. Reproducibility is invaluable when a future test requires the same environment.

Strengths That Deserve Applause

Despite the cautions, nano11 delivers genuine engineering value:

  • Disk efficiency: A 2.8 GB install is less than 15% of a typical Windows 11 footprint. For labs running dozens of VMs, that slashes storage costs.
  • Speed: Deployments finish in minutes rather than tens of minutes. Boot times shrink noticeably, especially on spinning rust or slow SSDs.
  • Reproducibility: Scripted pipelines enable consistent test environments, a boon for QA teams that must validate software against Windows.
  • Educational insight: Building nano11 teaches the internals of DISM and Windows componentization better than any textbook.

Risks That Cannot Be Ignored

  • Perpetual vulnerability: Without updates, every exploit discovered after your build date remains open forever.
  • Hardware roulette: Missing drivers can prevent Wi‑Fi, Bluetooth, touchpads, or GPU acceleration from working, sometimes in non-obvious ways. Windows Hello and biometrics are guaranteed to fail.
  • Feature entropy: Microsoft continually changes how components like Copilot and Edge reinstall themselves. A build that works today might be bypassed by a silent Windows update next month if you accidentally connect such a machine to the internet.
  • No support safety net: Microsoft will not assist with problems on a nano11 system, and community support, while enthusiastic, relies on volunteers with varied expertise.

What the Windows Community Should Monitor

As Windows evolves, scripts like nano11 face an ongoing cat-and-mouse game. Microsoft has steadily hardened the servicing stack, making it harder to permanently delete certain packages. The Tiny11 maintainer recently added routines to block Copilot reinstallation using provisioning commands; nano11 will need similar agility. Compression compatibility is another frontier: LZMS-compressed images might exhibit odd behaviors during in-place upgrade attempts, and there are no guarantees that future DISM versions will treat recovery-compressed images identically. Finally, community auditing remains light—newcomers should watch for repos that publish clear changelogs and respond transparently to issues.

The Bottom Line

nano11 is a remarkably effective script for distilling Windows 11 down to its bare essence, producing an ISO just over 2 GB and an installed size under 3 GB. It does so by wielding Microsoft’s own DISM toolchain with surgical precision, removing everything from Windows Update and Defender to inbox apps and drivers. This makes it a stellar candidate for VM testbeds, low-resource labs, and educational experiments. But the same cuts that deliver dramatic space savings also eliminate the safeguards that make Windows trustworthy for daily use.

Before running the script, ensure it aligns with a use case that can tolerate permanent disconnection from updates, manual security supplementation, and potential hardware incompatibilities. Build from an official ISO, inspect the script, and keep the resulting image confined to throwaway environments. Used wisely, nano11 exemplifies how much of Windows is optional—but it also dramatizes why those options exist in the first place.

Final checklist for the cautious:
- Build in a VM or on an expendable machine.
- Source your ISO directly from Microsoft.
- Read every line of the builder script before execution.
- Never expose a nano11 machine to untrusted networks.
- Treat the installation as ephemeral; be ready to reimage at any time.