As I contemplate the transition to Windows 11, I find myself in a familiar position—awaiting the completion of an IT request form. The migration of my files will likely consume a weekend, yet the necessity of this shift is underscored by my professional obligations. While I am primarily recognized as a Linux and Raspberry Pi enthusiast, the allure of Windows 11 beckons, particularly for video editing tasks using DaVinci Resolve. Although the software is available on Linux, my attempts to install it have yet to yield success.
Recently, we delved into NTDEV’s innovative endeavor to compress the Windows 11 installation ISO image. Dubbed the Nano11 Builder, this project aspires to create the most compact ISO possible. The developer, who prefers to remain pseudonymous, describes it as “an extreme experimental script designed for creating a quick and dirty development testbed.” The standard Microsoft ISO weighs in at 5,695,402KB (5.69GB), a size that, while manageable by contemporary standards, is laden with applications and features that may not appeal to every user. In contrast, the Tiny version of the ISO is half the size of the original, while the Nano version is nearly two-thirds smaller, resulting in a more streamlined Windows 11 installation.
Installing Windows 11 Three Times…for Science?
Curiosity piqued, I embarked on a journey to discover the final installation sizes for each of these ISOs. The process required a bit of patience, as the results would unfold over time.
<table tabindex="0" class="tablewrapper tablewrapper–inbodyContent tablewrapper–sticky tablewrapper–divider”>
<caption class="tablecaption tablecaption–top tablecaption–left”>ISO Sizes
<thead class="tablehead”>
<tr class="tableheadrow”>
<th class="tableheadheading tableheadheading–left” colspan=”1″>Header Cell – Column 0
<th class="tableheadheading tableheadheading–left” colspan=”1″>Size KB
<th class="tableheadheading tableheadheading–left” colspan=”1″>Difference to Microsoft
<tbody class="tablebody”>
<tr class="tablebodyrow”>
<td class="tablebody_data” colspan=”1″>Direct from Microsoft
<td class="tablebody_data” colspan=”1″>26,445,119,488 (24.6GB)
<td class="tablebody_data” colspan=”1″>Row 0 – Cell 2
<tr class="tablebodyrow”>
<td class="tablebody_data” colspan=”1″>Tiny
<td class="tablebody_data” colspan=”1″>10,865,098,752 (10.1GB)
<td class="tablebody_data” colspan=”1″>59.1% Smaller
<tr class="tablebodyrow”>
<td class="tablebody_data” colspan=”1″>Nano
<td class="tablebody_data” colspan=”1″>8,984,236,032 (8.36GB)
<td class="tablebody_data” colspan=”1″>66.2% Smaller
To facilitate the installations, I utilized a VirtualBox virtual machine equipped with 8GB of RAM, four cores, and a 40GB virtual hard drive. For the complete Windows 11 installation, I resorted to a Lenovo X220, a device not ideally suited for this operating system. The process required using Rufus to write the ISO images to a USB flash drive, including a workaround to bypass RAM, TPM, and Secure Boot requirements.
The disparity in installation experiences was notable. While the Nano and Tiny ISOs installed seamlessly in the virtual machine, the full Windows 11 ISO encountered hurdles despite meeting the necessary specifications. This focus on installation size rendered the tests valid.
The installation of the Nano version began with relative ease, although a few steps were omitted, such as the absence of a registry key and the lack of a choice for the Windows 11 version. Progress halted at 75% when the installer crashed, prompting a reboot. A second attempt yielded the same result. Ultimately, I raised a GitHub issue and received a suggestion to revert to an older setup process, which proved successful.
Despite the slow installation on my virtual machine, persistence paid off. I navigated the process, following a guide to bypass the Windows sign-in and utilize a local account, a tip graciously provided by our former Editor in Chief.
Now, as I reflect on this journey, the next step is clear: I must submit that IT request form before October 14.
