We'll be at #FOSDEM 2026 in Brussels (January 31-February 1) with talks in the Security, Virtualization, and Cloud Infrastructure rooms about the HyperDbg debugger.

More info:
- https://fosdem.org/2026/schedule/event/mbec_slat_and_hyperdbg_hypervisor-based_kernel-_and_user-mode_debugging/

- https://fosdem.org/2026/schedule/event/invisible_hypervisors_debugging_with_hyperdbg/

#FOSDEM2026

[discord] <same> Hello, I’m having trouble building HyperDbg on a windows 10 22H2 virtual machine. On my host machine (windows 11 Pro 25h2) everything works fine, and I’m using an older version of the WDK and SDK there. First, I installed the latest SDK and WDK on the VM, but the build failed. Then I installed the same SDK/WDK versions that successfully build on my host machine, but the build still fails on the VM. Could someone help me figure out what’s causing this issue? Here are the issues:
https://cdn.discordapp.com/attachments/962350355839066130/1444257966965391442/image.png?ex=694bb18c&is=694a600c&hm=771443de75e664ca7d6c1760590978f105c6cb12eac8491b1df33629a7ad7bc0&
https://cdn.discordapp.com/attachments/962350355839066130/1444257967347339385/image.png?ex=694bb18c&is=694a600c&hm=e54a619c6058b0cd7f012c6f1eb3b439fd63170198beb70ae78c0072787e7bc2&

[discord] <unrustled.jimmies> Also i ran into a heisenbug (happened only once and never again) yesterday where hyperdbg got a EPT violation on `HalpPciMmConfigWriteHandlers`. i will debug and let you know what i find.
https://cdn.discordapp.com/attachments/962350355839066130/1432068071111262270/Screenshot_2025-10-26_110152.png?ex=694b8312&is=694a3192&hm=7d7913b305b9b4a06938c8c2ab0e44b5e998bd5d23e8ab6bdc74847a053b4087&

Hi,
It appears that the new SDK has a compilation issue with Zydis. This can be resolved by opening the Zydis solution file (.sln) and fixing the project configuration.

After hours of fixing the problem, I've found the solution: it builds only from the eng-named folder and only with sdk/wdk version <= 26100.3323, because some of the dependencies (Zydis one of them) don't support kmdf 1.9.

Fix kmdf on zydis solution file.

@HughEverett looks like I can't see messages on Discord sent on December 23rd. Do you see them on discord?

Hi, it's the old messages from Discord, I sent them in November))

Ah, you mean this message?

It is not in discord? 🤔

Bot duplicated messages

It seems the synchronization BOT goes crazy. 🫤

First I sent messages to Discord, then the bot duplicated them month later

Maybe it tries to keep activity levels on this channel :)

yeah, I see. If it happens again, I'll update the bot.

😅😅

"same" is my account in discord)

1

[discord] <unrustled.jimmies> [reply]: on a semi related note.
https://cdn.discordapp.com/attachments/962350355839066130/1453493154861809726/Screenshot_2025-12-24_125904.png?ex=694da67c&is=694c54fc&hm=1f849b4bc8669be987989724d0d1a24ecd0cc5b0aa61b601288f008eb7e51db3&

I keep failing to open VMM with the release version; the driver cannot be loaded. I've confirmed that VBS is disabled on my system. Do yours all load successfully?

The system is in test mode.

How can this problem be solved?

delete old driver ?

The old driver is missing because it wasn't completely uninstalled after a previous failed loading attempt. Restarting the computer doesn't resolve the issue.

I've reinstalled the system, but I still can't load the published VMM. I'm completely out of ideas.

Please help me.

Also you can try to execute this command, maybe it will help:
bcdedit /set testsigning on

I'm having trouble loading VMM correctly. Please see the screenshot above.

In test mode

vmware

👍

HyperDbg is not signed for test mode AFAIK

You need to just disable driver signature enforcement

There are three ways of doing it as described here: https://docs.hyperdbg.org/getting-started/build-and-install#disable-driver-signature-enforcement

Please disable DSE (not Test mode) and let me know if it works or not.

I tried it, and it immediately crashed with a blue screen.

Can you send the bsod error?

Okay, just a moment, I'll load it again.

The .dmp file cannot be sent.

Are you sending a imindump?

Minidump*

yes

Groups prohibit sending files

Sorry about that. Can you try some file sharing service? Just make sure it's a minidump in order not to leak any sensitive data.

I'll give it a try.

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 0000000080000003, Exception code that caused the BugCheck
Arg2: fffff803336f1299, Address of the instruction which caused the BugCheck
Arg3: fffff80315789920, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for hyperhv.dll

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4749

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 6431

Key : Analysis.Init.CPU.mSec
Value: 2624

Key : Analysis.Init.Elapsed.mSec
Value: 57722

Key : Analysis.Memory.CommitPeak.Mb
Value: 88

FILE_IN_CAB: 122625-8171-01.dmp

VIRTUAL_MACHINE: VMware

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 3b

BUGCHECK_P1: 80000003

BUGCHECK_P2: fffff803336f1299

BUGCHECK_P3: fffff80315789920

BUGCHECK_P4: 0

CONTEXT: fffff80315789920 -- (.cxr 0xfffff80315789920)
rax=0000000000000000 rbx=ffffe9875dba30f0 rcx=bdb96fe8cb270000
rdx=0000000000000000 rsi=ffffe9875dba3270 rdi=ffffe9875dba30e0
rip=fffff803336f1299 rsp=ffffe9875dba2eb0 rbp=0000000000000000
r8=000000000ad013c0 r9=ffff9e0c73701d20 r10=ffff9e0c73800160
r11=ffffe9875dba2dc0 r12=ffffe9875dba3138 r13=0000000000000002
r14=fffff80316b1bcd0 r15=fffff8031483c180
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000282
hyperhv+0x1299:
fffff803336f1299 cc int 3
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: hyperdbg-cli.e

STACK_TEXT:
ffffe9875dba2eb0 ffffe9875dba30f0 : 0000000000000000 0000000000000007 0000000000000000 0000000000000460 : hyperhv+0x1299
ffffe9875dba2eb8 0000000000000000 : 0000000000000007 0000000000000000 0000000000000460 0000000000000da0 : 0xffffe9875dba30f0

SYMBOL_NAME: hyperhv+1299

MODULE_NAME: hyperhv

IMAGE_NAME: hyperhv.dll

STACK_COMMAND: .cxr 0xfffff80315789920 ; kb

BUCKET_ID_FUNC_OFFSET: 1299

FAILURE_BUCKET_ID: 0x3B_80000003_hyperhv!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {dd348f0b-8ee4-3073-19e3-d4a11add99fc}

Followup: MachineOwner
---------

This is the content of the .dmp file.

And what is your processor (which generation of Intel processor do you use?), as well as Windows version?

Does it not support win10?

[discord] <unrustled.jimmies> [reply]: if you have windbg kernel debugging set up, try setting a breakpoint on https://github.com/HyperDbg/HyperDbg/blob/5462d69dd189cdfca3a889daca3fb6eb8abf080d/hyperdbg/hyperhv/code/assembly/AsmVmxContextState.asm#L39 and VmxVirtualizeCurrentSystem to see what branch in`call VmxVirtualizeCurrentSystem` didnt succeed. hyperdbg is detecting the necessary vmx features to make it this far but one of vmclear/vmptrld/vmlaunch is failing.

Well, HyperDbg supports win 10 but for a long time, I didn't test it on Windows 10 since Win 10 is already depracated.

Yes, you're right. It is the way to find the error on Win 10.

Right now, I don't have a ready to test Win 10 VM, but you can easily step through instruction from where @unrustled.jimmies mentioned to see what's going wrong.

[discord] <unrustled.jimmies> i have a feeling the issue might be more his e3-1230 v2 than win 10. that looks like a ~2012 cpu.

Not just that, xeons have a different set of features and different physical memory layout (not sure if it matteres for hyperdbg)

if it's the case, probably the setup so old and different that we couldn't support. 🤔

Understood, I will try to change the win11 system first, if it doesn't work, try changing the cpu again, thank you for your help

Happy New Year! 🎉
Wishing you lots of joy, good health, and exciting new adventures ahead. ✨
Hopefully, we’ll have exciting releases in HyperDbg this year. 😎

HAPPY NEW YEAR! :D with HyperDBG! :)

Happy New Year! 🎉