Windows required CPU’s to have certain extensions/instructions to use the newest version, which might have required buying a new CPU and thus getting one of the affected ones. However, I don’t think it’s reasonable to blame Microsoft for this.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
No game suggestions, friend requests, surveys, or begging.
No Let’s Plays, streams, highlight reels/montages, random videos or shorts.
No off-topic posts/comments, within reason.
Use the original source, no clickbait titles, no duplicates.
(Submissions should be from the original source if possible, unless from paywalled or non-english sources.
If the title is clickbait or lacks context you may lightly edit the title.)
Wat. This has nothing to do with Windows 11 system requirements.
Windows required CPU’s to have certain extensions/instructions to use the newest version, which might have required buying a new CPU and thus getting one of the affected ones. However, I don’t think it’s reasonable to blame Microsoft for this.
M$ is not the source of this problem, but they did force TPM 2.0 on their OS, forcing people to throw away older CPUs, so they made it much worse.
Oh yeah, I forgot about TPM 2.0 and was just thinking about
POPCNTetc.