New WinPOPBit tool bypasses Windows 11 CPU restrictions to support truly ancient PCs

Alfonso Maruccia

Posts: 2,838   +1,102
Staff
In brief: Unlike previous releases, Windows 11 significantly limits the number of systems on which users can attempt to install the new operating system. Needless to say, some developers have recognized Microsoft's challenge and raised the stakes considerably.

A new open-source utility is bringing the latest Windows editions to places where Microsoft developers dared not go. Initially released a few weeks ago, WinPOPBit is designed to "pop" some of the most restrictive hardware requirements in newer Windows 11 versions. The project is progressing rapidly, which means even more ancient CPUs could soon become "compatible" with the latest PC operating systems.

WinPOPBit primarily targets Windows 11's requirement for CPUs with POPCNT and SSE4.2 instruction support, as well as Windows 10's NX bit requirement. Microsoft introduced the new CPU requirements with the Windows 11 24H2 update, preventing OS enthusiasts from installing the latest release on PCs still running decades-old processors.

Despite acknowledging these new "hard" CPU requirements, WinPOPBit's developers have found a way to restore compatibility. The Python tool is essentially an "experimental patcher" capable of modifying a few relevant bytes in Windows system files, allowing newer OS releases to boot and run on CPUs that date back to before Windows 7 was even a thing.

WinPOPBit is designed to directly patch binary files that host the Windows NT kernel (ntoskrnl.exe), the system boot loaders (winload.efi and winload.exe), and several additional DLL files. The developers explain that Windows 11 24H2 and newer versions check for POPCNT and SSE4.2 CPU support but do not actually require these newer instructions for 99% of their files. Meanwhile, Windows 10 primarily requires the NX bit for its innermost, ring 0-level kernel code.

WinPOPBit has already restored Windows 11 and Windows 10 compatibility on some truly ancient x86 processors, including AMD's Athlon II and Intel's Pentium 4 "Northwood" CPU from 2002. Now, the developers are working to expand the tool's capabilities even further, bringing support to increasingly old hardware.

The latest code commits could allow Windows 10 and Windows 11 23H2 to run on AMD systems based on Socket 754, 940, and 939, as well as AM2-based CPUs from the AMD K8 family. The upcoming WinPOPBit release should also force Windows 11 to boot on the Athlon 64. You heard that right: thanks to a third-party Python script, hardware enthusiasts may soon be able to install a modern 64-bit Windows release on AMD's first 64-bit processor, released in 2003.

Additionally, WinPOPBit is expected to support patched versions of Windows 10 and Windows 11 23H2 on Intel LGA 775 systems, including those powered by Pentium 4 "Prescott" and Pentium D "Smithfield" processors. Using the tool isn't for the faint of heart, and the WinPOPBit developers clearly state that Microsoft will not provide official support for this kind of tinkering.

Permalink to story:

 
It might be neat as a thought exercise but these CPUs are so slow I wouldn't want to even attempt to run 11 on them, let alone any modern application.

Even the later core 2 chips are nearly worthless for basic web browsing these days.
For running Windows in 64/32bit mode you don't need much CPU power,
it's the lot's of memory Windows needs for running in protectedmode
(back in days memory cost alot much like today's prices or even more)
So it's was a pine in a.. to get it working properly, you was nessay to use the HDD as swapdrive alot
 
It might be neat as a thought exercise but these CPUs are so slow I wouldn't want to even attempt to run 11 on them, let alone any modern application.

Even the later core 2 chips are nearly worthless for basic web browsing these days.
Exactly. Chrome alone would make those older CPUs practically beg for mercy.
 
For running Windows in 64/32bit mode you don't need much CPU power,
it's the lot's of memory Windows needs for running in protectedmode
(back in days memory cost alot much like today's prices or even more)
So it's was a pine in a.. to get it working properly, you was nessay to use the HDD as swapdrive alot
I think you're confusing the ability to run an operating system with the ability to run it effectively.

Yes, RAM was expensive decades ago, and Windows often relied heavily on hard drive paging when physical memory was insufficient. But that has little to do with what TheInsaneGamer is saying.

His point is about the actual performance of ancient processors running a modern operating system and today's applications.

You could put 32 GB of RAM and an SSD into an old Core 2 Duo system, and while it would certainly help, that processor would still struggle with many modern workloads.

And protected mode isn't what makes modern Windows memory hungry.

There's a considerable difference between getting Windows 11 to boot and having a computer you'd actually enjoy using.
 
Those initiatives are great from both a technical and a refurbishing/repurposing point of view, but why would you bother with using Windows 11 anyway ?
Giving a second life to old hardware is simple and straightforward : just install a lightweight, yet modern Linux distribution on it, and you're good to go.
 
If someone is willing to go this far to load W11 on a relic, they probably will use a stripped down version of W11 that needs <1GB of RAM that should run on 8GB RAM machines just fine.
 
Back