Today, you can’t buy a new x86 processor that runs at under 1 GHz, with most mainstream desktop CPUs carrying base clocks that are well over 2 GHz or even in the 3 GHz range and boosting up much higher than that. However, back in the 1980s and 1990s, processors that operated at just a few MHz were common, with the original IBM PC clocking in at just 4.77 MHz itself.
Could one run a modern Windows operating system on a CPU with such a low clock speed? Developer and popular YouTuber NTDEV has proven that you can, booting and using Windows 7, which launched in 2009, on a Pentium-S processor that was downclocked to just 5 MHz. That’s a full 995 MHz below the 2009-era OS’s 1-GHz minimum requirement. The test system also had just 128MB of RAM, which is way short of Windows 7’s 1GB minimum requirement.
In a YouTube video (embedded below), NTDEV shows the system, which is actually a virtual machine running in the 86Box emulator (opens in new tab), boot up into Windows 7 Ultimate, launch a program which shows its 5.00 MHz clock speed and even run Notepad. By the way, if you follow the sped-up time counter in the video, you’ll note that it takes more than 28 minutes for the Windows 7 desktop to appear!
In the video, you can see NTDEV power on his virtual machine which POSTs as a Pentium-S running at 50 MHz with a 128MB of RAM. However, it has been downclocked to 5 MHz, a low speed which NTDEV told us he achieved by editing 86Box’s source code.
(Image credit: NTDEV)
NTDEV boots the system and is given a choice to use Normal or Safe modes. He chooses Normal mode, but it actually boots into Safe mode, showing all of the .sys, .dll and .exe files as they load. NTDEV told us that, as part of the hacking process, he edited the BCD (boot configuration data) so even choosing Normal mode results in Safe mode booting.
(Image credit: NTDEV)
To get Windows 7 to boot and run with such a slow CPU, NTDEV told us that he had to disable a ton of system resources, which he accomplished by running Safe mode and disabling most drivers and services to the point where only three services are running at boot. He also had to address an issue with the logonUI.
“When going below 50MHz the login screen (logonUI) doesn’t want to load,” NTDEV told us. “So in order to get to a command prompt, I had to put the OS in a pseudo-OOBE state by modifying the registry and deleting everything in the c:windowssystem32oobe folder, so that it wouldn’t load.”
The OOBE (out of the box experience) is the one you get when running a Windows installer and it doesn’t have a Start menu or Windows Explorer. However, the command prompt is usually available during OOBE and you can usually get it by hitting Shift + F10.
We noted that the desktop NTDEV shows in the video has no Start menu, there’s no wallpaper and the windows themselves have a very simple theme; there’s no way Aero transparencies would work here. To launch a program, WCPUID / Real Time Clock Checker, NTDEV has to type its shortcut name into the command prompt. He later does the same to launch Notepad.
Perhaps …….