410
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 28 Sep 2023
410 points (100.0% liked)
Technology
60704 readers
3166 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
There could be a bit of a caveat here. I when I purchased my laptop it had windows 10 installed. When I installed Mint, I could not reuse that key in a VM because it was “different hardware”. The license, could not be transferred under any circumstance. I had also purchased the upgrade to Pro through the windows store. That’s also lost.
I seldom run windows, even in the VM, but it still leaves one a bit bitter.
Usually calling Windows support, they'll give you a key if you just tell them you replaced some piece of hardware due to failure, assuming you haven't been transferring the same key around for awhile. They tend to be more invested in keeping you in the Windows ecosystem than they are are just getting one more license sold.
I called support, they said no. Asked for a one time exception, still no. The key to my knowledge was only used once on the laptop when I bought it new.
I wasn’t investing any more time in it.
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.
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.