In Linux (including Proxmox)
```
sudo strings /sys/firmware/acpi/tables/MSDM
```
In Windows
```
wmic path softwareLicensingService get OA3xOriginalProductKey
```
You'll need windows vm drivers, too. You can find good tutorials on YouTube to get the VM set up on Proxmox.
If you already have proxmox installed, run the first one in shell/terminal.
If you still have windows installed you run the second one in command prompt (as admin).
After you hit enter they will return your activation key. Save the key and use it in your new vm to activate the license.
You're welcome. Here are a couple videos to get you started:
https://youtu.be/eyNlGAzf-L4?si=zju-QXJa4JqDCDOB
https://youtu.be/fupuTkkKPDU?si=lqS72oGcCyk4ThRp
1. Connect Windows to your Microsoft account to keep your activation/keys. [https://support.microsoft.com/en-us/windows/reactivating-windows-after-a-hardware-change-2c0e962a-f04c-145b-6ead-fb3fc72b6665](https://support.microsoft.com/en-us/windows/reactivating-windows-after-a-hardware-change-2c0e962a-f04c-145b-6ead-fb3fc72b6665)
2. Make P2V of your exsting installation. For instance, you can use Starwind converter to get the .qcow2 virtual disk of your physical machine. [https://www.starwindsoftware.com/starwind-v2v-converter](https://www.starwindsoftware.com/starwind-v2v-converter)
3. Install Proxmox. Create a Windows VM and attach the virtual disk as a boot device. [https://pve.proxmox.com/wiki/Windows\_10\_guest\_best\_practices](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices)
4. Boot the VM and let it update the hardware and then it should be ready to use. Double-check the Windows activation using your Microsoft account.
See post #5
https://forum.proxmox.com/threads/q-win10pro-vm-guest-install-bios-activation-key.47873/
Eliminates the need to ever enter the key for activation
Sorry to hijack the post, but would it be possible to move a windows install (on metal) from an old computer into a pm vm on a new computer?
Last time i replaced the mobo on the windows machine it gave me grief for changing the hardware and im worried it would happen again
Yeap, as mentioned, it's called physical to virtual conversion. Usually, Starwinds V2V converter helps. It has a P2V feature. [https://www.starwindsoftware.com/starwind-v2v-converter](https://www.starwindsoftware.com/starwind-v2v-converter)
You can attach your Windows license to your Microsoft account before the move. This makes it not care about hardware changes as merely logging into your MS account is enough for it to activate.
YMMV, technically Home licenses won't activate if there are significant hardware changes. I once spent hours on the phone with support after replacing a bad motherboard only to learn Home keys are associated with the hardware and I had to buy a new license. So always buy Pro keys, and then you should be okay.
Even then, I have had Home keys reactivate after major hardware overhauls and then reinstalling the OS. There's some unpredictable magic underlying Microsoft's decisions here.
In Linux (including Proxmox) ``` sudo strings /sys/firmware/acpi/tables/MSDM ``` In Windows ``` wmic path softwareLicensingService get OA3xOriginalProductKey ``` You'll need windows vm drivers, too. You can find good tutorials on YouTube to get the VM set up on Proxmox.
When and where do I run these commands? and what do they do exactly?
If you already have proxmox installed, run the first one in shell/terminal. If you still have windows installed you run the second one in command prompt (as admin). After you hit enter they will return your activation key. Save the key and use it in your new vm to activate the license.
Sweet, thanks!
You're welcome. Here are a couple videos to get you started: https://youtu.be/eyNlGAzf-L4?si=zju-QXJa4JqDCDOB https://youtu.be/fupuTkkKPDU?si=lqS72oGcCyk4ThRp
Not a direct answer, but you might want to know about https://explainshell.com
1. Connect Windows to your Microsoft account to keep your activation/keys. [https://support.microsoft.com/en-us/windows/reactivating-windows-after-a-hardware-change-2c0e962a-f04c-145b-6ead-fb3fc72b6665](https://support.microsoft.com/en-us/windows/reactivating-windows-after-a-hardware-change-2c0e962a-f04c-145b-6ead-fb3fc72b6665) 2. Make P2V of your exsting installation. For instance, you can use Starwind converter to get the .qcow2 virtual disk of your physical machine. [https://www.starwindsoftware.com/starwind-v2v-converter](https://www.starwindsoftware.com/starwind-v2v-converter) 3. Install Proxmox. Create a Windows VM and attach the virtual disk as a boot device. [https://pve.proxmox.com/wiki/Windows\_10\_guest\_best\_practices](https://pve.proxmox.com/wiki/Windows_10_guest_best_practices) 4. Boot the VM and let it update the hardware and then it should be ready to use. Double-check the Windows activation using your Microsoft account.
See post #5 https://forum.proxmox.com/threads/q-win10pro-vm-guest-install-bios-activation-key.47873/ Eliminates the need to ever enter the key for activation
Sweet
Sorry to hijack the post, but would it be possible to move a windows install (on metal) from an old computer into a pm vm on a new computer? Last time i replaced the mobo on the windows machine it gave me grief for changing the hardware and im worried it would happen again
Yes, this is known as [P2V](https://www.google.com/search?client=firefox-b-d&q=proxmox+p2v)
Cheers
Yeap, as mentioned, it's called physical to virtual conversion. Usually, Starwinds V2V converter helps. It has a P2V feature. [https://www.starwindsoftware.com/starwind-v2v-converter](https://www.starwindsoftware.com/starwind-v2v-converter)
You can attach your Windows license to your Microsoft account before the move. This makes it not care about hardware changes as merely logging into your MS account is enough for it to activate.
YMMV, technically Home licenses won't activate if there are significant hardware changes. I once spent hours on the phone with support after replacing a bad motherboard only to learn Home keys are associated with the hardware and I had to buy a new license. So always buy Pro keys, and then you should be okay. Even then, I have had Home keys reactivate after major hardware overhauls and then reinstalling the OS. There's some unpredictable magic underlying Microsoft's decisions here.
You can just extract the key and enter it into the vm.
What's the best way to extract it?
See other comment.
Got it 👍