this post was submitted on 28 Sep 2023
417 points (96.9% liked)

Technology

59314 readers
4948 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
L3s@lemmy.world
L3s@fry.gs
L4s@fry.gs
L4s@lemmy.world
enu@lemmy.world
417
You can no longer activate new Windows 11 builds with Windows 7 or 8 keys; maybe last chance to activate using Windows 7 or 8 keys, for 22H2. (www.neowin.net)
submitted 1 year ago by Raisin8659@monyet.cc to c/technology@lemmy.world
124 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[โ€“] Honytawk@lemmy.zip 1 points 1 year ago (1 children)

Windows 10 links their license to the motherboard.

So as long as you use the same motherboard, the key will work.

This isn't possible with VMs sadly.

[โ€“] mystik@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

You can extract the SLIC value from the ACPI table, and then pass it through to QEMU

See more details here: https://gist.github.com/Informatic/49bd034d43e054bd1d8d4fec38c305ec

It is my understanding that this can only be used to run the OEM license one one instance in a VM, on the specific hardware that is originally licensed. IE, you virtualize the license if the bootOS is Linux, but you can't run 2 instances of the same windows license inside each other.