Andrew_GrahamHi, We are running a network using a Windows Server. I have no problems activating on my development machine but when I try to activate on other machines on the network TurboActivate detects them as Virtual machines or hypervisors (sometimes one, sometimes the other) and won't complete the activation.Any suggestions as to what is wrong?
First, make sure you're using the latest version of TurboActivate (currently, 4.0.9.6), then try again. If it's still saying you're in a VM, then see our FAQ: https://wyday.com/limelm/help/faq/#in-vm
If you don't have Hyper-V enabled but TurboActivate *still* says you're in a VM (and you went through all the steps in the FAQ -- disabling Hyper-V, restarting the system, etc.), then we'll collect more information from you to see if it truly is a false-positive.
Andrew_GrahamHi, I've located the problem. If the BIOS is set to enable virtual machines then TurboActivate detects this as a virtual machine even though no virtual machine is being used.
No, that's not true. You can enable VT-d (a setting in bios that gives processors better functionality when running VMs) and it will have no effect with respect to TurboActivate. Namely, TA will correctly detect VMs whether you have that setting set or not.
Hyper-V, however, might have not booted up because you disabled the VT-d setting. So you have taken the long way around to disabling Hyper-V. See the FAQ for the easier way.
