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 6085] New: Can't capture on Windows 7 Professional 64-bit;

Date: Fri, 1 Jul 2011 21:39:49 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6085

           Summary: Can't capture on Windows 7 Professional 64-bit; no
                    interfaces available
           Product: Wireshark
           Version: 1.7.x (Experimental)
          Platform: x86-64
        OS/Version: Windows 7
            Status: NEW
          Severity: Major
          Priority: Medium
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: Jim@xxxxxxxxxxxxxxxxx


Build Information:
Version 1.7.0-SVN-37862 (SVN Rev 37862 from /trunk)

Copyright 1998-2011 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
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 GTK+ 2.22.1, with GLib 2.26.1, with WinPcap (version
unknown), with libz 1.2.5, without POSIX capabilities, without libpcre, with
SMI
0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.10.3,
with
Gcrypt 1.4.6, without Kerberos, with GeoIP, with PortAudio V19-devel (built Jul 
1 2011), with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.10.3, Gcrypt 1.4.6, with AirPcap 4.1.1 build
1838.

Built using Microsoft Visual C++ 9.0 build 21022
--
I installed Wireshark 1.7.0-SVN-37862 and ran Wireshark. A pop-up dialog box
showed the following message: “Unknown message from dumpcap, try to show it as
a string: Unable to open debug log file !” After clicking "OK" to close the
dialog, I saw that no interfaces were listed and this legend was displayed: “No
interface can be used for capturing in this system with the current
configuration”

Running "tshark -D" from the command line gave the same message: “Unknown
message from dumpcap, try to show it as a string: Unable to open debug log file
!”

Running "dumpcap -D" from the command line showed "Unable to open debug log
file !"

The same behavior was seen on 1.7.0-SVN-37850 64-bit and 1.7.0-SVN-37849
64-bit.

The 32-bit versions generate the same error message (on 64-bit Windows 7), but
the error is shown in a console window instead of a dialog box, and the GUI
never launches.

Reverting to stable version 1.6.0 or development version 1.7.0-SVN-37835
restores full functionality.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.