This restriction is on boot.wim? If is on it i can change boot.wim with an boot.wim Win10 for exclude restriction?
restriction are for 24h2 ( boot.wim and install.wim or install.esd ) popcnt are requirement like windows 8.0 to 8.1 cpu instruction
Why does Microsoft play these games (I mean this isn't just a simple case of locking someone out for piracy)?
bcuz u have 2 cut the cord at some point or there will b idiots bitching that 24h2 doesn run on thier 386 i think droppin suport 4 15yo cpus is perfectly fine
Still not a good enough excuse. Alienating your user base is bad business no matter how you put it, but it is Microsoft, and they are masters of bad business decisions. I guess I'm the loser here for expecting better answers than those.. Never mind, I'll take my business elsewhere.
I don't mind them going forward with more modern instructions. In fact, I welcome it with open arms. What I don't like is poor communication and artificial restraints.
Yeh, I am OK too with drawing a line on OLD HARDWARE that is no longer fit for use with any software. Technology moves on. ------ Want to use old hardware still and the latest Windows 11, well PLENTY OF OLD COMPUTERS 15 years old that will still work with POPCNT going real cheap that will do the job. Well within the poorest budgets to get those.
Come on! You can't be serious. Do you really think that any sane minded person would use productively Win11 24H2 on a 15 y/o machine? That's just matter of curious kids, who want to do that "just because". For sure it doesn't move by 1 cm the Windows' market share, and 99.99999 of users do not care (and do not know anything about this hard blocker).
Could anyone recommend the last working and last usable Win11 24H2 version(s) for such systems like Athlon 64 Core 2 Quad etc. ? I have ceramic caps.
Like in the linked original thread was extensively discussed any 253xx and previous builds are not affected. The last ready made ISOs should be Server11 25379.1 and Win11 25393.1. Maybe there are sligtly newer builds on UUPdump
No problem about expiration, my SKUwitch is your best friend To say better no problem except for the usual Vbox hardening, that checks more thoroughly than MS itself and won't start because some expired certificates. Funnily enough this is not a problem for a system (in theory) expired in 2013
Frankly I never care of 2XHY, (I don't even remember which is the first build marked as 24H2) the point is that with slight variations SKUwitch works since Vista. That said for the purpose of this thread obviously it works ONLY for 253xx and earlier builds, given the newer ones won't boot at all.