Ask Your Question

Wireshark 2.6 doesn't find the interfaces and exits the program.

asked 2018-05-16 18:42:34 +0000

this post is marked as community wiki

This post is a wiki. Anyone with karma >750 is welcome to improve it.

After several reinstalls I'm looking for help. Why can't Wireshark find my interfaces? I have reinstalled multiple times WinPcaP and Wireshark 2.6. Wireshark 2.4.6 worked without any problem. (Microsoft Windows 10 PRO (10.0.17134))

edit retag flag offensive close merge delete


Can you paste the contents of the Help | About Wireshark | Wireshark dialog box?

grahamb gravatar imagegrahamb ( 2018-05-17 09:17:16 +0000 )edit

In fact, I can't. Wireshark closes itself after less than 5 seconds. Can I add somewhere a screenshot?

Tom Cordemans gravatar imageTom Cordemans ( 2018-05-17 10:51:23 +0000 )edit

Maybe use tshark from a command prompt then:

"path\to\tshark.exe" -v

Where path\to is the appropriate path to your install of Wireshark, likely to be "C:\Program Files\Wireshark", or "C:\Program Files (x86)\Wireshark", and if it includes spaces will have to be quoted as in the example.

grahamb gravatar imagegrahamb ( 2018-05-17 11:35:18 +0000 )edit

tshark output:

C:\Program Files\Wireshark>tshark.exe -v
TShark (Wireshark) 2.6.0 (v2.6.0-0-gc7239f02)

Copyright 1998-2018 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later <>
This is free software; see the source for copying conditions. There is NO

Compiled (64-bit) with WinPcap (4_1_3), with GLib 2.42.0, with zlib 1.2.11, with
SMI 0.4.8, with c-ares 1.14.0, with Lua 5.2.4, with GnuTLS 3.4.11, with Gcrypt
1.7.6, with MIT Kerberos, with MaxMind DB resolver, with nghttp2 1.14.0, with
LZ4, with Snappy, with libxml2 2.9.4.

Running on 64-bit Windows 10, build 17134, with Intel(R) Core(TM) i7-5600U CPU @
2.60GHz (with SSE4.2), with 16275 MB of ...
Tom Cordemans gravatar imageTom Cordemans ( 2018-05-17 13:14:29 +0000 )edit

OK, that shows that npcap has been found and is being used. Something is up with the interfaces on your machine that prevents the initial scan of interfaces succeeding.

Can you open a PowerShell prompt and show the output of Get-NetAdaptor?

grahamb gravatar imagegrahamb ( 2018-05-17 13:21:07 +0000 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2018-05-16 21:20:42 +0000

Jaap gravatar image

Install npcap with Wireshark instead.

edit flag offensive delete link more


Used method: 1) I removed the WinPcaP driver and Wireshark. 2) I installed Npcap 0.99-r5 3) I installed Wireshark 2.6

Unfortunately same result!

Tom Cordemans gravatar imageTom Cordemans ( 2018-05-17 06:01:39 +0000 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools


Asked: 2018-05-16 18:42:34 +0000

Seen: 773 times

Last updated: May 16 '18