The lack of captured packets is either an Npcap issue or a Windows issue, and should be reported on the Npcap issues list.
The message in question is a warning. Please mention it in the issue you file and, if possible, copy and paste it rather than retyping it.
(The message in the libpcap and thus Npcap code begins with "Unknown NdisMedium value", capitalized in that fashion, so it was retyped here. 12 is an odd NdisMedium value for a teamed Ethernet device; it appears that it's NdisMediumCoWan
, which makes no sense, as it "Specifies a wide area network in a connection-oriented environment.", and Ethernet isn't considered a WAN and isn't connection-oriented, so the value may have been different as well. Knowing the correct value might help determine what DLT_ value it should be mapped to.)
Similar to npcap #173.
Can you update the question with the output of
wireshark -v
orHelp->About Wireshark:Wireshark
.Version 4.0.4 (v4.0.4-0-gea14d468d9ca).
message on start capture
Properties of adapter
Opening screen Wireshark
start, no activity stop, message "No packets captured. As no data was ...(more)
The output of
wireshark -v
also includes information onnpcap
(if loaded) and the operating system.Can you add the full output?
OUTPUT OF WIRESHARK -V
(more)"Npcap Packet Driver (NPCAP)" is visible in the local network properties and checkmarked to be active