131 results found
Also, ensure your BIOS doesn't have a built-in Xen hypervisor (some Dell laptops and other corporate-style laptops do).
I am tryting to run WSV3 on Windows 11 and It says I need ti disable Hypervisor. I had it on and off and it does not work.
Here's why: https://wyday.com/limelm/help/vm-hypervisor-licensing/
From turboactivate.h among others: “The function failed because this instance of your program is running inside a virtual machine / hypervisor and you've prevented the function from running inside a VM.”
See: Licensing from inside a virtual machine or hypervisor
See: http://wyday.com/limelm/help/vm-hypervisor-licensing/ http://wyday.com/limelm/help/using-turbofloat/
Well no - it's no hypervisor and the VMware product is VMware player.
See: Licensing from inside a virtual machine or hypervisor
Next, don't allow activations on VMs (use TurboFloat instead): https://wyday.com/limelm/help/vm-hypervisor-licensing/
More and more of our customers are refusing to disable Hypervisor, as on many new Windows 11 PCs it is enabled by default.
Just tried activating TurboFloat Server on an old physical machine running Windows Server 2003, but got the error: "Can't activate within a virtual machine or a hypervisor". Was the error because of the old version of Windows?
That's what a ring-0 hypervisor is (the Windows you're running under is in a VM).
The solution is TurboFloat: https://wyday.com/limelm/help/licensing-types/#floating https://wyday.com/limelm/help/vm-hypervisor-licensing/
i have allowed VM Activations for the product and tried installing TurboFloatServer on VM but i am getting can't activate inside a VM or hypervisor can u tell me what is next way to do to make it work on VM
Perhaps it is possible to improve the virtual/hypervisor detection, but is not a big priority. Actually it is more a feature than a bug 🙂
See here: Licensing from inside a virtual machine or hypervisor. And if you even want to prevent trials on VMs, then again, use UseTrial(TA_DISALLOW_VM).
The did however send us msinfo output, I see that "Hypervisor based security" and specifically "Credential Guard" is enabled.
Hi, I have a user who failed to activate his product because: IsActivated() - TA_E_IN_VM - The function failed because this instance of your program is running inside a virtual machine or hypervisor. What do I miss here? Wasn't this fixed in the latest turboactivate version?
You cannot activate <program-name> inside a virtual machine or a hypervisor. Please use a real computer. Finish." If I were to Allow Virtual Machine Activations, would this solve this user's issue?
Are you running Hypervisor? Do you have it enabled? Even if you're the "host" OS and you have hypervisor enabled, then you're running in a VM.