Monday, February 19th 2024

Windows 11 24H2 Instruction Requirement Affects Older/Incompatible CPUs

Systems running on older hardware could be excluded from upcoming public versions of Windows 11—the recently released preview/insider build (26052) has introduced all sorts of new features including "Sudo for Windows", an improved regedit, and hidden beneath the surface, an AI-flavored Super Resolution settings menu. Early partakers of version 24H2 are running into instruction set-related problems—Windows operating expert, Bob Pony, was one of the unlucky candidates. Microsoft's preview code seems to require a specific instruction set to reach operational status—Pony documented his frustrations on social media: "Using the command line argument "/product server" for setup.exe, BYPASSES the system requirement checks for the Windows 11 24H2 setup program. But unfortunately, after setup completes then reboots into the next stage. It'll be indefinitely stuck on the Windows logo boot screen."

He continued to narrow in on the source of blame: "Windows 11 Version 24H2 Build 26058's setup (if ran in a live Windows Install) now checks for a CPU instruction: PopCnt." The Register provided some history/context on the SSE4 set: "POPCNT/PopCnt counts the number of bits in a machine word that have been set (or different from zero.) You might see it in cryptography and it has been lurking in CPU architectures for years, pre-dating Intel and AMD's implementation by decades." It is believed that Microsoft has deployed PopCnt as part of its push into AI-augmented software features, although a segment of online discussion proposes that an engineer has "accidentally enabled" newer CPU instruction sets. Tom's Hardware marked a line in the sand: "PopCnt has been supported since the Intel Nehalem and AMD Phenom II (microarchitecture) era—14 years ago—so compatibility won't be an issue for any modern systems. The only users that will be affected are enthusiasts running modified versions of Windows 11 on 15+ year-old chips like Core 2 Duos or Athlon 64." Bob Pony's long-serving Core 2 Quad Q9650 processor—a late summer 2008 product—was deemed unworthy by the preview build's setup process.
Sources: Bob Pony, The Register, NeoWin, Tom's Hardware
Add your own comment

104 Comments on Windows 11 24H2 Instruction Requirement Affects Older/Incompatible CPUs

#1
mtosev
Who in the year 2024 would ran Windows 11 on core 2 duos/quads and Athlon 64 systems?
Posted on Reply
#2
matar
I have a FIX the answer is : Windows 10 :clap:
Posted on Reply
#3
Lycanwolfen
Windows 11 and coplit reminds me of the old Internet explorer and the lawsuits microsoft had in the 90's for forcing people too there will. I think MS needs another lawsuit.
Posted on Reply
#4
Onasi
mtosevWho in the year 2024 would ran Windows 11 on core 2 duos/quads and Athlon 64 systems?
Seeing how much outrage was even here, on TPU, in the Windows 11 thread, you would think that there is a giant amount of hidden mole people just itching at the bit to run a 2024 OS on outdated hardware.
In reality? This is a nonissue. Any PC with CPU affected isn’t worth running 11 on anyway.
Posted on Reply
#5
ThrashZone
mtosevWho in the year 2024 would ran Windows 11 on core 2 duos/quads and Athlon 64 systems?
Hi,
More people than people willing to use a dell logo as a avatar I'd bet :laugh:
Posted on Reply
#6
3valatzy
mtosevWho in the year 2024 would ran Windows 11 on core 2 duos/quads and Athlon 64 systems?
Athlon 64 no because it's very slow for internet browsing, but I don't see how the powerful for the time Core 2 Quad Q9650 processor could be labeled not decent for running Windows system?!
This is artificial obsolescence because of the greed.
Windows 11 shouldn't have existed in the first place.
Posted on Reply
#7
ZoneDymo
mtosevWho in the year 2024 would ran Windows 11 on core 2 duos/quads and Athlon 64 systems?
I mean if you dont do much other then watching youtube and word processing...you dont really need much more tbh
Posted on Reply
#8
P4-630
So my dad can dump his socket 775 e7200 system after windows 10 is EOL... :ohwell:
Posted on Reply
#9
john_
mtosevWho in the year 2024 would ran Windows 11 on core 2 duos/quads and Athlon 64 systems?
It can be run with a Core2Quad or a 4-6 core Phenom just fine, IF an SSD is installed. Think schools for example, still using pretty old systems where they would love to upgrade their OS from Win 7 for example to Win 11 to offer their students a more current environment. Of course Win 10 works fine on such old systems, but in a year from now browsers will probably stop offering updates.
Posted on Reply
#10
Beermotor
3valatzyThis is artificial obsolescence because of the greed.
Windows 11 shouldn't have existed in the first place.
Agreed my friend.

The best way to communicate your disapproval to Microsoft is to not use their OS at all and run Linux.
Posted on Reply
#11
Shihab
I'm all for backwards compatibility, but 15 years is a bit too long.
I doubt there are many casual users who still run such old hardware. Maintaining it this long does require care and people rarely do this. Those who do are probably knowledgeable enough to stick to outdated software and airgap the machine or migrate to other OS'es that still do support their hardware.
Or, and I'm betting those are the majority, using them for some fixed purpose workstation or interface for some equipment, and they'd already be on an outdated Win7 or XP.
T0@st"Sudo for Windows" (an improved Registry editor)
Did you mean "Sudo for Windows and an improved Registry editor?"
Because sudo is not a registry editor. Improved or otherwise.
Posted on Reply
#12
ThrashZone
3valatzyAthlon 64 no because it's very slow for internet browsing, but I don't see how the powerful for the time Core 2 Quad Q9650 processor could be labeled not decent for running Windows system?!
This is artificial obsolescence because of the greed.
Windows 11 shouldn't have existed in the first place.
Hi,
Yeah besides some UI differences it is pretty much win-10 sp2
Posted on Reply
#13
Wirko
I have also heard that macOS 14 has been given "instructions" not to run on PowerPC, hehe. Otherwise it would.
Posted on Reply
#14
dgianstefani
TPU Proofreader
ShihabI'm all for backwards compatibility, but 15 years is a bit too long.
I doubt there are many casual users who still run such old hardware. Maintaining it this long does require care and people rarely do this. Those who do are probably knowledgeable enough to stick to outdated software and airgap the machine or migrate to other OS'es that still do support their hardware.
Or, and I'm betting those are the majority, using them for some fixed purpose workstation or interface for some equipment, and they'd already be on an outdated Win7 or XP.

Did you mean "Sudo for Windows and an improved Registry editor?"
Because sudo is not a registry editor. Improved or otherwise.
People tend to ignore the fact that efficiency, performance and featureset software advancements also require hardware to progress. Was the switch to 64 bit operating systems a conspiracy to make everyone's hardware obsolete? No, it's just the natural progression of development.

Backwards compatibility is still excellent, there's nothing stopping those using 15 year old hardware from running a LTSC install or even Linux (which is arguably more cutting edge if kernel development is anything to go by) it's just people like to find something to complain about.
ShihabDid you mean "Sudo for Windows and an improved Registry editor?"
Because sudo is not a registry editor. Improved or otherwise.
Also noticed this. Going to follow up and edit if necessary.
Posted on Reply
#15
theFOoL
mtosevWho in the year 2024 would ran Windows 11 on core 2 duos/quads and Athlon 64 systems?
My... Uhh... 775 build
Posted on Reply
#16
dgianstefani
TPU Proofreader
ShihabDid you mean "Sudo for Windows and an improved Registry editor?"
Because sudo is not a registry editor. Improved or otherwise.
Fixed, the source had some bad formatting that made the differentiation unclear to the writer.
Posted on Reply
#17
ThrashZone
dgianstefaniPeople tend to ignore the fact that efficiency, performance and featureset software advancements also require hardware to progress. Was the switch to 64 bit operating systems a conspiracy to make everyone's hardware obsolete? No, it's just the natural progression of development.

Backwards compatibility is still excellent, there's nothing stopping those using 15 year old hardware from running a LTSC install or even Linux (which is arguably more cutting edge if kernel development is anything to go by) it's just people like to find something to complain about.


Also noticed this. Going to follow up and edit if necessary.
Hi,
Yeah sudo added to terminal to run as admin ?
Posted on Reply
#18
dgianstefani
TPU Proofreader
ThrashZoneHi,
Yeah sudo added to terminal to run as admin ?
Not sure, details aren't clear in sources, I haven't tested these builds myself. I'm sure it will be similar to how sudo works on other OS's.
Posted on Reply
#19
ThrashZone
dgianstefaniNot sure, details aren't clear in sources, I haven't tested these builds myself. I'm sure it will be similar to how sudo works on other OS's.
Hi,
Yeah Brink has a tutorial about it's addition in developer tools
But that is basically what it does
Open regular terminal and oops you need admin so just enter sudo and you're done.

Funny sudo su is what linux uses hehe

www.elevenforum.com/t/enable-or-disable-sudo-command-in-windows-11.22329/

Option 3 if you don't see it.
Posted on Reply
#20
Wirko
theFOoLMy... Uhh... 775 build
And it has to be 24H2?
Posted on Reply
#21
Halo3Addict
Why is everyone so up in arms.. it is an instruction that has been in CPUs for 15 years..
Posted on Reply
#22
Shihab
ThrashZoneFunny sudo su is what linux uses hehe
They should've followed their convention for superusers and called it admin do, or ado. Which would be more descriptive of nearly every scenario one would need a privileged cmd for... >_>
Posted on Reply
#23
mechtech
I thought even 1st gen ryzen was not "officially" supported by W11 due to tpm requirements?
Posted on Reply
#24
dgianstefani
TPU Proofreader
ShihabThey should've followed their convention for superusers and called it admin do, or ado. Which would be more descriptive of nearly every scenario one would need a privileged cmd for... >_>
Much ado about nothing, sudo?
Posted on Reply
#25
ThrashZone
ShihabThey should've followed their convention for superusers and called it admin do, or ado. Which would be more descriptive of nearly every scenario one would need a privileged cmd for... >_>
Hi,
Yeah dude on linux mint forum gave me this to just set the clock to USA time see if you recognize this stuff lol
for e in kate gedit pluma;do if test -e /usr/bin/$e;then sudo $e /etc/default/rcS;fi;done

# assume that the BIOS clock is set to UTC time (recommended)
UTC=no
Posted on Reply
Add your own comment
Nov 23rd, 2024 20:15 EST change timezone

New Forum Posts

Popular Reviews

Controversial News Posts