This is a chronological continuation of this question.
I have simplified my board so it runs well with the DDK version of BulkUSB on 32bit versions of XP and Vista, but I'm not able to install it on Vista 64.(built with amd64 fre)
I've been able to make windows recognize the files it needs to install, using both BulkUSB and USBSamp, but once installed it says
Windows cannot load the device driver for this hardware.
The driver may be corrupted or missing. (Code 39)
In problem code property in the details, it says 27.
When I install it for the first time, it complains about the driver not being digitally signed, and I've tried running:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
As there are placed that mention it should make windows run unsigned drivers, but it doesn't help.
If anyone has an insight about this, any help will be appreciated.
Thank you,
Surd.
Edit another part of the deal it took me a long time to find that isn't anywhere in the questions or answers:
When unintalling a driver, you either need to check "remove driver" in the device manager or use pnputil -d oem##.inf to remove the driver, otherwise the new drivers won't be used.
Even after changing the bcedit options, it is impossible to load unsigned drivers under Windows Vista/7 64 bit. You need to make test-signing for the driver. I solved this problem following instructions from "Kernel-Mode Code Signing Walkthrough" document which can be downloaded from the Microsoft site: http://www.microsoft.com/whdc/driver/install/drvsign/kmcs-walkthrough.mspx
Unsigned drivers cannot be loaded by Vista/7 64 bit in any case. Test-signied drivers can be loaded after changing bcedit options. Release-signed drivers are loaded without restrictions, but with warning message. You can make test-signing yourself, following this document instructions. For release-signing, it is necessary to buy a code-signing certificate.
The final (and optional) step is passing the tests from the Windows Logo Kit (WLK). This allows to remove the warning message shown during driver installation.
I am getting this error message on windows 10: 'Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)'.
After following https://www.tenforums.com/tutorials/104025-turn-off-core-isolation-memory-integrity-windows-10-a.html this, the issue is solved for me.
Related
I was trying to install SDK and Emulator without the Andriod studio on Ubuntu 20.04.
But got stuck at this error.
E0520 11:06:29.866803544 5261 socket_utils_common_posix.cc:201] check for SO_REUSEPORT: {"created":"#1589952989.866791260","description":"SO_REUSEPORT unavailable on compiling system","file":"/mnt/tmpfs/src/android/emu-master-dev/external/grpc/src/core/lib/iomgr/socket_utils_common_posix.cc","file_line":169}
checkValid: hw configs not eq
I got the solution from this article:
So in order to fix this, I just disabled the Camera by switching the option from Emulated to None and that was all.
Don't ask why this works, but it seemed to solve it for me.
Install Android SDK Platform tools. if already exist uninstall and install Android SDK Platform tool in ubuntu 20.04
Seems a GPU issue, try :
sudo ubuntu-drivers autoinstall
Or (or both) change graphic emulated performance to software if your emulated device allow it.
Had same issue with linux mint android studio ..
Hope it will help.
Though not directly affected by the error you described, when stuck at this point (namely, when supposed to be connecting back to the ADB server, but can't), this can be a result of a corrupted quick-boot snapshot.
What worked for me is to hard-delete the existing quick-boot snapshot, and have the emulator regenerate it on the next run.
To delete the snapshots:
rm -fr ~/.android/avd/<AVD name>/snapshots/default_boot
To regenerate the next snapshot, rerun the emulator as you normally would, then kill it after if full loads. But first, make sure that it is configured for saving a quick-boot snapshot on exit:
Edit quickbootChoice.ini, for example:
vi ~/.android/avd/<AVD name>/quickbootChoice.ini
The only line there should be:
saveOnExit = true
If you wish to see whether any of this is likely to help you before making any changes, run the emulator with the -no-snapshot argument applied, beforehand. For example:
$ANDROID_SDK_ROOT/emulator/emulator -no-snapshot #Pixel_API_29 &
(Or find a way to do this through Android Studio)
A note regarding other answers here that advised configuring the camera differently (which seems unrelated): It is very likely that changing the camera setting, for the Emulator, is considered a configuration change - which ends up in forcing a cold-boot (i.e. skipping usage of the quick-boot snapshot), which can explain why it works (but with no voodoo involved).
Goodix Fingerprint sensor not working after windows 10 1903 update on my Dell G3 3579.
It worked while installing windows 10 1903 via iso (which failed to update otherwise), windows hello was all good during setup but after first boot then it just stopped working & driver shows error code 31 on device manager.
I tried updating everything & also tried reinstalling Goodix fingerprint driver but that didn't work either. The fingerprint worked fine on the previous 1809 update of windows 10.
..
images attached showing errors.
Just wanted to update it got fixed, without re-intalling windows.
I did a couple of things with a guy from nearest dell partner who provided me free technical support at their center, He guided me a little and I did a few things on my own. I don't know what fixed it but I'll go on chronologically.
First I downloaded a utility named UsbSafelyRemove and using this I stopped the power to the fingerprint sensor virtually without having to disconnect it, this removed it from devicemanager by preventing it from getting detected for current session. Then I uninstalled the sensor driver software and it was no longer detected aswell. Then I downgraded the bios using Dells Bios Tool, Meanwhile Microsoft or maybe Dell launched an un-logged/unscheduled automatic update and perhaps a possible patch for windows, I don't know if they did it or if it was windows on its own because it wasn't logged. I then restarted the computer, the sensor was detected and appropriate drivers were automatically installed, didn't check for error at this time. Then my antivirus software also found a simple PUP.Optional.OpenCandy malware, which shouldn't likely have any effect. I enabled Microphone for a skype call and just out of the blue the sensor error code 31 which I was checking for frequently, just disappeared. I have now upgraded my bios and the sensor still appears to work. I believe the miracle was due to the windows update most probably, just for reference I was on windows 10v.1909 before and even now, the update was minor a fix perhaps.
I still don't know what caused the error 31, & which particular update fixed the conflict, was it dell support software which was continuously on or windows, but I'm pretty sure its fixed.
Thanks to all those who helped for your time & support.
This error happened under Android studio 3.4. I'm using Windows 10. I didn't find any way to fix it on the other threads asking the same question.
Especially, I've installed Intel HAXM manually, my BIOS settings are allowing virtualization, it can't be a problem involving my anti-virus as I tried to run my project while it was disabled, I've also rebuild my project each time.
What am I missing? Thanks already to all those who will answer me.
Solved. I had to go change the advanced settings of the emulated software, changing the "graphics" value by "software ..." instead of "hardware ...".
I've got a new Dell Inspiron 17 (7779) laptop with Windows 10 x64 (1703) which was working fine right up until the point where HyperV was installed. Now the host screen flickers like mad even with no Guest VM's created.
Dell are being particularly unhelpful, so I was wondering is anyone else was having the same issue.
Basically is anyone running Hyper V on a dell Inspiron successfully.
I guess it could also be a clash with the display drivers (Intel HD Graphics 620, driver ver 21.20.16.4627)
OK, I think I've resolved this with the latest Intel graphics drivers 21.20.16.4678, however there were a few issues...
So the Intel drivers (21.20.16.4627) installed on the machine were the ones installed via the Dell Driver Detect tool, if you just download the latest drivers from intel and install them, it wont update them....I think there is some versioning issue with the dell drivers, as it seems to think the existing drivers are newer than the ones your trying to install....
In order to make it accept the new drivers you need to uninstall the existing display driver AND delete the install files. Then after a re-boot the display drivers used should be the default Microsoft ones, you can then upgrade the driver (again via computer manager) selecting the location of the downloaded and unzipped intel drivers.
I'd like to be able to thank Dell for there help, but they failed miserably to provide any.
One last thing...
For some reason windows automatically 'upgrade' the display drivers and re-installed a old version (21.20.16.4627) replacing the latest drivers I installed. I then had to rollback the automatic update, which fixed the issue again. Hopefully I won't have to keep doing this...
It looks like someone has made a mess of versioning some of these updates, its difficult to tell whether its an issue with the Intel drivers or the Dell wrapping of them as part of the driver detect tool, but there's definitely an issue.
Post installing Windows 10 , and then Visual studio 2015 pro, I found , to my disappointment , that my laptop model G480lenovo doesn't support Hardware virtualization. In fact there is no entry for "CPU" in my BIOS configuration section.
So then , there is no phone emulators which I could use available in my VS
What are the alternatives here for the emulators that I could use, for testing universal windows applications?
Any pointers here?
If you cannot run Hyper-V on your machine, you need to test it directly with device.
But...I think it's better to double confirm if the CPU doesn't support SLAT. There is tools called Coreinfo. And you can download it from windows sysinternals.
After you download it and extract to a folder(for example: c:\coreinfo). Open command prompt as administrator and navigate to the folder(cd c:\coreinfo), then run coreinfo.exe -v (as below image shows). You can see it is supported on my end.
I did a quick research and found the G480 Lenovo uses i5-3210M or i3-2370M. And found the following specifications on intel official website which indicates both CPU support the EPT(Extended Page Tables) which is SLAT.
http://ark.intel.com/products/67355/Intel-Core-i5-3210M-Processor-3M-Cache-up-to-3_10-GHz-rPGA
http://ark.intel.com/products/53442/Intel-Core-i3-2370M-Processor-3M-Cache-2_40-GHz
If you cannot find the options in BIOS, I think you need to contact your vendor to help you and maybe you need to update your BIOS firmware.