Fixed
Status Update
No update yet.
Comments
vi...@google.com
Thank you for your feedback. Team may reach out for more feedback in reproducing or triaging this issue.
lf...@google.com
Hi, thanks for the report. This is weird, we expect GVM to install successfully without that check on Windows 7. Reaching out to the team on this
hs...@google.com
Thanks for reporting! I am working on that. Microsoft's information on Windows 7 driver signature is pretty bad.
According to Microsoft, they should patch Windows 7 so that it has the same driver signature requirement as Windows 10 (old SHA1 is deprecated). But since you have all the updates installed, it is apparently not what they have claimed.
According to Microsoft, they should patch Windows 7 so that it has the same driver signature requirement as Windows 10 (old SHA1 is deprecated). But since you have all the updates installed, it is apparently not what they have claimed.
gv...@gmail.com
As I know the SHA2 was introduced with KB4512506 (august monthly rollup update) and/or KB4474419, both are installed.
I've checked gvm.sys properties in Windows from Canary 4 and it shows digital signatures: Google LLC and Microsoft Windows Hardware Compatibility Publisher both sha256, V2.
For example, NVIDIA's nvhda64v.sys also have Microsoft Windows Hardware Compatibility Publisher (V2), but two version from NVIDIA (v1, v2), not sure if that matters. Other drivers like tcpip.sys have only SHA256, V2 signature.
Also it seems that silent_install.bat -u doesn't completely remove the gvm.sys from my system - it's left inside C:\Windows\System32\drivers folder.
I've checked gvm.sys properties in Windows from Canary 4 and it shows digital signatures: Google LLC and Microsoft Windows Hardware Compatibility Publisher both sha256, V2.
For example, NVIDIA's nvhda64v.sys also have Microsoft Windows Hardware Compatibility Publisher (V2), but two version from NVIDIA (v1, v2), not sure if that matters. Other drivers like tcpip.sys have only SHA256, V2 signature.
Also it seems that silent_install.bat -u doesn't completely remove the gvm.sys from my system - it's left inside C:\Windows\System32\drivers folder.
hs...@google.com
We are working on adding that V1 signature. However, according to Microsoft, it should not be needed. No one really knows why.
gv...@gmail.com
Not sure if needed but here are some additional logs from Event Viewer -> Windows Logs -> Security:
Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error.
File Name: \Device\HarddiskVolume4\Windows\System32\drivers\gvm.sys
Details:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event ">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
<EventID>5038</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12290</Task>
<Opcode>0</Opcode>
<Keywords>0x8010000000000000</Keywords>
<TimeCreated SystemTime="2019-12-02T19:48:22.660518200Z" />
<EventRecordID>170801</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="56" />
<Channel>Security</Channel>
<Computer>X64</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">\Device\HarddiskVolume4\Windows\System32\drivers\gvm.sys</Data>
</EventData>
</Event>
Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error.
File Name: \Device\HarddiskVolume4\Windows\System32\drivers\gvm.sys
Details:
<Event xmlns="
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
<EventID>5038</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12290</Task>
<Opcode>0</Opcode>
<Keywords>0x8010000000000000</Keywords>
<TimeCreated SystemTime="2019-12-02T19:48:22.660518200Z" />
<EventRecordID>170801</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="56" />
<Channel>Security</Channel>
<Computer>X64</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">\Device\HarddiskVolume4\Windows\System32\drivers\gvm.sys</Data>
</EventData>
</Event>
hs...@google.com
Thanks! Using google, I've seen a few threads talking about the same issue as yours (with other drivers). They also installed the required Windows 7 updates.
So far, adding SHA1 should be the best solution.
So far, adding SHA1 should be the best solution.
gv...@gmail.com
I've tried using signtool to verify the gvm.sys (pitily I only have VS2013).
It verifies with success only if I use "/pa" flag otherwise it shows same output but also the next error: "SignTool Error: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider."
I wonder if kernel-mode drivers should be signed differently, like this:https://knowledge.digicert.com/solution/SO20529.html
NOTE /kp flag for kernel signing!
There is also some kind of driver signing policy:https://docs.microsoft.com/en-us/windows-hardware/drivers/install/kernel-mode-code-signing-policy--windows-vista-and-later-
I'm sorry that's all I can report as I never had experience with driver's signing.
It verifies with success only if I use "/pa" flag otherwise it shows same output but also the next error: "SignTool Error: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider."
I wonder if kernel-mode drivers should be signed differently, like this:
NOTE /kp flag for kernel signing!
There is also some kind of driver signing policy:
I'm sorry that's all I can report as I never had experience with driver's signing.
ch...@gmail.com
class MainActivity : AppCompatActivity() {
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContent {
Greeting("Android")
}
}
}
@Composable
fun Greeting(name: String) {
Text (text = "Hello $name!")
}
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContent {
Greeting("Android")
}
}
}
@Composable
fun Greeting(name: String) {
Text (text = "Hello $name!")
}
hs...@google.com
We are waiting for certificate for legacy Windows 7 driver signing. Update will be provided once there is progress.
so...@gmail.com
Dear sirs, any news about the legacy Windows 7 driver signing? Please hurry up, as Windows 7 just arrived to its End-Of-Life. Thanks. Regards.
hs...@google.com
I would like to update if I can. However, our internal team handling certificate has not delivered the certificate I needed yet.
I am sorry for that.
I am sorry for that.
hs...@google.com
Microsoft has created a problem to us. Microsoft is stating that the same type of signing (for Win10) can be supported by Win7. And the old signing for Win7 should not be used. I have to explain to any internal supporting team members that it is not true.
I am hoping I can get the needed certificate in the end.
I am hoping I can get the needed certificate in the end.
gv...@gmail.com
As I stated previously: are you sure that gvm.sys is signed as kenel-mode driver (/kp flag when signing and verifying)? and should it be? I suppose it should as it's probably using some low-level stuff.
Example for nvidia nvlddmkm.sys vs gvm.sys:
"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Bin\signtool.exe" verify /kp nvlddmkm.sys
Successfully verified: nvlddmkm.sys
"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Bin\signtool.exe" verify /kp gvm.sys
SignTool Error: Signing Cert does not chain to a Microsoft Root Cert.
Both pass verify when not using /kp.
Example for nvidia nvlddmkm.sys vs gvm.sys:
"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Bin\signtool.exe" verify /kp nvlddmkm.sys
Successfully verified: nvlddmkm.sys
"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Bin\signtool.exe" verify /kp gvm.sys
SignTool Error: Signing Cert does not chain to a Microsoft Root Cert.
Both pass verify when not using /kp.
hs...@google.com
It is signed as kernel-mode driver. But it is signed using Windows 10's way.
I once was told and I thought this could work also on Windows 7 as Windows 7 would get needed supports from Windows updates.
Apparently, either I misunderstood Microsoft's doc or the doc could be wrong.
In order to get the driver signed for Windows 7, I am requesting needed certificate. I believe once I get it, the driver should pass this /kp check. It looks like this checking is only for Windows 7.
I once was told and I thought this could work also on Windows 7 as Windows 7 would get needed supports from Windows updates.
Apparently, either I misunderstood Microsoft's doc or the doc could be wrong.
In order to get the driver signed for Windows 7, I am requesting needed certificate. I believe once I get it, the driver should pass this /kp check. It looks like this checking is only for Windows 7.
hs...@google.com
Can anyone try and see whether this package works?
hs...@google.com
It does not pass "/kp" check but it does load on my Windows 7 test laptop.
gv...@gmail.com
I confirm this one working. Driver installs fine, state is RUNNING. Emulator works fast!
fe...@gmail.com
Confirming package works, emulator running. Thank you!
hs...@google.com
Thanks! I will then work on releasing the driver via Android Studio. I will update once it is done. But I believe you can simply bypass the Android Studio release unless it happens to release 1.4 at the same time.
so...@gmail.com
I confirm this one is working even under Windows 7 driver test mode off - now I can work with test mode disabled. Now command "sc query gvm" gives "RUNNING". Thanks for your support.
hs...@google.com
I am releasing 1.4 to github and Android Studio with needed Windows 7 support. Thanks!
You can download from github and have a try. Update from Android Studio Sdk Manager should be available in a week.
You can download from github and have a try. Update from Android Studio Sdk Manager should be available in a week.
an...@gmail.com
I have Asus Tuf fx505DT and my android emulator was freezing on startup.
I got 4RUNNING status on silent_setup.bat which was normally expected .
The fix which i found for my laptop and maybe similar laptops:--
If you have laptop with AMD processor with NVIDIA dedicated gpu then go to nvidia control panel and add these two programs and select High performance NVIDIA processor.
file location : C:\Users\anila\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64
files to be added : qemu-system-i386.exe , qemu-system-x86_64.exe
If you have AMD Desktop processor without integrated graphics and dedicated gpu , everything must work normally.
If you have Amd processor with integrated gpu and no dedicated gpu then i don't know.
I got 4RUNNING status on silent_setup.bat which was normally expected .
The fix which i found for my laptop and maybe similar laptops:--
If you have laptop with AMD processor with NVIDIA dedicated gpu then go to nvidia control panel and add these two programs and select High performance NVIDIA processor.
file location : C:\Users\anila\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64
files to be added : qemu-system-i386.exe , qemu-system-x86_64.exe
If you have AMD Desktop processor without integrated graphics and dedicated gpu , everything must work normally.
If you have Amd processor with integrated gpu and no dedicated gpu then i don't know.
ne...@gmail.com
Helo, i use CPU R9 3900X, but when i try execute "silent_install.bat" in Administrator CMD, i use Windows 10 the last update.
Output is:
[SC] ControlService FAILURE 1062:
The service did not start.
[SC] DeleteService SUCCESS
[SC] StartService FAILS with error 4294967201.
Output is:
[SC] ControlService FAILURE 1062:
The service did not start.
[SC] DeleteService SUCCESS
[SC] StartService FAILS with error 4294967201.
hs...@google.com
This could mean:
1> You may have BIOS disabled virtualization.
2> You may have enabled hyper-V explicitly or implicitly (such as WSL2, Windows Sandbox, Credential Guard, etc).
1> You may have BIOS disabled virtualization.
2> You may have enabled hyper-V explicitly or implicitly (such as WSL2, Windows Sandbox, Credential Guard, etc).
hs...@google.com
an...@gmail.com
My AVD is freezing after some use . Any fix for this?
I am using Dedicated Nvidia GPU for startup as emulator doesn't start while using Integrated Vega GPU .
I am using Dedicated Nvidia GPU for startup as emulator doesn't start while using Integrated Vega GPU .
hs...@google.com
AVD frozen? Are you using 1.5? 1.5 fixed a frozen issue like your describe. And you will need to coldboot once after updating the driver in order to clear the hang status.
ta...@gmail.com
Upon inputting the following path: C:\Users\tavis\AppData\Local\Android\Sdk\extras\google\Android_Emulator_Hypervisor_Driver>silent.install.bat
I got a message stating the service has not started.
Do you all have any fixes?
I got a message stating the service has not started.
Do you all have any fixes?
hs...@google.com
As I said before, the reason of failure could be 1> SVM is not enabled in BIOS 2> Hyper-V is enabled. These are not bugs.
Ar...@seznam.cz
Hi. This issue isn't fixed at all. I just tried now to install this driver on my old Windows 7 laptop (with all latest updates installed) and I got this exact same error (that Windows requires a signed driver and this is unsigned - Start service error number 577) in both Android studio and manual installation.
hs...@google.com
Can you upload the driver package you used here? As I could not reproduce the problem, let me try to check whether the driver package is correct.
hs...@google.com
I've reproduced the issue with driver 1.8. It seems the problem is related to the deprecation of SHA1 (Microsoft's policy). Can you try to download 1.7 and see if it works?
Ar...@seznam.cz
Sorry for late answer, as the emails alerting me about it fell to spam for some reason. I used both the latest versions on Github and the one which Android Studio downloads, which is the mentioned 1.8 at the Github version. I'll try the version 1.7.
Ar...@seznam.cz
The version 1.7 successfully installed and is in status of kernel driver running. I'll add the both packages of 1.8 and 1.7 to this message, which I got from the Github version of the driver, in case that they are further needed.
Thanks for the help.
Thanks for the help.
Description
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 29.2.11.0 (build_id 6031357) (CL:N/A)
HAXM / KVM Version: none
Android SDK Tools: 26.1.1
Host Operating System: Windows 7 Ultimate 64-bit, Service Pack 1
CPU Manufacturer: AMD FX-8320
Steps to Reproduce Bug:
1. Just run \android-sdk\extras\google\Android_Emulator_Hypervisor_Driver\silent_install.bat
Expected Behavior:
No errors on result of silent_install.bat, emulator runs x86/x86_64 images without asking about HAXM.
Observed Behavior:
Running "\Android_Emulator_Hypervisor_Driver\silent_install.bat" installs the driver but unable to start it.
Installer outputs:
[SC] ControlService FAILED 1062:
The service has not been started.
[SC] DeleteService SUCCESS
[SC] StartService FAILED 577:
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
If I start Windows with F8 menu and turn off digital signatures check - gvm.sys installs, emulator works fast and fine until reboot. Some tiny errors logget from Android studio in this case: Emulator: D:\Android\android-sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
PS All Windows Update patches are installed. I remember there were some changes for digital signatures in updates.