First time here? Check out the FAQ!
THIS IS A TEST INSTANCE. Feel free to ask and answer questions, but take care to avoid triggering too many notifications.
0

When I open WireShark, I got this error: Can't get list of interfaces: PacketGetAdapterNames: The system cannot find the path specified. (3)

When I open WireShark, I get this error: Can't get list of interfaces: PacketGetAdapterNames: The system cannot find the path specified. (3)

I am running wireshark as administrator.

Below is the Help-> About -> WireShark dialog box:

3.6.0 (v3.6.0-0-g3a34e44d02c9)

Compiled (64-bit) using Microsoft Visual Studio 2019 (VC++ 14.29, build 30040), with Qt 5.15.2, with libpcap, with GLib 2.66.4, with zlib 1.2.11, with Lua 5.2.4, with GnuTLS 3.6.3 and PKCS #11 support, with Gcrypt 1.8.3, with MIT Kerberos, with MaxMind DB resolver, with nghttp2 1.44.0, with brotli, with LZ4, with Zstandard, with Snappy, with libxml2 2.9.10, with libsmi 0.4.8, with QtMultimedia, with automatic updates using WinSparkle 0.5.7, with AirPcap, with SpeexDSP (using bundled resampler), with Minizip.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz (with SSE4.2), with 8103 MB of physical memory, with GLib 2.66.4, with Qt 5.15.2, with Npcap version 1.55, based on libpcap version 1.10.2-PRE-GIT, with c-ares 1.17.0, with GnuTLS 3.6.3, with Gcrypt 1.8.3, with nghttp2 1.44.0, with brotli 1.0.9, with LZ4 1.9.3, with Zstandard 1.4.0, without AirPcap, with light display mode, without HiDPI, with LC_TYPE=C, binary plugins supported (21 loaded).

Thanks for your assistance!

kdbennett63's avatar
1
kdbennett63
asked 2021-12-22 10:50:30 +0000
Guy Harris's avatar
19.9k
Guy Harris
updated 2021-12-24 11:14:13 +0000
edit flag offensive 0 remove flag close merge delete

Comments

Thou shall not start Wireshark as administrator.

hugo.vanderkooij's avatar hugo.vanderkooij (2021-12-22 15:31:30 +0000) edit

It displays the same error when I run it as not an administrator.

kdbennett63's avatar kdbennett63 (2021-12-22 17:35:25 +0000) edit

But it doesn't have as many security risks when you run it not as administrator.

Guy Harris's avatar Guy Harris (2021-12-24 11:13:06 +0000) edit
add a comment see more comments

2 Answers

0

NPCAP people say there's a bug in version v1.5 and v1.55 relating to Windows 7. They recommended going to v1.6. I have an old Win7 machine that had this happen to it after I installed the latest Wireshark release with NPCAP 1.5 incorporated. After the install Wireshark said it could not see the interfaces. I downloaded v1.6 and installed it over the top of what I had and rebooted. And, just like that, I have interfaces again!

I filed this on their board site "[nmap/npcap] wireshark Can't get list of interfaces: PacketGetAdapterNames: The system cannot find the path specified. (3) (Issue #575)"

They returned this: "This is a known issue with Npcap 1.50 and 1.55 on Windows 7 that is fixed in Npcap 1.60. The issue is #536".

dribniff's avatar
1
dribniff
answered 2022-01-20 02:17:52 +0000
edit flag offensive 0 remove flag delete link

Comments

add a comment see more comments
0

This is an Npcap issue; you should report it on the Npcap issues page.

Guy Harris's avatar
19.9k
Guy Harris
answered 2021-12-24 11:22:57 +0000
edit flag offensive 0 remove flag delete link

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