-
Notifications
You must be signed in to change notification settings - Fork 867
Not Digitally Signed driver #56
Comments
Could you provide us the download link of HAXM v7.2.0? And describe the detailed information of the host machine, such as OS version, OS bits, Windows security software version, etc. Moreover, you may attach your IntelHaxm.sys and perhaps the installer package here if convenient. Thanks. |
Sure no problem, Download Link: https://github.com/intel/haxm/releases/download/v7.2.0/haxm-windows_v7_2_0.zip Machine Details: Windows 7 Ultimate SP1 x64 Not sure what you mean with Windows Security software verison HAXM 7.2 is not working because it doesn't pass the Driver Signature Enforcement |
My workaround to this issue was simple to go back to HAXM v7.1 because it's digitally signed, in case anyone else have the issue, while you figure it out. Regards, |
OK I had to reproduce the issue again, here is the information requested. My IntelHaxm.sys and the installer package downloaded, IntelHaxm.zip Hope this helps, Regards, |
Could you please attach the error screenshot when blocking installation? And since HAXM v7.2.0 cannot finish to install, how did you extract IntelHaxm.sys driver? Thanks. |
Sorry my friend, I went back to HAXM v7.1 because i'm working right now on Android Studio, On HAXM v7.2 if you run the silent_install.bat, it will show no error, the files get copied to the system that's how I managed to get the IntelHaxm.sys, but Windows shows a message saying that an installation tried to install a driver that was not digitally signed and it will not run. If you run the HAXM Installer (intelhaxm-android), it will show an error then the Finish button, there I'm not sure if the files get copied to the system. This error will happen to any computer having Windows 7,8 or 10, if you don't have a Windows OS close to you right now I could try again to show you those messsages. BTW if you noted my Windows OS is in Spanish so I'm not sure if you will understand the error anyway, just let me know if you still need them. |
Could you help to provide the Windows build version of Windows 7? Just run below command, Could you also help to check the signature certification chains for IntelHaxm.sys of HAXM v7.2.0? The following screenshots are certification path of HAXM v7.1.0 and v7.2.0 from my Windows 7 computer. Figure 1. HAXM v7.1.0 Figure 2. HAXM v7.2.0By the way, after our checking, all of certification paths from both drivers are shown as OK from our computers, including Windows 7, 8 and 10. |
Thanks for your detailed information. We compared the certificate chains and found there were some differences between us. There are 4 levels in ours and 3 levels in yours. We will investigate this issue in the next week. You can change to HAXM v7.1.0 to continue using. Sorry for bring you trouble. Thanks a lot. |
As far as I was reading about certificates this issue could be reported in computers with Windows OS 7,8 and 10 with Architecture of 64 bits, I just noticed the issue after updating HAXM from Android Studio, I would like to think it's just me who has the issue but I found another user that updated Haxm as well and had the same problem. https://stackoverflow.com/questions/50615096/intel-haxm-version-7-2-not-digitally-signed I appreciate your time and efforts, now I will go back to HAXM v7.1 Best Regards, |
We now have another report of the same issue from @minimop (#57). @minimop Are you also on Windows 7? Please provide the following information about your Windows system:
If you could also check the certification path for Thanks. |
TLDR: I believe this issue only affects 64-bit Windows 7 systems that lack this security update, which enables support for drivers signed with a SHA-256 (SHA-2) certificate. For the HAXM 7.2.0 release, we changed the certificate that we use to sign the Windows 7/8/8.1 driver ( However, apparently the new driver signature is not recognized by some Windows systems. According to this article, Windows 7 actually requires a patch to enable SHA-256 support, whereas Windows 8 and later supports it by default. @olizama Could you install that patch and see if it fixes the issue for you? |
You must be right @raphaelning, it's an old bad habit that I have to disabled Windows Updates, got tired of getting my computer broken because of those. Let me install the patch, then install HAXM v7.2 |
OK my friends, sorry for the issue report, it was as you said a windows update missing, patched the computer and installed HAXM v7.2 without issues, working like a charm. Big thanks for your hard work. |
Cool! So we'll continue to sign the Windows 7 driver with the SHA-256 certificate for future HAXM releases. Closing this issue now. |
I'm having exactly same issue and can't install KB3033929. Having this - "The update is not applicable to your computer". I don't know how many people would get in same situation, but it's sad. Digging in why it can't be installed isn't the best pastime. |
@F0RIS I had the same issue. Try uninstalling 7.2 and simply unzip and install 7.1. |
@Drmuaz I did that. But with that approach I will not able to use newer versions :/ |
@raphaelning |
Version 6.1.7600Windows 7 professional 64 bit
Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: Yu Ning <notifications@github.com> Date: 6/25/18 7:32 AM (GMT+05:00) To: intel/haxm <haxm@noreply.github.com> Cc: drmuaz <muaz.niazi@gmail.com>, Mention <mention@noreply.github.com> Subject: Re: [intel/haxm] Not Digitally Signed driver (#56)
@F0RIS @Drmuaz Sorry for the delay, I just reopened this issue. Are you also on Windows 7? Could you provide details about your Windows system:
Version (check output of ver from a command prompt window)
Edition (Home/Professional/Ultimate/Enterprise)
Architecture (32-bit or 64-bit)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@Drmuaz Apparently you haven't installed Service Pack 1 yet, which is required by the patch:
@F0RIS I guess you probably have a dual OS setup (Windows + Linux) where the default boot loader is not the Windows boot loader. According to KB3033929:
If that's indeed the case, there will be no easy way for you to install the patch. We'll need to reconsider our driver signing policy for Windows 7--for example, should we just go back to SHA-1 for the Windows 7 driver, but keep using SHA-256 for the Windows 8/8.1 driver? Or is there a better option? |
@raphaelning And yes. I have dual OS setup. And of course my default boot loader is grub, because Windows' loader can't load linux. So yeah, may be you should switch back to SHA-1 for Windows 7. |
People will able to install the patch if they have windows 8, 8.1, 10 and Linux? With grub? Or those OS already have support for sha-256? Edit Looks like that windows patch has a lot of issues, and anyone having dual boot with grub loading windows will be unable to install it. A way around it could be fix the windows MBR to make windows load by default then install the patch and once done, reinstall grub. I could take a hour or so. But since Microsoft released that patch they didn't fixed the dual booting issue looks like they don't care. |
Right, SHA-256 is natively supported by Windows 8 and later.
Thanks, we're seriously considering this option, but we need to find out if that's allowed by Intel policy first. |
I followed the solution from Foris. Go to google search KB3033929, then download it, install it. Then reinstall HAXVM v7.2.0. Then run android studio, everything running flawlessly. Thannnnnnnnnnnnnnnnnnk you very much! I use Windows 7 pro sp1 64bit |
I was have same issue but now i have installed v3 and now its working ok thanks |
Thanks for @murtadaalwaely confirmation. |
For what it's worth, you can use signtool to sign the driver with a SHA1 signature then use the There's a nice guide on the steps required on DigiCert's support portal (though the CA-specific steps will obviously vary): https://www.digicert.com/code-signing/code-signing-dual-signing-sha256-sha1.htm |
Thanks, that's a brilliant idea! We'll give it a try. |
Same issue here on release v7.5.1, I didn't stop to read all the topics because I'm in hurry right now, later I come with prints if reading the topics don't solve anything... By now I will try to go with v7.1.0 as stated by someone before... |
Thanks for your report. Could you help to confirm that your OS version is Windows 7 SP1? Currently, HAXM will not support the system that does not support SHA-256 signature. You are suggested to use HAXM v7.3.2 as this version is the last version supports SHA-1 signature. |
Yes, I do have SP1. I have already solved my problem by running version 7.1.0 as previously suggested on this thread, I've just commented out of care for newbies like my trying to just get the job done. I will later try running 7.3.2 on a VM, maybe installing KB4472027 could fix this... Don't know, I may try it out and drop a few prints here with the result. Anyway! Thank you very much for replying my comment, it proves people still care about newbies like me... |
@wcwang Thank you man for suggestion. I have installed this "haxm-windows_v7_1_0" working like charm. I have checked lots of SO thread but didn't get solution and west many hours to resolved this issue. Thank you very very much for suggestion. |
Hi Please help me solve this issue. Thank you |
Hi, did u intalling KB... and had progress??? |
@aleenajoseph993, thanks for your report. Could you try HAXM v7.3.2 instead as this version is the last version supports SHA-1 signature? Have you installed KB3033929 for Windows update? |
@aleenajoseph993, the patch KB3033929 is exactly targeted to Windows 7, rather than Windows 10. HAXM is independent of Android Studio. I have provided the HAXM v7.3.2 installer in the previous reply. You may download it and try to install HAXM manually. Thanks. |
Hi, |
Hi |
I have the same problem. Which versions are known to work with Windows 7? 7.1.0 ok |
Hi! |
My dears,
Looks like you forgot to digitally sign the driver on version 7.2, it can't be installed normally without bypassing windows security.
The text was updated successfully, but these errors were encountered: