Dead Space 3 (PC): false VM detection on Surface — VBS can't be disabled

Hey zrosea​ 

Thanks for the very detailed report and for listing everything you've already tested.

I had a look into this, and there have been similar reports involving other older EA titles, including Dragon Age II, Mass Effect 3, Bejeweled 3 and Plants vs. Zombies. A number of those reports also involve Microsoft Surface devices running Windows 11 and show the same "virtual environment" message even when the usual Hyper-V and Windows virtualisation features have been disabled.

So you're definitely not the first person to run into this particular situation on physical hardware.

From what you've described, this doesn't appear to be a case of the Surface Laptop 4 failing to meet the game's hardware requirements. The issue is more likely related to the environment in which the game is expected to run.

Modern Secured-core Windows devices can use virtualization-based security and the Windows hypervisor as part of the operating system's security architecture. That means a physical PC can still report that a hypervisor is present.

Older games and their legacy protection or activation systems were designed at a time when the presence of a hypervisor was much more commonly associated with actually running Windows inside a virtual machine. Because of that, older software may interpret the modern Windows security environment as a virtual environment even though the machine itself is physical.

In other words, the limitation here is not necessarily the CPU, GPU or other hardware. It can be an incompatibility between the older game's environment checks and the way a modern Secured-core Windows system is structured internally.

That said, I can't confirm exactly which check Dead Space 3 is using or whether HyperVisorPresent, VBS or another virtualization indicator is specifically what triggers the message on your Surface.

Given everything you've already tried, I also don't want to suggest making any further changes to Windows security, boot configuration or firmware just to try to get around the detection.

Unfortunately, Dead Space 3 is no longer actively supported, so we're not able to escalate this for a change to the game's virtual environment detection. I also don't have another supported workaround I can recommend from the forum side.

I realise that's not the answer you were hoping for, but you've already covered the troubleshooting paths that have commonly been suggested for this error, and I don't want to send you through the same steps again or ask you to weaken security features on the device.