Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 12943] New: No interfaces found after Windows 10 'Annivers

Date: Sat, 24 Sep 2016 08:40:21 +0000
Bug ID 12943
Summary No interfaces found after Windows 10 'Anniversary Update'
Product Wireshark
Version 2.2.0
Hardware x86
OS Windows 10
Status UNCONFIRMED
Severity Normal
Priority Low
Component Common utilities (libwsutil)
Assignee [email protected]
Reporter [email protected]

Build Information:
tshark -v
The NPF driver isn't running.  You may have trouble capturing or
listing interfaces.
TShark (Wireshark) 2.2.0 (v2.2.0-0-g5368c50 from master-2.2)

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 WinPcap (4_1_3), with GLib 2.42.0, with zlib 1.2.8, with
SMI 0.4.8, with c-ares 1.11.0, with Lua 5.2.4, with GnuTLS 3.2.15, with Gcrypt
1.6.2, with MIT Kerberos, with GeoIP.

Running on 64-bit Windows 10, build 14393, with locale English_United
States.1252, with Npcap version 0.09r13, based on libpcap version
1.9.0-PRE-GIT, with GnuTLS 3.2.15, with Gcrypt 1.6.2.
Intel(R) Core(TM) i7-4771 CPU @ 3.50GHz (with SSE4.2), with 32706MB of physical
memory.


Built using Microsoft Visual C++ 12.0 build 40629

--
I'm not sure if this is a Wireshark or Npcap issue, but after I updated Windows
10 Home (64-bit) to the 'Anniversary Update' (version 1607 [OS Build
14393.187]), Wireshark is no longer able to identify any interfaces. 'tshark'
is a bit more specific, and gives me this: "The NPF driver isn't running". When
I look at the services that are running and/or installed, I cannot find a
service called 'NPF'. (Not sure if it was there before, or if it is called
something different with npcap).

Im running Wireshark 2.2.0 and was running Npcap 0.09-r13 when I first ran into
the issue, but updated to the latest 0.10-r2 (installed in winpcap
compatibility mode) to see if that helped anything (it didn't).


You are receiving this mail because:
  • You are watching all bug changes.