Windows 10 activation error 0xC004F034

If you are looking for a Digital License (HWID) Generation activator then that's not allowed here in MDL.


Or perhaps you were talking about genuine HWID activation.

 

Maybe you would like to talk a bit more about your Windows.
This is a typical error when installing Pro or any other version on a computer that has a Home or Home Premium installed on the factory and later user goes to install Windows 10 Pro, but does not observe the installation rules.

 

greetings
Is it possible to have a virtual machine "VMware or Hyper-V" with the same UUID of a physical machine to be activated as Digital License (HWID)
my logic if I activated the physical using a genuine Windows 10 Pro Key & create a VM using same UUID from MS prospective it should be activated
Kindly advise

 

Why don't you just generate a HWID for the VM install, that VM will keep the HWID.

 

because it is not worth it financially to buy a genuine Key to activate a VM. while you use the physical activated HWID to activate a VM for testing other things and you can always revert it back to original state

 

I said, generate a HWID, nobody said to buy anything, we are at almost 3.5 years of HWID now

 

sorry i got it wrong
i did activate physical using HWID & created a VM with the same UUID of the physical using "UUID_Conv.exe" but it didn't activate. Maybe I'm doing something wrong

 

Tools can be permanently activated, of course not including LTSC.

 

You can't "duplicate hwid" simply by duplicating UUID.In fact I think it is not possible at all.Simply use free upgrade from 7 ultimate to 10 pro to generate a hwid for virtual machine.

 

It has been done between VM's in the past, iirc it was @s1ave77 who did it.

But with all the new insights about hwid generation on the fly, why not just generate one for the VM.

 

Never did from physical machine to virtual . You definitely can transfer the UUIDs from one VM to another by preserving the license, was used for the first KMS Hosts that where leaked as VMs.

 

The same I was unable to move HWID activation between Hyper-V & VMware VM's

 

Don't give up just yet. LTSC will be added to the list soon, I believe.

 

KMS2038 isn't long enough?

 

That works fine. I was just talking about a DL for LTSC.

 

Not seeing it happen

 

No problem then. KMS2038 is fine.

 

LTSC cannot automatically activate numbers. Of course, it is enough to use KMS activation.