No, there shouldn't be false VM detection. We're putting together a tool that will allow us to debug this. I'll email you early tomorrow with the tool.
Virtual Machine Detection
I have a product key with "Allow virtual machine activation?" set to disallow.When I try and activate I'm receiving the can't activate virtual machine exception. I am testing on a windows 8 machine outside of any virtual machine. If I allow VM activation it works fine.Is there something that might be causing a false VM detection?
Thanks. When I tested the activation on a Win 7 machine that was a non development machine it activated perfectly.On my win8 dev machine where it failed I do have Hyper-V enabled but had no active VMs running or in use when trying to activate.
where it failed I do have Hyper-V enabled but had no active VMs running or in use when trying to activate.
Oh, well that's it. Hyper-V is a Virtual Machine. Your base operating system is actually running as an instance on Hyper-V.
Ah ok. I didn't realize enabling the Hyper-V feature in win8 caused the base os to also run as a VM instance per se or would be detected as a VM for LimeLM.
I had thought any VM's I added through the hyper-v manager would not allow product activations but the base OS would.
I didn't realize enabling the Hyper-V feature in win8 caused the base os to also run as a VM instance per se or would be detected as a VM for LimeLM.
Yeah, that's just the design of Hyper-V -- everything, including the base OS, runs atop the hypervisor. It's different than say VMWare or Virtual Box, both of which are self-contained VM's that run atop a non-VM instance.