Computer being (falsely) recognised as a VM?

Hello,

I'm trying to activate a license on my development machine, but the process is failing. Looking at the network traffic with Fiddler, I see the following response from LimeLM:

<?xml version="1.0" encoding="utf-8"?><rsp stat="fail"> <err code="145" msg="Activating VMs is not allowed."/></rsp>

This PC is not a VM. I've had it for a while and I am almost completely sure that I have successfully activated products in the past. Can you share some information regarding how LimeLM detects whether a machine is a VM or not? I am worried that my users may encounter a similar situation.

Thanks!

As an update to this, I've just blown away my OS and installed a fresh build of Windows 10 (build 10586). Seeing the same issue. This is a physical machine, not a VM.

Firstly, you don't have to analyze network traffic. TurboActivate returns TA_E_VM. Next, what version of TurboActivate are you using? If it's not the latest, then that's the problem. Lastly, make sure Hyper-V is disabled. Because if it's enabled then you *are* in a VM.

Thanks Sam, this has clarified the situation. Cheers!

Reply
Discard post