Unable to activate my win10pro virtual machine after changing hardware

Question

Unable to activate my win10pro virtual machine after changing hardware...
Originally was activated with Win8, in a VirtualBox machine, and have had ongoing issues. Was upgraded to Win10 many years ago, but again have had ongoing issues (with the VM.)

Decided to change to QEMU/KVM, using a VDI image from VB, and after many issues (mostly booting), decided to do a fresh install. Fresh install was done with the same disk image (VDI), and after up and running, I managed to get it activated OK.

I then decided to convert the disk image to a QEMU image (qcow2), and this seemed to work OK, EXCEPT Windows decided to remove/cancel the activation. Have tried everything to reactivate, but get the message

Wondering how to proceed with this?
It is still a genuine version, so I would believe the activation should be fine!?

Thanks.

Answer 1

Was this post approved? Has it actually been published??

Got an email telling me my thread was undermoderation review (for what??), and never received anything else??

Answer 2

Hello, JOHN BENNETT.

Quote: "Originally was activated with Win8, in a VirtualBox machine, and have had ongoing issues. Was upgraded to Win10...."

Unfortunately, Windows 10, which was received as part of the free upgrade promotion from genuine 7/8/8.1 in 2015-16, is permanently linked to the device that participated in the promotion and cannot be transferred. These were the terms of the action. Subsequently, Microsoft completely blocked the possibility of activating Windows 10/11 with keys from previous operating systems.: https://devicepartner.microsoft.com/en-us/communications/comm-windows-ends-installation-path-for-free-windows-7-8-upgrade

That is, if the license for this Windows 10 was obtained by a free upgrade from Windows 8, then a separate license for the standalone (BOX or ESD) version of the OS will be required to install on another device (physical or virtual).

Answer 3

Changing the virtual hardware (moving from VirtualBox to QEMU/KVM and then converting the disk to qcow2) is treated by Windows as a significant hardware change. The existing digital license is bound to the old virtual hardware, so Windows now reports that the digital license has already been used and won’t reactivate automatically.

Use these supported options:

1. Try the Activation troubleshooter (only if not already exhausted):
   1. In the VM, sign in with an administrator account that’s linked to the same Microsoft account previously used for activation.
   2. Go to Start > Settings > Update & Security > Activation.
   3. If Windows shows as not activated, select Troubleshoot.
   4. If offered, choose I changed hardware on this device recently and follow the prompts to see if the exception path can re-bind the license.
2. If the troubleshooter cannot reactivate and reports that the digital license has already been used, the supported paths are:
   • Enter a valid product key that was previously used on this VM before the hardware change: in Settings > Update & Security > Activation, select Change product key and enter the key.
   • Or purchase a new Windows 10/11 license: in Settings > Update & Security > Activation, select Go to Microsoft Store and buy a genuine copy, then activate.
3. If the license was a digital license with no product key and the troubleshooter cannot transfer it, contact Microsoft support so an agent can review the activation history and, if eligible, reactivate the license for the new virtual hardware.

Note that if the original activation came from an upgrade path (for example, from Windows 8 on different virtual hardware) and that digital license has already been used for reactivation after a hardware change, Windows may require a new license for the new VM.

---

References:

• Reactivating Windows after a hardware change
• Using the Windows Activation troubleshooter
• Get help with Windows activation errors
• Why can't I activate Windows?
• Unable to activate windows after hardware update - Microsoft Q&A
• Windows reactivation fails - Microsoft Q&A
• Unable to use troubleshooter for windows activation - Microsoft Q&A