The news
NTDEV, a known Windows tinkerer, has posted a working build of Windows 11 26H2 that boots and runs on a machine equipped with only 128 megabytes of RAM. The work was done while the developer tested a new tool aimed at the same build. The result is not a stripped-down demo but a functional instance of the operating system.
Context
Windows 11 26H2 is the version currently under active development. Prior public builds have carried the same memory floor that Microsoft set for the initial Windows 11 release. NTDEV’s experiment shows that the kernel and core components can be coaxed into far smaller footprints when non-essential services are removed or disabled at a low level. The effort coincides with the developer’s work on an unnamed tool that apparently required repeated clean installs and rapid reboots.
The single published source describes the outcome as the product of ongoing testing rather than an isolated stunt. This places the result in the context of practical iteration: the developer needed a reliable way to reset environments quickly while refining the tool. The 128 MB configuration therefore emerged from repeated cycles of modification, boot, and observation rather than from a single targeted patch.
Details
The 128 MB figure comes directly from the developer’s report on the modified 26H2 image. No additional hardware specifications beyond the memory constraint were shared. The build still reaches a desktop environment, which implies that the memory manager, basic drivers, and shell were retained rather than excised entirely. NTDEV described the outcome as the product of iterative testing rather than a one-off stunt, suggesting the changes are reproducible on similar hardware.
The source article provides no further technical breakdown of which components were removed or how paging and driver loading were adjusted. It also gives no indication whether the same image remains stable under load or whether it is limited to a single boot cycle. Those details remain outside the published record.
Because the source supplies only the headline result and the developer’s stated purpose, any discussion of exact service lists, registry edits, or custom drivers would exceed the available facts. The report instead emphasizes that the system reached a usable desktop state under the stated constraint, leaving the precise engineering steps undocumented for now.
Why it matters
For most users the demonstration changes nothing; production Windows 11 machines will continue to ship with gigabytes of RAM and the full set of services Microsoft enables by default. The value lies in what it reveals about the underlying code. When a single developer can compress the system this far, the gap between the official minimum and the theoretical minimum becomes visible. Tool makers who need disposable test environments now have evidence that extreme memory constraints are at least possible. Hardware hobbyists and embedded integrators may treat the result as a data point when they evaluate whether future Windows builds can be pared down for niche devices. The work also underscores that memory requirements are not fixed by physics but by the choices made in the default configuration. Until Microsoft publishes its own guidance on minimal footprints for 26H2, NTDEV’s build stands as the clearest public marker of how low the number can go.
The experiment also highlights a practical boundary for anyone who maintains test fleets or automated build pipelines. When a full Windows 11 image can be coaxed onto 128 MB, the cost of spinning up short-lived virtual machines drops sharply for those willing to accept the same level of manual trimming. That reduction matters most to developers who already work at the edge of resource limits rather than to general users.
---
Sources:
No comments yet