 | 1 | initial version |
This sounds like the issue fixed in USBPcap 1.5.3.0 (see https://github.com/desowin/usbpcap/releases).
To use this version, you need to use at least Wireshark 3.1.0 development version as USBPcap 1.5.0.0 and later are not compatible with the 3.0.x Wireshak versions (due to the new control data transfer format that is not supported by earleir version of Wireshark).
As Wireshark 3.1.0 packages USBPcap 1.5.2.0, you need to either manually update it (and copy the USBPcapCMD.exe to the extcap folder of your Wiresahrk installation) or use a Wireshark 3.1.1 nightly build.
Wireshark 3.1.0 development build can be found here: https://www.wireshark.org/#download and 3.1.1 nightly builds here: https://www.wireshark.org/download/automated/
| | 2 | No.2 Revision |
This sounds like the issue fixed in USBPcap 1.5.3.0 (see https://github.com/desowin/usbpcap/releases).
To use this version, you need to use at least Wireshark 3.1.0 development version as USBPcap 1.5.0.0 and later are not compatible with the 3.0.x Wireshak versions (due to the new control data transfer format that is not supported by earleir version of Wireshark).
As Wireshark 3.1.0 packages USBPcap 1.5.2.0, you need to either manually update it (and copy the USBPcapCMD.exe to the extcap folder of your Wiresahrk Wireshark installation) or use a Wireshark 3.1.1 nightly build.
Wireshark 3.1.0 development build can be found here: https://www.wireshark.org/#download and 3.1.1 nightly builds here: https://www.wireshark.org/download/automated/
