3 ms·
Calling these processors unsupported for Windows 10 is dubious. The official minimum CPU specification for Windows 10 only mentions PAX, NX, SSE2, CMPXCHG16B, L
by ack_complete 3y ago
Calling these processors unsupported for Windows 10 is dubious. The official minimum CPU specification for Windows 10 only mentions PAX, NX, SSE2, CMPXCHG16B, LAHF/SAHF, and PREFETCHW, not SSE4:
https://learn.microsoft.com/en-us/windows-hardware/design/minimum/minimum-hardware-requirements-overview https://learn.microsoft.com/en-us/windows-hardware/design/mi...
There is a more general Windows Processor Requirements doc that does drop a number of old CPUs off of the list for newer builds:
https://learn.microsoft.com/en-us/windows-hardware/design/minimum/windows-processor-requirements https://learn.microsoft.com/en-us/windows-hardware/design/mi...
However, this is not surfaced to the user nor are there compatibility blocks to prevent auto-upgrades to newer builds, and the page specifically says this:
> Changes to the processors listed do not indicate or impact a customer’s existing Windows support and are intended for OEMs to determine processors which may be used in new Windows devices.
If Microsoft wants to raise the minspec to maintain a reasonable support window, more power to them. I can't see how apps suddenly crashing is a good way to do this. It has to be an unintentional bug.
- lousken 3y agoon one hand - it's not really windows 10 related, these are windows store apps (even though preinstalled), and core 2 duos are 18 year old at this point but it's true that maybe the store should start blocking old systems from updating such apps instead
- cptskippy 3y ago> core 2 duos are 18 year old at this point I recall that Microsoft periodically drops support for versions of Windows 10 AND drops support for hardware with newer versions. It looks like Windows 10, version 1909, which fell out of support in 2021, only supports Nehalem (2008) or newer CPUs. I didn't dig further back to see when support for Core 2 Duos was dropped but this makes me wonder what version of Windows 10 these folks are running. Are they running 22H2 on unsupported hardware, or 1909 which just isn't supported. If it's the later case and old versions like 1909 aren't supported, shouldn't they just be excluded from these Windows Store releases entirely? Is this just a matter of someone not specifying the correct OS version to target in the Store deployment?