HereLink Airunit fails at FW update

Hello All,
I’m getting a usb1.USBErrorTimeout: LIBUSB_ERROR_TIMEOUT [-7] when flashing the latest FW on the Air unit. Any suggestions?
BTW, I’m updating the FW because I get constantly on QGroundcontrol the message “Communication Lost”

D:\FW_Herelink> .\flasher_win.exe
Looking for Device…
Found Unit Type: airunit

Downloading required package…
Latest airunit release: AU01200226
Downloading Latest Release from
airunit-AU01200226.tar.gz: 100%|███████████████████████████████████████████████████▉| 408M/409M [03:18<00:00, 2.16MB/s]
Successfully download package
Extracting package…
100%|██████████████████████████████████████████████████████████████████████████████████| 20/20 [00:05<00:00, 3.38it/s]
Successfully extracted package
Flashing Unit…
Flashing partition: 100%|█████████████████████████████████████████████████████████████████████| 213/213 [00:00<?, ?B/s]
Flashing persist: 100%|███████████████████████████████████████████████████████████| 4.30M/4.30M [00:00<00:00, 51.1MB/s]
Flashing oem: 100%|███████████████████████████████████████████████████████████████| 4.56M/4.56M [00:00<00:00, 54.2MB/s]
Flashing boot: 100%|██████████████████████████████████████████████████████████████| 21.7M/21.7M [00:00<00:00, 46.5MB/s]
Splitting Sparse Partition system.img @ C:\Users\Bart\AppData\Local\Temp\tmptqzwiset
Flashing system 1/10: 100%|███████████████████████████████████████████████████████| 56.0M/56.0M [00:01<00:00, 44.1MB/s]
Traceback (most recent call last):
File “site-packages\adb-1.3.0-py3.8.egg\adb\”, line 175, in BulkWrite
File “site-packages\”, line 1546, in bulkWrite
File “site-packages\”, line 1517, in bulkTransfer
File "site-packages\usb1_init
.py", line 133, in mayRaiseUSBError
File “site-packages\”, line 125, in raiseUSBError
usb1.USBErrorTimeout: LIBUSB_ERROR_TIMEOUT [-7]

During handling of the above exception, another exception occurred:

@champ8242 Did you resolve this issue? I am having the same problem.

Found a solution. It was pointed out to us that we were not extracting the zip file before running the file. This causes issues where the files are saved and hence giving us the error. Simply extracting and then running the file solved the issue.

Good you found a solution. We could move on at that time but don’t remember what we did to solve