THIS IS A TEST INSTANCE. Feel free to ask and answer questions, but take care to avoid triggering too many notifications.
Ask Your Question
0

How can I resolve the issue of not being able to see my computer interfaces?

Version 2.3.0-1855-gb3b23ff (v2.3.0rc0-1855-gb3b23ff)

Copyright 1998-2016 Gerald Combs [email protected] and contributors. License GPLv2+: GNU GPL version 2 or later http://www.gnu.org/licenses/old-licenses/gpl-2.0.html This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with Qt 5.6.1, with WinPcap (413), with GLib 2.42.0, with zlib 1.2.8, with SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS 3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with nghttp2 1.14.0, with LZ4, with Snappy, with QtMultimedia, with AirPcap, with SBC, with SpanDSP.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz (with SSE4.2), with 8072 MB of physical memory, with locale English_United States.1252, without WinPcap, with GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.

Built using Microsoft Visual C++ 12.0 build 40629

gmchat's avatar
1
gmchat
asked 2018-03-20 17:37:55 +0000
grahamb's avatar
23.8k
grahamb
updated 2018-03-24 20:21:32 +0000
edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

2 Answers

0

I've had this issue for over a year now with previous versions of Wireshark on Windows 10. I've tried about everything I could find on the internet, installing the 32 bit version, installing npcap instead of winpcap, but nothing worked to restore the list of interfaces when I ran wireshark.

After updating to version 2.4.5 recently, now voila, all the interfaces have returned or reappeared in the interface options window so I can capture once again from Windows 10. I am hoping that another update doesn't cause the issue again as i never did find a solution for this previously.

lpaz's avatar
1
lpaz
answered 2018-04-02 15:42:48 +0000
edit flag offensive 0 remove flag delete link
more

Comments

add a comment see more comments
0

Your version of Wireshark hasn't been able to locate a capture library:

Running on 64-bit Windows 7 Service Pack 1, build 7601, with Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz (with SSE4.2), with 8072 MB of physical memory, with locale English_United States.1252, without WinPcap, with GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.

Installing WinPcap should fix that.

You are also running a somewhat old development version (2.3.0), please upgrade to the current stable version 2.4.5.

grahamb's avatar
23.8k
grahamb
answered 2018-03-20 18:19:50 +0000
edit flag offensive 0 remove flag delete link
more

Comments

add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer