> But it’s causing trouble because if NX cannot be enabled on an Intel CPU for whatever reason (such as running in a VM on a host with disabled NX, thanks Intel

> But it’s causing trouble because if NX cannot be enabled on an Intel CPU for whatever reason (such as running in a VM on a host with disabled NX, thanks Intel!), Windows 10 doesn’t believe the CPUID information and tries to enable NX anyway, which blows up. This seems like a "Doctor, it hurts when I do this." kind of thing. Just don't do that. Is there any good reason to disable NX systemwide on a VM host? Seems kinda risky.