Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

16bit program cannot find haxm #236

Open
SkillGodAk opened this issue Aug 3, 2023 · 12 comments
Open

16bit program cannot find haxm #236

SkillGodAk opened this issue Aug 3, 2023 · 12 comments

Comments

@SkillGodAk
Copy link

I installed HAXM versions
But executing the program I want to run shows that haxm is not installed
I'm sure hyper-v is off and vt in bios is on
Use cmd to check and make sure it is open. Where is the problem?

01
@leecher1337
Copy link
Owner

Wrong service. You mustn't run IntelHaxm service! It has to be IntelHaxmNtvdm shipped with HAXM build. To be safe, ensure that original IntelHaxm driver doesn't run.

ntvdmx64/ntvdmpatch/doc/haxm.txt

Line 93 in 0f7f33e

If there is a service named IntelHaxmNtvdm on the system, it tries to start it,

@SkillGodAk
Copy link
Author

SkillGodAk commented Aug 4, 2023 •
edited

I built IntelHaxm and IntelHaxmNtvdm using HAXM in the forum, no error pops up when I execute the program, but nothing responds when I execute the program. Please help tell what is the problem? The software I use is cracking software, and he has cracked files that need to be placed under c:\system to run. I don't know if it will affect
By the way, I have also installed the ccpu version of ntvdmx64 before, and the running program is the same as the current HAXM version without any response
This software can run successfully on OTVDM, but it shows an error on NTVDMX64
attached log
USER.LOG

Attach the program here, can you help me find out where the problem is?
https://mega.nz/file/ByNWXSwA#gT_3sDhbAeCYmaYDCkZ-ZYvqSsdSLDJ0qFxwG3g2RhY

@theliz12x
Copy link

theliz12x commented Jan 17, 2024 •
edited

Hi i am tring to install the HAXM version of NTVLDMX64 becouse the CCPU seems quiet slow with softwares but i am a bit in trouble. i've installre the Version 7.8.0 from https://github.com/intel/haxm
at first attempt to launch an application (simpe EDIT) i've received an error
"cannot setup exception bitmap for "BOPping" you are running our custom haxm version... close"
then i've checkd all the requirement into the readme.txt (checktool.exe show all requirements present)
i suppose i am using the official HAXM downloaded from
The latest HAXM release for Windows and macOS hosts are available
https://github.com/intel/haxm/releases/latest

is that my fault?
(i've deleted also the present service called IntelHAXMNtvdm that now is not present anymore)
in the project https://github.com/leecher1337/haxm there is not haxm release versions that i can download?
i've deleted also the service called IntelHAXM and now i receive the message that no Intelhaxm is installed

i did it in the way i've copied the "patched" IntelHaxm.sys in the intel haxm original installed folder. but i still receive message that HAXM is not installed. if i query the service instalhaxmntvld it is stoped, if i try to start it the system tells me that a certificate is explicit revoked
is there a way to start the service? i've made the
bcdedit /set hypervisorlaunchtype off
bcdedit /set testsigning on
VT-x in BIOS, is present

last note @leecher1337 Secure bios is not active on the win10 i'm using

leecher1337 added a commit that referenced this issue Feb 29, 2024
@leecher1337
Due to the fact that the NVIDIA code signing certificate is revoked n…
eb24d23 
…ow on most Windows installation and therefore isn't useful anymore,

revert "Facilitating HAXM build installation by using old code signing certificate to make it possible to install it without the requirement to enable test signing mode"
You need Test signing mode again now.

This reverts commit 32688f9.

#236
@leecher1337
Copy link
Owner

Hi,
Unfortunately, leaked NVIDIA code signing certficate was blocked on most Windows installations by now and therefore isn't useful any longer, so running Windows in test signing mode using the old driver seems to be the only way, as can be seen bey the error message you got.
It's mandatory to use my custom IntelHAXM-version, as Intel refused to integrate my improvements in their main driver, unfortunately (I tried many times to persuade them, but to no avail, even though, these are only enhancements fully compatible with the main driver).
Thus, try test signing mode with older IntelHaxm driver with test signed certificate now that I reverted back now in last commit.

@theliz12x
Copy link

Hi, Unfortunately, leaked NVIDIA code signing certficate was blocked on most Windows installations by now and therefore isn't useful any longer, so running Windows in test signing mode using the old driver seems to be the only way, as can be seen bey the error message you got. It's mandatory to use my custom IntelHAXM-version, as Intel refused to integrate my improvements in their main driver, unfortunately (I tried many times to persuade them, but to no avail, even though, these are only enhancements fully compatible with the main driver). Thus, try test signing mode with older IntelHaxm driver with test signed certificate now that I reverted back now in last commit.

i've tried your custom version (i did it in the way i've copied the "patched" IntelHaxm.sys ) but with the same result, "not installed" and i see that the service is not started i suppose becouse of the "signed certificate issue". if i use your patched version shuold i cross the problem or i missunderstood?

@theliz12x
Copy link

theliz12x commented Feb 29, 2024 via email

@leecher1337
Copy link
Owner

So, did you take this version (that I downgraded 2 hours ago, you need the new .cer and the new .sys and add the .cer to the store):
https://github.com/leecher1337/ntvdmx64/tree/master/ntvdmpatch/haxm

And did you enable test signing mode?

bcdedit /set testsigning on
certutil -addstore "TrustedPublisher" haxm\IntelHaxm.cer

In testsigning mode, it shouldn't be too picky about the certificate as long as it is installed in the store of trusted publishers.

@theliz12x
Copy link

not yet, it was a version of 1 year ago , i will let you now that you

@theliz12x
Copy link

Hi @leecher1337 , i did it , now with this last version the service is started and then i do not receive anymore the message about "haxm not installed" but i still have another issue an error message if i try to use edit.com
"16 bit application not supported" , etc etc

@theliz12x
Copy link

it works, following other issues i were checking file folders, i had to take ownership of syswow64 so that the installation process could replace corretly all the files so that maybe this can help others.
@leecher1337 it will works until 23.03.2026 (the date of certificare expiration?) there is no way to let the service starts without need of the signed certs?
thank you now the speed of TP compiler is 2 seconds for 1 million lines, the same of an old I7 of 10 years ago :)

@leecher1337
Copy link
Owner

@theliz12x Glad to hear that it worked for you now! 👍
The issues with Syswow64 ownership is strange, never encountered this on a system yet, I thought admin user that is needed to install it will have permissions to write ot syswow64 anyway.
Normally the installer does takeown /f only for wow32.dll and user.exe, as these are files that are already present from Windows and need to be replaced, but the other stuff normally isn't there on a new system so it should be able to write it.
Anyway, good that you documented it here!
If anyone else is also experiencing this problem, informations on how to reproduce this are welcome.

Regarding the signature expiration date of the certificiate: This is not a problem. It is just necessary that the certificate is valid at the time of signing the driver.

Currently I don't have a way to allow the driver to be loaded outside of test signing mode, due to now having contact to a company that posesses a driver signing certificate and is willing to pass the driver through Microsoft's signing process.
If anyone is able to sign the driver, I would be delighted!

There are hacks like "Bring your own vulnerable driver":
https://github.com/hfiref0x/KDU
This requires a signed vulnerable driver to chain-load your driver, but it's a hack and these drivers frequently get blacklisted too, so it's also only a temporary fix. So I guess it's not much better than the leaked certificate I used before.

Your use-case is the one that haxm support was developed for - speeding up textmode applications. Good to hear that it gets used

@theliz12x
Copy link

Yes i will use it. Great job!!! i still use some old compilers on 32b machines. It works very well, i will let you know if any issue can occur. Rightnow i've found only that problem with LPT connected with net use as i told you in another post. DOSPRN can be a workaround i will try it. Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@leecher1337 @SkillGodAk @theliz12x