Issue With Virtual Machine

[Mahmoudnia]

The issue is related to detecting a virtual machine inside the real OS. I use this option in the protector without using a marker.

Device: Surface Pro 5 (Surface Pro 1796)
OS: Windows 10 Build 19045

System Details:
Virtualization-Based Security (VBS): Not Enabled
Hyper-V VM Monitor Mode Extensions: Yes
Hyper-V requires Second Level Address Translation (SLAT): Yes
Hyper-V Virtualization Enabled in Firmware: Yes
Hyper-V Data Execution Prevention: Yes

Could this issue be related to Hyper-V

[Admin]

I don't understand what problem you mean and what version of VMProtect you used.

[MrLot]

The issue is related to detecting a virtual machine inside the real OS. I use this option in the protector without using a marker.

Device: Surface Pro 5 (Surface Pro 1796)
OS: Windows 10 Build 19045

System Details:
Virtualization-Based Security (VBS): Not Enabled
Hyper-V VM Monitor Mode Extensions: Yes
Hyper-V requires Second Level Address Translation (SLAT): Yes
Hyper-V Virtualization Enabled in Firmware: Yes
Hyper-V Data Execution Prevention: Yes

Could this issue be related to Hyper-V

This is due to Microsoft making the genius decision to run all hardware behind a VM (good for security, bad for things like this). It’s in the UEFI bios itself, and there is no way to turn it off. So yes, your machine is being flagged because the OS is actually running behind virtual hardware even though you’re not running a VM. This is something you should create a ticket with Microsoft to fix. This is not a VMP issue. I have seen this occur as well and this was the problem.