On Windows 11 Pro host, Microsoft deactivated my Window 10 VMware VM and recovering is flaky

I ran my VMware Windows 10 VM yesterday and it came up unactivated, complaining about "hardware change" with the always helpful hex-style error code 0xC0EA000A. I went through the Troubleshooter, and it started by hooking my local account up to a Microsoft account, telling me I would need to use the email address to log in next time, which I had to undo. Then as the final step, it asked me to confirm the machine I was using was my Windows 11 host, which is my main PC I want to keep out of this mess. Any idea how to best proceed? (I will not call Microsoft ever again. They strung me along last time concerning my main PC and hung up on me after an hour long ordeal, after I read them from their web site all the reasons I didn't want to try a repair install.)

barreleye said:

I will not call Microsoft ever again

Click to expand...

Never say never, especially when it comes to activation issues because many times MS is the only one who CAN help you resolve activation issues.

Were you using the same underlying license key for the 10 VM that you use for your 11 install. If so, that's the issue. A VM has to have it's own license. It does not use that of the host. If the VM had it's own license, what kind of license was it and for what version of windows. Microsoft licensing does not differentiate between a physical or virtual installation. No 2 machines can use the same license.
It would be helpful if you would fill out your device specificatios in your forum profile.

glasskuter said:

Were you using the same underlying license key for the 10 VM that you use for your 11 install.

Click to expand...

Separate licenses. I have another Windows 10 VM and one Windows 11 in VMware that were not affected. The Windows 10 machines are both at least 5 years old.

Certain changes to a VMware instance will alter the HW signature presented to Windows for licensing purposes.

If you run the Troubleshooter tool, it's very dumb and doesn't understand if you're running in a VM or not. It's programmed to suggest you open your MS Account and look for previous digital activations, in the hope it may be already linked for this Windows.

Have you tried to re-install the same product key used to license this VM the first time? Digital license activation only works if the server detects a previously known HW signature. Once it changes, MS thinks you have a different "PC".

garlin said:

Certain changes to a VMware instance will alter the HW signature presented to Windows for licensing purposes.

If you run the Troubleshooter tool, it's very dumb and doesn't understand if you're running in a VM or not. It's programmed to suggest you open your MS Account and look for previous digital activations, in the hope it may be already linked for this Windows.

Click to expand...

That sounds about right.

Have you tried to re-install the same product key used to license this VM the first time? Digital license activation only works if the server detects a previously known HW signature. Once it changes, MS thinks you have a different "PC".

Click to expand...

I did, and it didn't work. It was a key I got with free MSDN as an MVP for 10+ years. My remaining unused keys from those days no longer work, either. They were all for Windows 7 Pro and Ultimate, and they used to work for Windows 10. Now they're giving me "Unable to activate Windows" 0x803fa067. Oh well, it was nice while it lasted!

The free upgrade path from W7 key -> W10 (W11 uses the same licensing) has been closed for a few years now. It was never intended to be forever, but MS didn't bother closing the loophole for so long people thought it was a permanent thing. Turns out it wasn't forever.

If your vm is PRO you can activate one of the cheap license keys. I bought one from StackSocial and it activated as retail without any problem.
While it's always a gamble, for $13 I'd give it a try. Microsoft Windows 11 Pro | StackSocial

garlin said:

The free upgrade path from W7 key -> W10 (W11 uses the same licensing) has been closed for a few years now. It was never intended to be forever, but MS didn't bother closing the loophole for so long people thought it was a permanent thing. Turns out it wasn't forever.

Click to expand...

I do vaguely remember hearing that.

glasskuter said:

If your vm is PRO you can activate one of the cheap license keys. I bought one from StackSocial and it activated as retail without any problem.
While it's always a gamble, for $13 I'd give it a try. Microsoft Windows 11 Pro | StackSocial

Click to expand...

I've had good luck with Groupon the last couple of years for Windows 11 Pro keys, around $8. This VM is not worth the trouble. It was just annoying, especially what the Troubleshooter did and wanted me to do before I balked.

after reading the above i am not sure if you have tried 'change product key'
settings > system > activation > upgrade your edition of Windows > change product key
then on the right click 'change'

put the same product key you all ready have into the product key box
and then see if the system re-activates.

i have had to do this on a clean install when things went fubar upgrading to 24H2
if nothing else its worth a try.

you can also find out what product key is being used on the Windows VM
before trying to re-activate with your key or another key.

best of luck Steve ..

Tip: Once you activate a Windows VM in VMware, locate the .VMX file for the VM and oipen it in Notepad. Save the line that starts with "uuid.bios"

The next time you install your VM from scratch, create the initial VM but before you boot from your Windows ISO image to install Windows, open the VMX file and replace the UUD.BIOS line with the line you saved. After installing Windows, it should auto activate so long as you have internet access. Note that you can make this change after Windows is installed as well if you wish.