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.
Related
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.
I'm using Android Studio on windows 10 currently. However, as I try to install HAXM via android studio, there is an error which always pops up "This computer does not support Intel Virtualization Technology (VT-x) or it is being exclusively used by Hyper-V. HAXM cannot be installed".
The weird thing is that when I checked my installed programs, HAXM is already installed by default. I have no idea why I am not able to upgrade. I'm using a decent gaming laptop with an 8th Gen Intel Core i7 processor.
Things I have tried :
I have already went into my bios and made sure all virtualization options were enabled and went to "Windows Features"and unchecked Windows Hyper-visor Platform but to no avail as the problem still persists
I recently had the same issue, and even though Intel virtualization was enabled in the BIOS and my Windows 10 doesn't have the Hyper-V option because it's the home edition, I wasn't able to use Android Studio emulators/virtual machines or upgrade/reinstall Intel HAXM. I then found out that an enabled feature on Windows Defender was the cause of the problem. Try the following steps (sorry, my device is in portuguese so the options might have another naming other than the direct translation to english):
In Windows Defender, go to Device Security (The one with a laptop icon).
Choose Kernel Isolation Details (first option).
And disable the Memory Integrity option if it isn't disabled already (in case it is, I'm sorry but this solution won't help you out).
If you have to change the option to disabled, restart your computer and try upgrading HAXM via Android Studio again.
I hope this helps. :)
In my case, after disabling Hyper-V in Windows Features I had to turn the antivirus (Kaspersky) off to install Intel x86 Emulator Accelerator (HAXM) 7.5.6 on Windows 10 Pro (1909).
IF u have AMD CPU you have to install Driver for AMD processor Check img
Win7(64), nvdia 960.
All of a sudden 90% of my games stopped working. My oldest game (GOC 1998) works using dxwnd. My newest game (For Honor-online 2017) still works, but Total War, Tropico4 and Americas Army doesnt detect my graphics card anymore. Ive reinstalled drivers,games,contacted MSFT and Nvidia support but keep getting graphics errors. I think a recent MSFt update fugged something.
Has anyone else had this error?
Tried to update my BIOS step by step but get the "bad command" error. That's another topic i may start.
Use DDU http://www.guru3d.com/files-details/display-driver-uninstaller-download.html
Install latest Nvidia drivers
Make sure you have latest chipset drivers for your motherboard installed.
If all else fails, open cmd as admin and run sfc /scannow
Fixed it by doing what I was trying to avoid, reinstalled the entire OS.
It appeared to be corrupt or missing windows drivers, possibly msft vc 2008 x64,x86 version(9.0.30729.6161) and msft vc 2010 x64,x86 version(10.0.40219) along with a ton of other drivers during reinstall. It took about 3+ hours.
I've been using Genymotion, but its been pretty laggy. I only had HAXM accelerator installed so I decided to mess with VM manager, but it only seems to have made it worse. Now it runs smoothly but upon opening any application, it will either wait a bit then tell me the application isn't responding, or just freeze all together and give me a "player.exe has stopped working" dialog box. My changed system settings are as follows:
1 processor,
1024MB for the motherboard,
128MB for video with 3D acceleration enabled.
All other configurations are set to default.
I have an intel i5-2450M 2.5GHz chip with virtualization enabled in the BIOS.
Before when I had only HAXM installed, it worked fine. Just lagged a lot.
Help would be much appreciated.
You are using Windows 10?
Try to reinstall genymotion deleting all geny folders from your computer, remove virtualbox too.
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.