Win: Alternating usage of OH60222 and "normal" Software

[MaMiKoe]

I can use the last 32-bit-version of OH60922 in Win10 and the newest 64Bit-Version, but I also would like to use alternative, for special purposes "normal" Software für the 6022, e.g. PCScope (linked in one of my other posts), which need the standard-Hantek-driver. After installing the winusb-driver for OH6022 with Zadik the "normal" Hantek-driver does not recognize the 6022. So the usage of the "normal" software for the 6022 needs the complete deinstallation of the drivers for OH6022. And of course re-installation when I want to use OH6022 again.
Does somebody has an idea how an easy swap between the programs w/o the complete deinstallation and re-installation of the OH6022-driver can be performed? My first idea was using different USB-ports but I don´t find a way "fixing" driver to a single USB-port.

[MaMiKoe]

I have found a solution by mself, not for fixing to an USB-port but for one-cklick-changing of the driver. For all other with the same "problem" here is my way (maybe there is some easier solution I don't know):

Both drivers - the original Hantek-driver and the winusb-driver for OH6022 - must already be installed previously one time so that they are not only in Windows' DriverStore/FileRepository (C:\Windows\System32\DriverStore\FileRepository) but also in the Inf-directory (C:\Windows\INF):

At first I have installed the normal Hantek-driver (done for the 6022BL, the following description refers to 6022BL):
You can do this with the "normal" Hantek-software-installation or manually: Attaching the 6022 to the PC and updating/installing the driver for this found new device in the traditionell, well-known way by selecting the driver in the Hantek-driver-directory (for the BL it is HT6022BL_Driver\Driver for Win10); for Win7 and Win10 I have used the Win10-driver. This works with Win7/Win10, 32/64 bit.
As result the devive manager shows a new category "Hantek6022BL". In this category there is in Win7 as hidden entry "Hantek6022BL DRIVER 1" (to see it you have to enable the display of the the hidden entries and the entry is greyed) and when the 6022BL is attached also "Hantek6022BL DRIVER 2" which seems to be the "real active" driver in Win7. In Win10 only when the 6022BL is attached I saw "Hantek6022BL DRIVER 1" visible as "real active" driver and no hidden entry.
Nearly every time I have testet I was able to install the winusb-driver for OH6022 as followed: With attached 6022BL I selected the "Hantek6022BL DRIVER 2" in Win7 (or "Hantek6022BL DRIVER 1" in Win10) for updating the driver and selected as place of new driver the OH6022-directory (for 32Bit I have used the OH6022 x86-Release-b488). As result a new category "USB devices" appeared with the active entry (= new driver) "Hantek6022BL". Corresponding in the category "Hantek6022BL" the entry "Hantek6022BL DRIVER 2" in Win7 (and "Hantek6022BL DRIVER 1" in Win10 ) disappeared and in Win7 the hidden/greyed entry "Hantek6022BL DRIVER 1" is left.
After starting OH6022 and loading the firmware into the 6022BL the entry "Hantek6022BL" changed to hidden/greyed and a new active entry "DSO-6022BL" appeared. This stays while the 6022BL is attached and holds the new fimware.
Sometimes - I don' t know why - this procedure does not work and I have to install the new driver with the Zadig-software es explained. In this case sometimes some entries appeared twice so that I had to delete one (with help of DriverStoreExplorer Rapr.exe).
After powering-off the 6022BL and re-attaching it the entry "DSO-6022BL" changes to hidden/greyed and the entry "Hantek6022BL" is active.
After this initial install of the drivers the changing between the the "normal" software with the original Hantek-driver and the OH6022 and it´s winusb-driver is possible by "simple" updating (replacing) the current active driver with the other, needed driver: When selecting the manually updating and usage of a list of current drivers the drivers "Hantek6022BL" for OH6022 and "Hantek6022BL DRIVER 2" (or "Hantek6022BL DRIVER 1" in Win10) for the "normal" software are available and you have to select the driver you want to change to.
When changing from OH6022 (winusb) to "normal" software (original Hantek-driver) it is important that at first the 6022 ist swichted-off and -on for using the normal firmware in the 6022, so that not "DSO-6022" is active but "Hantek6022BL". Then the entry "Hantek6022BL" disappeared and in the category "Hantek6022BL" the entry "Hantek6022BL DRIVER 2" reappaered in Win7 (or "Hantek6022BL DRIVER 1" in Win10).

A very helpful tool for dealing with the drivers and driverstore is the DriverStoreExplorer Rapr.exe which you can find also in github.

Doing this changing/updating the drivers takes some time and clicking. Maybe there is a way of automation/"batch" with the device manager I do not know, but with using the MS-command-tool devcon.exe and two batch-files it can be done with one click. For obtaining devcon.exe please use google; there are a lot of explanations how to obtain this tool w/o installing the whole packet.
After running cmd.exe as admin you can force with
devcon update
(where specifies an INF file with installation information for the devices and specifies the hardware ID of the devices)
the updating/changing of drivers.
The name of the needed inf-files we find with
devcon drivernodes "04B
The result is for example
....
Inf file is C:\Windows\INF\oem12.inf
Inf section is Hantek6022BL2.Dev
Driver description is Hantek6022BL DRIVER 2
...
and
...
Inf file is C:\Windows\INF\oem13.inf
Inf section is Install
Driver description is Hantek 6022BL
...
So in this example when chaning to the original Hantek-driver the needed inf-file is C:\Windows\INF\oem12.inf and when changing to OH6022 it is C:\Windows\INF\oem13.inf
The needed hardware-ID we find either in the device-manager as well-known (details, hardware-ID) or also with decvon:
devcon hwids "04B
It reports in this example
USB\VID_04B5&PID_602A\5&B248509&0&1
Name: Hantek6022BL DRIVER 2
Hardware IDs:
USB\VID_04B5&PID_602A&REV_0000
USB\VID_04B5&PID_602A
or
USB\VID_04B5&PID_602A\5&B248509&0&1
Name: Hantek6022BL
Hardware IDs:
USB\VID_04B5&PID_602A&REV_0000
USB\VID_04B5&PID_602A
and we need the ID USB\VID_04B5&PID_602A&REV_0000
( I can´t explain why but also with the Hantek-driver the hw-ID starts with 04B5).
So the commands for changing the drivers are
devcon update C:\WINDOWS\INF\oem12.inf "USB\VID_04B5&PID_602A&REV_0000"
for changig to the original Hantek-driver (in this example)
and
devcon update C:\WINDOWS\INF\oem13.inf "USB\VID_04B5&PID_602A&REV_0000"
for changing to winusb and OH6022 (in this example).
Put the command it into batch files, link them to where you want and give them Admin-rights (devcon needs Admin-rights).