131 results found
Covered here: “Licensing from inside a virtual machine or hypervisor”
TA is giving an error that my work laptop is a Virtual Machine or Hypervisor. I followed all of the steps in your FAQ to make sure all virtualization and hypervisor functions are disabled but still get the error.
Being inside a hypervisor is being inside of a VM (even if you're in the “host” machine – because that “host” machine is *also* in a VM).
Smart5ULT.VirtualMachineException: The function failed because this instance of your program if running inside a virtual machine / hypervisor and you've prevented the function from running inside a VM.
Initialisation failed because this instance of your program is running inside a virtual machine/ hypervisor and you've prevented the function from..”.
For some of them I mentioned to do this that you advice on other posts: “turn off (Hyper-V, Windows Hypervisor Platform, Windows Defender Application Guard, Virtual Machine Platform)”.
VMs can have identical fingerprints: https://wyday.com/limelm/help/vm-hypervisor-licensing/ Long story short: no, there's nothing that can be deleted on the system to "reset" a trial.
Error: “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”The user says that they are not running inside a virtual machine.
When I run TurboActivate on one of my laptops WinXP (32-bit x86), I get "You cannot activate inside a virtual machine or a hypervisor. Please use a real computer". The point is it this a real native XP and not a virtual instance.
See: http://wyday.com/limelm/help/vm-hypervisor-licensing/ and http://wyday.com/limelm/help/using-turbofloat/
I am testing an app that I developed and when I enter a key I get 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 but I am not running in a VM.
The solution to this problem is TurboFloat: https://wyday.com/limelm/help/vm-hypervisor-licensing/ Automating the deactivation of an end-user using the web API means that any user can deactivate from anywhere and unlimited number of times.
Tell them to go into their BIOS and disable any BIOS level Hypervisor. Also, tell them to disable the Windows AV VM (see the FAQ, its been updated to cover those 2 things).
All of the consequences of running TurboActivate on a VM are described here and here: https://wyday.com/limelm/help/vm-hypervisor-licensing/ https://wyday.com/limelm/help/faq/#in-vm Short answer: in VMs use TurboFloat.
We've also covered them in "Licensing from inside a virtual machine or hypervisor". VPSs are a slightly more restricted variant of VMs (that is, VPS are designed to reflect the base hardware -- so moving a VPS to a different machine will mean the VPS instance will have a different hardware fingerpring -- that of the new machine).
We recommend following these instructions (forcing customers to use TurboFloat if they're inside a VM): http://wyday.com/limelm/help/vm-hypervisor-licensing/
My one issue is, when I try to run the .exe that Visual Studio compiles, it looks like this: http://screencast.com/t/KQnF3e9bLW9My code seems to be all fine and good, and the license is enabled and I can activate on hypervisor (my computer is hypervisor) My code is as here: http://paste.teambuildirc.com/view/c3191c20 I host my own pasting site, and that's why it's not a normal paste URL.
Even with Hyper-V, Windows Virtualization Platform, Windows Hypervisor Platform and Windows Subsystem for Linux disabled, TurboActivate still detects virtualization as enabled.
See: http://wyday.com/limelm/help/vm-hypervisor-licensing/
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.