 | 1 | initial version |
As is usually the case, this is likely to be an npcap issue, as that's the 3rd party software installed by Wireshark that actually talks to the hardware. Upgrading to 3.2.7 will install, if you allow it, a newer version of npcap from your previous version that may have caused this issue.
Npcap have subsequently released a newer version (1.00) that may or may not fix this issue, try downloading it directly from their site and installing it. If you still get the issue then report it on the npcap issue tracker.
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
