Windows 10: Personalization possible pre-activation in VMware, not Hyper-V. Why?

I have an observation that has led me to a question...

Normally, when Windows 10 is installed, changes to the personalization settings are not possible until you activate Windows. However, I have noticed that both on a physical machine and when Windows is installed in VMware Workstation, so long as the network adapter is disabled, you can successfully change personalization settings. Once you enable the network adapter and Windows communicates with the activation servers this capability is lost, even if you disable the network adapter again.

In Hyper-V this is not true. Even with networking disabled, personalization is not possible until Windows is activated.

I'm just curious to know if anyone has any idea on what the underlying cause for the difference in behavior might be.

Note that this is not any attempt to bypass activation. It's just that I sometimes configure a VM just to perform a couple of quick tests, then I destroy that VM. Along the way I simply noticed this behavior.

I believe that I may have previously asked this question in the context of another issue quite some time ago, but thought that I would just give this one more try to see if anyone had any ideas.

:)

 

Hyper V

Please Mississippi State IT student do not respond. The last of you that replied didn't know what the hell he was talking about. I will repeat my question. I opened Hyper-v and ran Fedora for about three days. I got a free copy of VMware. VMware and
Hyper-v are not compatible. I have VMware for 30 days, I have Hyper-v forever. How do I disable Hyper-v so that VMware does not see it?

 

Cannot turn off Hyper V, cannot run Virtual Box machines or VMWare machines

Since the latest update:

Edition: Windows 10 Pro

Verion: 1607

OS Build: 14393.222

I can no longer turn off Hyper V and thus cannot run Virtual Box machines or VMware machines.

When I attempt to turn off Hyper V and restart Windows as requested, Windows simply re-enables Hyper V.

Then when I try to run a Virtual Box machine, I get an error like this:

Failed to open a session for the virtual machine Centos 70.

VT-x is not available (VERR_VMX_NO_VMX).

Result Code:

Component:
ConsoleWrap

Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

When I try to start a VMware machine, I get this:

VMware Player and Hyper-V are not compatible. Remove the Hyper-V role from the system before running VMware Player.

But as I have noted, I am not able to turn off Hyper-V since the Anniversary Update.

Any suggestions would be greatly appreciated.

 

VMware is not working in Windows 10 Home edition due to "Hyper-V role".

I use VMware Workstation Player 14 as a Virtual Machine runner. However, when I try to run a virtual machine, VMware tells me:

VMware Player and Hyper-V are not compatible. Remove the Hyper-V role

from the system before running VMware player.

I know that Windows 10 Home does not have Hyper-V but VMware says it does, and I have not been able to run a virtual machine since.

Can anyone help me?