Quote from: SK Unices on October 19, 2021, 08:44:27
Well, this was clickbait and a half.
I can't believe people don't realize what/why the minimum specs are there for - such as not taking a 15-30% performance hit when security features are functional, and the fact that they're baselining on a specific (Skylake-X) version of the x86_64 ISA, so the 'future updates may not work' is because they WILL be taking advantage of new hardware features in security/functional updates.
Remember when Windows 10 dropped support for entire 64 bit multi-core CPU families due to an update issue? Remember when Windows 7 suddenly lost pentium 3 support due to an update? Or when Windows 8.1 and server 2012 R2 came out and completely dropped support for an entire generation of x86_64 processors?
What's happening in the first RTM copy (which is hot off the build system they were using to provide copies to run on unsupported systems in insider program for data/compat/config/firmware metrics/etc collection) is entirely unsurprising.
And "windows update still works!" .... well, yes, the whole point was that future updates may fail, just like how the Windows 7 update killed the OS on a slew of older systems.....
in first place: Windows 7 dropping CPUs without SSE happened nearly 9 years after it's release, and a bunch of the affected CPUs did actually meet Windows 7 requeriments (1 GHz x86 CPU or faster), mainly the late >1 GHz Penitum 3s and the AMD Athlon XP (which competed against the Pentium 4, but lacked SSE2). The same issues also affected Windows Embedded POSReady 2009 as well, the later based on Windows XP and consequently affecting Windows XP with the POSReady hack as well. Also keep in mind Windows 7 never enforced an SSE2 requeriment until said update came nearly 9 years, it was an stealth change and when MS acknowledged that, they decided to not fix it and start requiring SSE2.
Windows 8.1 and Server 2012 R2: yeah, they dropped early x86_64 CPUs on the 64 bit versions by requering CMPXCHG16b (CX16), LAHF-SAHF y PREFETCHW instructions, which basically killed all 90nm Netburst chips and AMD K8 CPUs before Windsor based Athlon 64 X2s. However these requeriments didn't affected the 32 bit versions of Windows 8.1 and 10. MS did warn about them and these old CPUs were incompatible since day one,
Windows 10 only dropped a certain CPU after it's release and it happened to be the older Atom Z2xxx line and they were dropped because of incompatible graphics drivers for their integrated graphics (that specific Atom line used PowerVR based graphics that didn't have updated driver and breaks on Windows 10 versions past 1607).
Also Windows 11 is technically the first Windows version to start enforcing CPU support, Windows 7 didn't enforce a supported CPU list, same for 8.1 and 10. Also saying the Skylake-X ISA is kinda exaggeratting since that one even includes AVX-512, which is NOT present in all mainstream Intel CPUs other than Tiger Lake or Rocket Lake, also still no AMD CPU features AVX-512 yet. also Windows won't be requering AVX anytime soon considering a bunch of the officially supported CPUs still lack AVX (see Coffee Lake and Comet Lake Pentium and Celeron), and requering AVX-512 would mean even killing almost all supported intel cpus and all AMD CPUs. Requeriment changes may change in the future
Requiring SSE4.1 or 4.2: Probably, but who knows
Requiring AVX: Not anytime soon, as long there are current generations and supported CPUs without AVX in the market