We have the latest versions of TurboActivate built into our app. We have had many customers saying that they cannot trial our software on physical machines running Windows 11. To be sure, we have the flag that prevents trials in VMs from running.
To verify the experience our customers have, I procured a fresh new Dell XPS laptop running Windows 11. I installed our application, and sure enough I could not trial it because the app has that flag to NOT allow trials on VMs.
So, I visited the Q&A page that is posted on the help area of this site. I have done all of the following:
1. Disabled “Windows Hypervisor Platform” from the "Turn Windows features on or off" dialog.
2. Disabled “Virtual Machine Platform” from the “Turn Windows features on or off” dialog.
3. Successfully ran the following command from an Administrator command prompt: bcdedit /set hypervisorlaunchtype off
4. Disabled all virtualization options from the Intel BIOS of the laptop.
Still, when I run the trial, TurboActivate assumes the physical machine is a virtual machine.
To be sure, there is no “Hyper-V” option nor “Windows Defender Application Guard” option in the “Turn Windows features on or off” as it appears in the screenshot in the help area.
What we'll do is likely just allow verified trials to work in VMs, but it's not ideal for us.
I'm not looking for answers, I'm just leaving a note: the singular flaw I see with LimeLM is this VM detection feature. It just does not work properly on Windows given what Microsoft has done with security the last few years. Even if your suggestions did work, it's ALOT to ask an end-user to disable all of these features. It makes them feel like their machine is more vulnerable. I think you should strongly consider just letting folks know about the MS limitations for VM detection instead of advising developers that it's possible. I guess what I'm trying to say is that it should be advised that on Windows, developers need to ensure that trials should work on VMs.