Hantek 6022BE drivers for Windows 10/11: the setup that works (OpenHantek6022 + Zadig)

The Hantek 6022BE has two driver worlds, and most install failures on Windows 10 and 11 come from mixing them up. The setup that works today is OpenHantek6022 3.4.1-rc2 with WinUSB, installed either from the signed OpenHantek.inf that ships in the zip or with Zadig run twice. If you want to stay on Hantek’s own software, the fix is the separate 2025 driver package, not the driver folders inside the software ZIP.

Last verified: 7 November 2026. Every file below was downloaded and hashed on that date.

Setup on Windows 10/11: OpenHantek6022 with the signed INF

The project README states that “the original Hantek driver for Windows doesn’t work” with OpenHantek. It needs WinUSB, and the zip brings an INF that assigns it. We read that INF: it has no kernel code of its own. It pulls in Windows’ built-in WinUSB.inf for 04B4:6022 and 04B5:6022 (the 6022BE before and after firmware), plus the 6022BL, the Voltcraft DSO-2020 and the sigrok firmware ID 1D50:608E. Its catalog is signed through a Sectigo code-signing chain.

1. Download the zip and check it. In PowerShell: Get-FileHash .openhantek_3.4.1-rc2_msvc_x64.zip, which defaults to SHA-256.
2. Extract it anywhere, for example C:OpenHantek. There is no installer.
3. Open the driver folder, right-click OpenHantek.inf and choose Install. On Windows 11, if Install is missing from the short menu, open “Show more options” first.
4. Plug the scope straight into the PC, with no hub. The user manual says to move to a USB 2.0 port if a USB 3 port gives trouble.
5. Start OpenHantek.exe. It uploads firmware into the scope’s RAM, and the device re-enumerates as 04B5:6022. Per the manual, the LED left of CH1 blinks red once the upload succeeds. If it takes longer than 30 s, close the program and start it again.
6. Check the title bar for FW0210. If the scope was last used with Hantek’s software or sigrok, unplug and replug it once first.
7. Smoke test: probe on CH1 switched to 1X, hook on the left calibration terminal, ground clip on the right one. You should see a 0–2 V, 1 kHz square wave. Drag the yellow trigger arrow into the trace and the red “TR” turns green.

Fallback: Zadig, twice

The project’s build notes say Zadig must assign WinUSB “twice”: once for the ID the scope boots with and once after the firmware has made it re-enumerate. They also say you don’t need to uninstall Hantek’s driver first, because Zadig replaces it.

1. With the scope plugged in, run Zadig (use Options → List All Devices if it isn’t listed). Pick USB ID 04B4 6022, choose WinUSB and click Install Driver. The project’s tutorial says it takes about a minute.
2. Start OpenHantek. “Connection failed!” is expected at this point: the firmware went up, and the scope is now DSO-6022BE, 04B5 6022.
3. Run Zadig again on 04B5 6022 with WinUSB.
4. Replug the scope or restart OpenHantek.

Staying on Hantek’s software: use the 2025 driver

The software ZIP carries two driver folders that both install a file called Hantek6022BE.inf. The separate 2025 download installs a third one with the same name. We read all three catalogs with openssl:

Microsoft’s kernel-mode signing policy says that, starting with Windows 10 version 1607, Windows “will not load any new kernel-mode drivers which are not signed by the Dev Portal”, apart from a few legacy exceptions. Google completed its distrust of WoSign in 2017. And an INF without DriverVer gets the default date 00/00/0000 (INF DriverVer directive), so Windows ranks it below anything else. Install Setup.exe, skip its driver folders, extract the 2025 RAR (7-Zip handles it) and point Device Manager at it with Update driver → Browse my computer. It covers both USB IDs, so the wizard may run twice. We have not bench-tested this path; the signature is the reason to pick it. The two stacks are exclusive per device: switching programs means switching drivers and replugging.

Maximum input voltage

The Hantek 6022BE manual (V1.0.5, Appendix A) lists “Max. Input ±5V” and “Input protection 35Vpk (Without external attenuation DC + peak AC < 10kHz)”. The OpenHantek manual gives the same limits and works out the 10X case:

A 19 V laptop adapter on a 1X probe won’t hurt the input, since it stays under 35 V, but it won’t measure either. The trace sits flat at +5 V, and OpenHantek turns the channel label red to flag clipping. Switch the probe and the software to 10X and the scope sees 1.9 V and displays 19 V. There is no hardware AC coupling, so to look at ripple use the math channel’s “CH1 AC” mode.

Never connect the ground clip to mains, with or without a 10X probe. The OpenHantek manual is explicit: the scope’s GND “is directly connected also to the PC and to the main’s GND”, so connecting it to another voltage “can destroy the scope and the PC”. On top of that, 120 V mains peaks near 170 V and 230 V near 325 V, both far outside the ±50 V a 10X probe gives you. Measuring line voltage takes a differential probe rated for it. The kit’s probes are 1:1/10:1; the manual doesn’t name the model. If yours are Hantek PP-80s, their manual rates them 200 V at 1X and 600 V at 10X, with only 6 MHz of bandwidth at 1X. The scope, not the probe, sets the limit.

Five failures and their fixes

1. LED red, program never gets past the connect screen. Hantek’s manual doesn’t document LED colours. The real tell is Device Manager. Code 52 means Windows couldn’t verify the driver’s signature, and Code 39 means it couldn’t load it. Either way, replace the ZIP driver with the 2025 package or move to WinUSB. Under OpenHantek, a blinking red LED is normal, and FW0210 in the title bar is the proof that it works.

2. “I have to disable driver signature enforcement every boot.” That switch lives in Windows’ Startup Settings, which you choose at a restart; it is not a persistent setting. Neither path above needs it.

3. Trace flickers or jumps. A red “TR” means the software trigger hasn’t locked: drag the trigger arrow into the waveform or use Normal mode. At slow timebases, Auto and Normal only redraw after a full block, so use Roll from 200 ms/div up. Overrun limits are 30 MS/s with CH1 alone and 15 MS/s with both channels (limitations.md). On a weak PC, raise the hold-off. If the window stays black, start it with OpenHantek -e (OpenGL ES), as the README suggests.

4. Waveform too small. Lower V/div until the signal fills 4–6 of the 8 divisions. The classic mistake is a probe on 10X with the software on x1: the trace shrinks tenfold and every reading is off by ten.

5. No CD drive. You don’t need one. Everything is in the download box above, and OpenHantek replaces the whole vendor stack.

Sources

• OpenHantek6022: README, build.md (Zadig), limitations.md, user manual 3.4 and DaPa’s Zadig tutorial (both PDFs inside the release zip)
• Hantek: Hantek6002BE Series page, 6022BE user’s manual V1.0.5, PP-80/150/200 probe manual
• Microsoft: kernel-mode code signing policy, INF DriverVer directive, Device Manager codes 39 and 52, Windows Startup Settings

Related on the bench: Zadig and USBasp, PulseView download (the same FX2 chip as a sigrok device), and how to read an oscilloscope.