NTVDMx64 v. HAXM

[theliz12x]

Hi @leecher1337
i am trying to install this version under the latest version of Win11. the "standard" installation works properly but i am not sure,
is it a problem of the Intelhaxmntvdm driver that is 32bit?
i've crossed over all the needs about the driver sign certification and the system recognises the driver until if i try to start the service i get the error message
is there any workaround ? i were reading about to disable all the "hyperv" device guards and memory integrity checks before tring to install Haxm but nothing to do ,
if i try intelhaxm or intelhaxm i see that the service is stopped and if i try to start it i receive the error:
startsservice operation failed: 31

i'am using Haxm under win10 and the difference of speed/performances is really big

[leecher1337]

I checked if there are issues with latest Windows 11 24H2 and IntelHaxm driver, but it works flawlessly here.
The driver is always 64bit, not 32bit.

So I did the eaxct steps outlines in the docs.

As Admin:

C:\Windows\System32>bcdedit /set hypervisorlaunchtype off
Der Vorgang wurde erfolgreich beendet.

--> works

C:\Windows\System32>bcdedit /set testsigning on
Fehler beim Festlegen der Elementdaten.
Der Wert wird durch die Richtlinie für sicheres Starten geschützt und kann nicht geändert oder gelöscht werden.

--> Failed, because I was using SecureBoot.
Disabled secureboot in BIOS, booted again, entered command again -> Success

C:\ntvdmx64\GER>certutil -addstore "TrustedPublisher" haxm\IntelHaxm.cer
TrustedPublisher "Vertrauenswürdige Herausgeber"
Signatur stimmt mit dem öffentlichen Schlüssel überein.
Das Zertifikat "WDKTestCert ert,131034892687025778" wurde zum Speicher hinzugefügt.
CertUtil: -addstore-Befehl wurde erfolgreich ausgeführt.

--> success

Reboot. Windows shows on bottom right, that it is running in Test signing mode:

Started DOS application and it works.

If driver fails to load, this for example happens if VT-x is not enabled in BIOS and therefore the driver cannot run.
But I guess you verified that it is enabled?

[theliz12x]

Hi @leecher1337

i've checked it , virtualizzation is enabled the option in the bios of a Levono m70s does not specify exactly VT-x but just "virtualizzazioni capability" and is ON like VT-D but that has nothing to do
the driver is installed but cannot start, when trying

c:\Windows\System32>sc start intelhaxmntvdm
SC] StartService FAILED OPERATIONS 31:

A device connected to the system is not working

if i check in the eventmgr in system:

Log Name: System
Source: IntelHaxmNtvdm
Date: 09/29/2025 3:52:36 PM
Event ID: 6
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: pc-sales-xxx.local
Description:
The description for Event ID 6 from source IntelHaxmNtvdm could not be found. The component that generated the event is not installed on the local computer, or the installation is corrupt. You can install or repair the component on the local computer.

If the event originated on another computer, the viewing information was saved with the event.

The following information was saved with the event:

The message resource exists, but the message was not found in the message table.

Event XML:



6
0
2
0
0
0x800000000000000

20966


System
pc-sales-xxx.local





000000000100000000000000060001C00000000000000000000000000000000000000000000000

do you think i can check for something else? i were looking all around the bios for any other "extra option" about Vt-x but there is only that one

[leecher1337]

Hm, M70s seems to be Intel CPU, so the most obvious error (AMD CPU) isn't the case, I guess.
HAXM needs VT-x with EPT (Extended Page Table) support.
Some old Intel CPUs didn't support EPT, so Haxm does not work there. So the exact processor model plays a role.
You can check this thread at the end: intel/haxm#320
You must ensure that the following is disabled:

• Hyper-V
• Containers
• Virtual Machine Platform
• WSL2

https://github.com/intel/haxm/wiki/Installation-Instructions-on-Windows#troubleshooting

If nothing helps, you can try to get official IntelHAXM running via installer (maybe it gives you hints about what doesn't work) and as soon as you got it working, remove it (as it interferes with NTVDMx64) and then use NTVDMx64's version again.

[theliz12x]

Hi @leecher1337

i've tried anything, last , installing the official IntelHaxm as you suggested then i've got:
The HAXM driver can be installed on this computer. However it is required to further configure the system to make it usable.
Then HAXM will be automatically loaded for use.

and at the end:
Attenction only when the following system configurations are completed can HAXM run properly.

this is strange, i've followed all the suggestions in the thread to disable
Hyper-V
Containers
Virtual Machine Platform
WSL2
but i am still receving this alert that should be the couse of the service that cannot start.
in my other tests with Win11 not always Hyper-V is disactivated "completely" but Intelhaxmntvdm works
that's gets me crazy!!

[leecher1337]

What does

C:\Program Files\Intel\HAXM\checktool.exe --verbose

output?

[theliz12x]

@leecher1337 --verbose parameter is not accepted
anyway=>

C:\Program Files\Intel\HAXM>checktool.exe
CPU vendor * GenuineIntel
Intel64 supported * Yes
VMX supported - No
VMX enabled - No
EPT supported - No
NX supported * Yes
NX enabled * Yes
Hyper-V disabled - No
OS version * Windows 10.0.26100
OS architecture * x86_64
Guest unoccupied * Yes. 0 guest(s)

p.s. if i check msinfo32 i see that VBS is still active (regarding other posts about the all kind of "protection" that we have now in latest win11 that do not "stop totally" hyperV

[leecher1337]

EPT supported - No

Bad, no NTVDMx64 support without EPT technically possible.
In this ticket they also suspect that this damn Hyper-V is somehow still active and blocking the calls. Hyper-V, Virtual Machine Platform, and Windows Sandbox need to be turned off in the Windows Features list.

Maybe you can get help from chatgpt for troubleshooting?

[theliz12x]

all is turned of sandbox, platoforms etc, i've tried both chatgpt and grok and tried almost anything but hyperv ... nothing to do if i check with msinfo i receive that VBS is active and then hyperv is not "totally off"
but EPT is enabled disabling hyperv?
i can try to see if i query AI with EPT
one more question, but the signingtestmode must be always signed on? otherwise the driver with fail to load?
the actual certificate will expire in march 2026

what is strange is why only in one network i am having this trouble, maybe is there some addictional "protection" coming from the DOMAIN policies

[leecher1337]

Hm, they also mention "Device Guard" and "Credential Guard":
https://learn.microsoft.com/en-us/troubleshoot/windows-client/application-management/virtualization-apps-not-work-with-hyper-v

EPT are Extended Pagetables, a feature that the CPU must supprot in order to work properly. In the other thread I read that EPT feature not working is one symtom when Hyper-V is still running which is what you also found out.

The test signing mode must be active to load the NTVDMx64 HAXM-driver, because the driver is not signed with an official Microsoft certificate. I guess certificate expiration may not be an issue if the driver date is prior to certificate expiration date, because otherwise many drivers would suddenly cease to work, but Microsoft constantly changes it driver policies, so who knows what they might come up with tomorrow...

Hm, if this is a machine in a domain, maybe it works when signing on with a local user so that no Domain policies apply? Just guessing...

[theliz12x]

@leecher1337
Hi , i did'nt disappeared, just trying many ways to find a workaround. i had this issue with 2 Win11 installed , various update version.
one of them i suppose it is caused by the BIOS (Lenovo) that does not let stop the Device guard but i am still "workin on in"
i need to take time to try to update the bios to see if is there any bug.
in another Asrock workstation now the official version of HAXM works finally, i suppose that Domain+antivirus were causing the issue blocking also some registry key. I had to reinstall the OS so now i can disable Hyperv and activate the testsigning mode
i still have a strange issue that is not letting NTVDMX+HAXM works
when i try to launch a 16bit program, also a EDIT.com i receive this error, is it an error coming from the personalized version of haxm?
Hypervisor is panicked!! Reason: VMX_EXIT_TRIPLE_FAULT CS:IP
D028:0C64 SP:00FE BP:0000091E CR0:10011 Choose close to terminate the application
i cannot find any information about it to valuate where and if is there an issue of any type

p.s. checktool of HAXM report all YES

[leecher1337]

Hi,

Glad that you found at least the potential reasons for the problems, at least on one machine.

Triple fault is a VMX exit reason documented in the Intel Manuals:

Exit Reason	Description
2	Triple fault. The logical processor encountered an exception while attempting to call the double-fault handler and that exception did not itself cause a VM exit due to the exception bitmap.

As can be seen here

So you can think of it as a segmentation fault in the code where no error handler was able to trap the exception leading to an ultimate crash of the VM.
Potential reasons could be i.e. invalid memory mappings / memory contents.
So if I get that correctly, you cannot even start up command.com

How it's really strange that the error occurs on a specific machine, even though the code that gets excuted should be the same on every machine tested. There must be some error condition that the code runs into, but it's hard to tell what is causing this from the distance.
One quick thing to check is if the error occurs with both CHK and FRE build of ntvdmx64, so to check if it also fails on the debug version (I guess so, but you never know).
When using checked build, you also have the opportunity to attach yoda to the process and trace through the code in order to see the execution flow until the crash occurs. Enabling Yoda is explained in the readme. It is also advisable to install the debug symbols to have better traces. (See i.e. #182 (comment))
Simple tracing with yoda is explained here: #295 (comment)

You may get a few gigabytes of trace in the trace.txt, but it it is within an executable known by the debug symbols (so DOS internals that ship with NTVDMx64), there may be a hint where it crashes or where it derails.
You may also want to watch debugview output in the checked build for anomalies, but in the "normal" checked build, there is not so much debug output as it would slow down the execution time significantly.
My guess is that the DOS code derails at some point, i.e. due to invalid memory contents and then ends up nowhere and finally completely crashes.
I was under the assumption that the same code should work on every machine, but it seems that I was wrong. Maybe something interferes with the NTVDM, but as you said you reinstalled the system, so it should be clean. Very weird case...