Windows 11 presents a sleek and refined appearance, but numerous pre-installed applications remain redundant for many users. Following a fresh installation, the system consumes approximately 25GB or more before any personal applications have been added. To explore the potential for a more minimalist version, I investigated options to trim down Windows to its essential core. Initiatives like Tiny11 have demonstrated the possibilities, and through the use of a PowerShell script, creating a lightweight ISO at home became feasible. Implementing this method yielded surprising results, albeit with certain limitations.
My pursuit for a more compact version of Windows 11 led me to discover a powerful tool specifically designed for this task.
Reasons for Building a Custom Windows 11 ISO
Elimination of Built-in Clutter
Windows 11 comes bundled with several applications that I find unnecessary, with Edge and its components being the primary culprits. While I typically use debloating tools to eliminate what I don’t use, their effectiveness is limited. Crafting a custom ISO provides the unique advantage of removing these components before the installation process begins.
The script I utilized adopts an assertive strategy to achieve a lean setup. It removes elements such as Windows Update, Microsoft Defender, select language packs, and legacy Internet Explorer components. Additionally, it prunes the WinSxS component store, shrinking the ISO size to approximately 2GB.
Download: Nano11
Leveraging Nano11 to Construct a Compact ISO
Script Functionality for Pre-Installation Trimming
This tool utilizes the Deployment Image Servicing and Management (DISM) to exclude specific components from the installation image and then recompresses it to minimize size. It’s important to note that this process is irreversible; once removed, these components can’t be reinstated, and because servicing and update elements are omitted in this version, the installed OS will not receive updates.
To begin, download the latest Windows 11 ISO from Microsoft’s official site and mount it using File Explorer. Next, obtain the Nano11 PowerShell script from GitHub and extract it to a designated folder on your device. Follow these steps to continue:
- Launch PowerShell with administrative privileges.
- Execute Set-ExecutionPolicy Bypass -Scope Process to permit the script to run for the active session.
- Navigate to the directory housing the Nano11 builder script using the cd command.
- Initiate the script by typing .\nano11builder.ps1 and agree to the terms when prompted.
- Input the drive letter of the mounted ISO and allow the script to commence its task.
- Select the index number corresponding to your preferred Windows edition, such as Home or Pro, visible in the prior list.
The entire process on my test configuration took approximately an hour, culminating in a new ISO file saved in the same directory as the Nano11 files. The resulting image was 2.09 GB, significantly reduced from the original 5.49 GB.
Evaluating the Trimmed ISO within a Virtual Machine
Verification of Functionality
To ascertain the performance of the trimmed image, I installed it on a fresh Windows 11 virtual machine. I configured the VM with two CPU cores and 2GB of RAM, pushing to see if it would perform adequately with minimal resources. During installation via VMware, an error arose close to completion, but reverting to an older installation method allowed me to bypass this and finalize the installation. Upon first boot, the desktop displayed a black background, which was likely a result of the modifications made by the script.
The Task Manager indicated that memory utilization was nearly half of what was assigned, about 1GB in this configuration. The installed system occupied 7.7GB of disk space, compared to around 25GB for a standard Windows 11 installation at idle with 2GB of memory use. Upon inspecting the installed components, the Settings app revealed only eight items, with the Programs and Features page showing just Remote Desktop. With Edge removed, I needed to manually install a web browser; however, Winget encountered errors, and the curl command stalled. Thus, I resorted to transferring the Chrome installer via USB into the virtual environment.
Once a browser was in place, I examined the functionality of the Microsoft Store. Although the taskbar icon was present with working search capabilities, app pages failed to load. Winget also produced source errors when attempting to install new applications like Firefox and Chrome. Manually installing Chrome enabled me to subsequently acquire Brave from the Store, probably because some components were reinstated during that installation. Media playback functionality was verified with YouTube playing successfully, indicating that essential audio support persisted despite some removals by the script.
Limitations of the Nano11 Tool
While the Nano11 script grants the flexibility to curate the contents of the ISO, this capability comes with an expectation of technical proficiency. Incorrectly omitting certain components may lead to a non-functional image or boot issues. Moreover, Nano11 can remove critical Windows services including Windows Update, so this version is not recommended for primary usage. The developer suggests it serves better as a testing or development platform rather than a complete operating system.
Users will also promptly notice the absence of many fundamental utilities. Lacking a native image viewer or editor, other commonplace tools must be added manually. Despite these concessions, I would contemplate employing this setup on a low-spec or secondary PC where update frequency holds less significance. Each time Microsoft releases a new build, I can generate another streamlined ISO with ease.
Leave a Reply