this post was submitted on 13 Feb 2024
589 points (97.3% liked)

Technology

59374 readers
6264 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 56 points 9 months ago* (last edited 9 months ago) (4 children)

In modern x86 CPUs, POPCNT is implemented as part of the SSE4 instruction set. For Intel's chips, it was added as part of SSE4.2 in the original first-generation Core architecture, codenamed Nehalem. In AMD's processors, it's included in SSE4a, first used in Phenom, Athlon, and Sempron CPUs based on the K10 architecture. These architectures date back to 2008 and 2007, respectively.

That effectively bars mid-2000s Intel Core 2 Duo systems and early Athlon 64-era PCs from booting Windows 11 at all, not that they officially supported it in the first place. This means the change should mainly affect retro-computing enthusiasts who spend their days making YouTube videos in the "we installed Windows 11 on a potato, let's see how it runs" genre rather than users of actual systems.

You can check if your CPU has SSE 4.2(Intel) or 4a(AMD) but it sounds like unless you're running some real old stuff you shouldn't have to worry.

[–] [email protected] 25 points 9 months ago* (last edited 9 months ago) (1 children)

But isn't Microsoft just so evil for making it so their operating system doesn't function flawlessly on twenty year old hardware?

load more comments (2 replies)