NTVDMx64 CPPU, HAXM and MinNT method crash the entire PC.

[LudoLud]

I don't know how, but whenever I try to install NTVDMx64 on my main computer, it froze. There's no error with the installer, but after the restart, the lock screen is black, without any cursor/keyboard/startup sound. On a VM, the same instance, it work pretty great. Is this an issue that other people have too?

[leecher1337]

My guess is that you have some process on your machine that doesn't like it when the loader gets injected into it and maybe locks up. I'm not aware of the problem you described, but if you find out which process causes it, you can add it to a whitelist where the loader doesn't get injected into:

#196 (comment)

[LudoLud]

So, I try the method, but it doesn't work too. And the worst is even a VM crash now. I try the CCPU, HAXM and the MinNT method, no one work. Also, it's like luck. The french language doens't work at all, but the USA version works sometimes, but never with WOW32 support. Is it because of the outdated symbols from the Microsoft website? Idk, it's just a guess.

My PC spec (maybe it can help)

Main: ASUS ROG Strix Scar 17 2022 (Laptop)
CPU: i9-12900H
RAM: 16 GB DDR5 4800
SSD: 1TB NVMe Micro 3400
GPU: NVIDIA GeForce RTX 3070 Ti Laptop GPU
Screen: Integrated FHD 360hz
Internet: Intel WiFi 6E AX211

Plugged on the computer:

• HyperX Quadcast S
• TopMate C11 Laptop Cooler
• DVD Disk Drive USB
• Floppy Drive USB
• ASUS ZenScreen
• Razer Barracuda X

Softwares:

• Rectify11
• Visual Studio 2022
• Bunch of other, ask me if you want

FUN FACT: After the installation of NTVDMx64. It's stuck on the lock screen. My mic replicate the sound around it so I can hear it in my headset. When it froze on the lock screen, it's slightly more louder.

[leecher1337]

Which Windows version and build number?

[LudoLud]

Windows 11 Version 22H2 22621.1778 (64-Bit) with every updates. French Canadian.

[leecher1337]

I tried it with Windows 11 Version 22H2 22621.1708 (64-Bit) German and didn't experience described issue, so the lockup it must be something related to your setup.
As you said, you were also able to reproduce the lockup in a VM, is it possible to share the VM image with me so that it can be investigated?

Regarding WOW32 support: It seems that Microsoft removed UserRegisterWowHandlers functions from USER32.DLL, thus ruining WOW32 support. A bug report has been filed by me via Feedback Hub, but usually, they don't care about feedback, so if they don't fix this issue, WOW32 support then is dead as of Windows 11 22H2. I guess you have to switch to WineVDM for that.

[leecher1337]

Feedback hub entry: https://aka.ms/AAl858b
Maybe users can upvote the issue...?