Talks to Watch

Windows 11 on Pentium 4

839K views · Feb 20, 2023 · 38:59 · 0 HN recommenders · 3 mentions · discussed 2023

Enderman gets Windows 11 running on a Pentium 4 system with a Radeon HD 5870 and 8 GB of DDR2. It explores how an unsupported, ancient CPU can be made to work by using the rare last Pentium 4 variant and a registry flag.

Why Hacker News points people here: HN mentions it as a reference for Windows 11's actual CPU requirements and for how screen flicker is edited out of footage.

“he basically says that he needed to run the rare last variant of the Pentium IV to get it to work”HN comment, 2023

What Hacker News said 3

Cites itnordsieckFeb 2023

“he basically says that he needed to run the rare last variant of the Pentium IV to get it to work”

Shows Windows 11 only works on rare last Pentium 4 variant.

Full comment

> this video I feel a bit vidicated by that video. In the beginning, he basically says that he needed to run the rare last variant of the Pentium IV to get it to work and that most Pentium IVs would be impossible to get it to work. Pretty impressive that it's possible at all, though.

in “Nokia launches DIY repairable budget Android phone” · view on HN
Cites itMedoxMar 2023

“TFT flickering can also be edited out afterwards, as seen here after ~22:40”

Shows screen flicker edited out afterwards around 22:40.

Full comment

Not sure for CRT's but TFT flickering can also be edited out afterwards, as seen here after ~22:40: this video

in “How they filmed The Last of Us arcade scene” · view on HN
Cites ittoasterosAug 2023

Shows installing Windows 11 on a Pentium 4 via registry flag.

Full comment

Indeed no pitchforks, but I can see where some concern has come from. On the release of Windows 11 it was stated that only newer Intel and AMD generations were to be officially supported and while workarounds are built in (literally a registry flag in the installer) to install on even a Pentium 4 [1], they came with a warning from Microsoft that installations in such environments "may not receive updates". Is it therefore possible that this bug check is being implemented as part of the journey towards actually dropping "support" for these CPUs? Indeed, it's a preview release, and the Insider program is amazing for getting insight into Windows development and it shouldn't be held up to the same level of journalistic scrutiny as a sanctioned general release, but I can absolutely see why this particular change may have raised some eyebrows. [1]: this video

in “New Windows updates cause UNSUPPORTED_PROCESSOR blue screens” · view on HN