this post was submitted on 28 Jul 2024
214 points (100.0% liked)

PC Gaming

8524 readers
1009 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments.
  10. 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.)

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Flatfire@lemmy.ca 9 points 3 months ago (1 children)

Wat. This has nothing to do with Windows 11 system requirements.

[–] qaz@lemmy.world 17 points 3 months ago* (last edited 3 months ago) (1 children)

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.

[–] msage@programming.dev 15 points 3 months ago (1 children)

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.

[–] qaz@lemmy.world 3 points 3 months ago

Oh yeah, I forgot about TPM 2.0 and was just thinking about POPCNT etc.