Hantek 6022BL driver install crashes Windows 10

davidjo

I have tried a number of methods of installling drivers for the 6022BL model under Windows 10 (64 bit).  On two previous computers it involved installing Saleae Logic Analyser drivers and also changing the startup behaviour of Windows 10 to accept non-signed drivers.  On my rebuilt new Windows 10 hardware I have had failure after failure.

From this forum site I downloaded the drivers and expanded them.  I didnt install the Hantek Software at this stage.  
After plugging in the PC Oscilloscope Device manager reported an unknown device an error I expected. I followwed the update driver instructions as listed in this forum and pointed to the driver folder.  

Even though I am installing the English drivers Windows asks whether I trust this software (labelled in Chinese).  Image is attached.


The driver installed and for a brief second I saw the Windows message saying that the device was correctly installed.  
About 1-2 seconds later the Windows blue screen appears with the message:

Blue Screen message:
Stop Code: SYSTEM THREAD_EXCEPTION NOT HANDLED
What failed: Hantek6022BLAMD642.sys

While the 6022BL is plugged into a USB port the PC crashes.  The 6022BL has the button pressed in at the rear of the instrument.  If I remove the 6022 from the USB the system stops crashing but from now on there is no way to remove the faulty driver as if I plug the PC Oscilloscope in to the USB  Windows 10 crashes immediately.  Thankfully I do a complete System backup before trying to reinstall Hantek driver.

Even though I am installing the English drivers Windows asks whether I trust this software.  Image is attached.

Do you have signed drivers and something that will work and not crash Windows 10  64bit.???

I am at the stage of replacing the PC Oscilloscope with another brand as this is totally frustrating.  Are you able to help?
Regards
David

amy

Go to this path (C:\Windows\System32\drivers) and find the file (Hantek6022BLAMD641.SYS/Hantek6022BLAMD642.SYS).
Go to this path (C:\Windows\INF) and find the new .oem files (which may contain these"USB\VID_04B4&PID_602A.DeviceDesc%=Hantek6022BL1.Dev, USB\VID_04B4&PID_602A
%USB\VID_04B5&PID_602A.DeviceDesc%=Hantek6022BL2.Dev, USB\VID_04B5&PID_602A").
Delete these files.

And try update again.

If the problem still exists after the update, please let me know.