Windows 11 Hyper-V error Turbo ActiveAnswered

Dear All,

We use Turbo Activate with “Virtual Machine” option to “not allowed”.
Now a client has a Microsoft surface 3 running full windows 11.

The license fails to register, Error 17 (not allowed on VM).

Windows options we have disabled all the hyper-V options.
But running the system information app (msinfo32), last line of summary tab states “A hyper visor has been detected”. 

Now I read that Microsoft Defender also employs certain vm strategies nowadays.
I tried already to disable Windows Security Core Isolation|Memory Integration but this does not work either.

Is there a solution to this? 

Thanks!
 

Answer

Covered extensively in the FAQ.

We ran into this same problem on Microsoft Surface running Windows 11. They have Virtualization based security turned on and there is no way to turn it off. The above mentioned FAQ is inadequate. Also if you turn off “virtualization based security” through some registry hack, you have to turn off important security feature in windows 11 called “Core Isolation→Memory integrity”. Our customers would not accept that.

Here are the details on Windows 11. How do you ask your customers to turn off security now?

Virtualization-based security	Running	
Virtualization-based security Required Security Properties	Base Virtualization Support	
Virtualization-based security Available Security Properties	Base Virtualization Support, Secure Boot, DMA Protection, UEFI Code Readonly, SMM Security Mitigations 1.0, Mode Based Execution Control, APIC Virtualization	
Virtualization-based security Services Configured	Hypervisor enforced Code Integrity, Secure Launch	
Virtualization-based security Services Running	Hypervisor enforced Code Integrity	
Windows Defender Application Control policy	Enforced	
Windows Defender Application Control user mode policy	Off	
Device Encryption Support	Elevation Required to View	
A hypervisor has been detected. Features required for Hyper-V will not be displayed.
Answer

Answered above:

Covered extensively in the FAQ.

Briefly (see the FAQ for the whole explanation), you have options:

  1. Disable VM. And/or…
  2. Use TurboFloat.

Both 1. & 2. are not possible for a lot of our customers. Their IT doesn't have physical machines any more. So our products can't get installed. 

Answer

Your app using TurboFloat can be used on a VMs. That’s why it was designed. See our docs. It’s covered across many separate articles.

They can run TurboFloat Server in a physical machine, you can run it on your infrastructure, or, coming soon, it can be run on our infrastructure.

, edited

Following up on this one, we're seeing a LOT more people having issues starting trials in the last few months. It's often hard to get useful feedback as to why the trial fails to start, but could it be related to default security/hypervisor settings in Windows 11 as mentioned above?

*If* they contact us, we can set up a time limited key using functionality we coded in from the beginning (obviously using TurboFloat isn't a sensible option for trials), but the standard trial method is much nicer - when it works!

(I'll also add that “just use TurboFloat, and never enable VMs” isn't as good a solution as it used to be in general cases, plenty of our customers don't have a single physical machine available!)

Reply
Discard post