Share via

How to unlock an authentic activation code for Windows 11 pro when moved to a new PC / virtual machine?

Anonymous
2024-12-03T11:18:00+00:00

I am trying to activate WIN11PRO on a virtual machine created on a Truenas Scale NAS/ Server. I've purchased a new licence for that on a reseller's website (with invoice and receipt).

I've made a few attempts to come to complete installation due to the virtual machine configuration, so I actually entered a few times the activation code (which every time was acknowledged as valid), but one time only I completed the WIN11PRO installation, which of course is the last one. Now, installation is complete, and the systems requires me to activate the product, when entered the activation code the feedback is activation is not possible because that code has been already used on another device. It is not clear to me if previous attempts on previous incomplete virtual machines can count as such.

The error code is 0xC004C008

Troubleshooting is not click-able and when clicking the "get help" option, and providing the product ID / installation ID, I am brought here.

Hoping the code received by the reseller is authentic, I need to tell Microsoft's systems that this very code must be assigned to the running virtual machine only. Secondly, a double check on the authenticity might be worth, and in that case I'll need evidence to protect my rights by challenging the seller (and informing Microsoft).

I'd be truly thankful to anyone providing advice on this.

Windows for home | Windows 11 | Licensing and activation

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

  1. Virginia M 40,820 Reputation points Independent Advisor
    2024-12-04T17:19:42+00:00

    Glad to hear support solved the problem.

    Give back to the Community. Help the next person who has this issue by indicating if this reply solved your problem. Click Yes or No below.

    If you still require help then please continue the thread.

    Thank you & have a great day/evening.

    1 person found this answer helpful.
    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-12-04T14:55:41+00:00

    Thanks Virginia. Indeed, the cause of the problem must have been the repeated use of the same key when configuring the VM, even if only the last attempt led to full installation. So, there was no way of removing the key before uninstalling the VM. Luckily, despite some difficulites navigating the on line help's options, I ended up being called by Microsoft and everything was solved sharing the unique installation code on the phone.

    So, in short, when this happens I can suggest to get in touch with support and ask being called.

    Nevertheless, thanks much for your timely advice!

    0 comments
  2. Virginia M 40,820 Reputation points Independent Advisor
    2024-12-03T15:41:10+00:00

    Hello, I’m Virginia, a fellow user like yourself.

    Sorry to hear you’re experiencing problems. May I ask which Windows 10/11 build are you running - 22H2 (Win 10/Win 11) or 23H2 (Win 11)?

    I understand you’re having problems with activation, Don’t worry as I’ll do my best to assist you today.

    If you purchased an OEM key then it would be connected to the first installation it was used on, any reinstalls of the same should activate but with moving the key to a VMs this may be different so the key may no longer be valid as it would show as a different installation. Did you remove the key from the PC & also every time before deleting the VMs & using again?

    Most likely the key was a KMS/volume license which has reached the max number of activations.

    To see the installed key:

    Right click on start & choose powershell with admin & enter: slmgr.vbs /dlv

    This will show a popup showing whether your license is OEM, Retail, or Volume amongst other information.

    However as this is being run within a VM it may not work or it may show the PCs activation rather than the VM.

    0 comments