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 reused a Win10 Pro key from a mini PC from 2015 onto a brand new build and it worked right away. Not sure what the difference is with your situation. Maybe it was your license type?
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.
When I build a new PC, I could not transfer my old 7 pro retail license, even though it worked fine on my old PC running Windows 10 and it even said it was a digital license connected to my MS account.
So I bought a Win 10 pro key from one of the ebay resellers aber everything was fine… until it wasn’t. I updated the firmware for my mainboard and Windows took that for a replacement of hardware. Troubleshooter did not show three option “I recently changed my hardware” and did not give me the option to call Microsoft’s support.
Turns out it was a “one time install” key which was invalidated by changing the hardware. So it couldn’t activate a second time. And since the key seller was out of business at that time (they’ll change accounts every few months), I had no way of getting the key replaced.
Luckily, I still had an old Windows 7 COA with key and CD lying around from an old Dell business Workstation. That activated just fine.
But yeah, even if you have a valid license connected to your Microsoft account, there’s no way of seeing it in your account, and it’s not guaranteed MS will honor it.
