Can not load driver

[oeroi]

Describe the bug
When using HyperDbg in VMware, there is an error message indicating that the driver failed to load with error 0x7f. DES has already been disabled using WinDbg, and both VBS and Hyper-V have been turned off.

To Reproduce

HyperDbg> .debug prepare serial 115200 com1
err, StartService failure (7f)
unable to install VMM driver
failed to install or load the driver

HyperDbg>

Expected behavior
Load Driver success

Screenshots
no

Desktop (please complete the following information):

• VM OS: [e.g. Win 10 10.0.18363]
• Processor [e.g. Intel i5 12600k]

[SinaKarvandi]

Hi,
Thanks for creating this issue.

Well, based on the error,

ERROR_PROC_NOT_FOUND
    127 (0x7F)
    The specified procedure could not be found.

It seems the error is related to the target Windows. Is it a 32-bit Windows 10? or 64-bit?
Are you sure that HyperDbg is correctly compiled and are you using the latest version (v0.9)?

[oeroi]

Thank you for your response.
The system is Windows 10 version 10.0.18363 64-bit. Whether using a self-compiled version of HyperDbg or the release version from GitHub v0.9, the result is the same.

[SinaKarvandi]

My first guess is that since HyperDbg uses the latest Windows 11 SDK, Windows 10 19h2 (build 10.0.18363) is not compatible, though not sure. Can you lower the SDK version of the Visual Studio before building HyperDbg?

Another suggestion, maybe using the 'sc' command in Windows or OSR Driver loader to load the 'hprdbgkd.sys' can give us more information about why Windows won't allow HyperDbg to load normally.

[oeroi]

It might be related to my virtual machine system. I have made anti-anti-VM check modifications to the system, such as altering the return values of CPUID, which might be causing the driver to fail to load.

[oeroi]

I installed a new vm system, but the result is still the same.

[oeroi]

I'll try installing Windows 11 later and see if it works.

[SinaKarvandi]

It might be related to my virtual machine system. I have made anti-anti-VM check modifications to the system, such as altering the return values of CPUID, which might be causing the driver to fail to load.

This could be the reason why it fails since HyperDbg checks for VMX features on CPUID.