Wireshark-bugs: [Wireshark-bugs] [Bug 6772] New: Wireshark fails to run on Win7 x64 if AirPcap N
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 26 Jan 2012 02:37:32 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6772

           Summary: Wireshark fails to run on Win7 x64 if AirPcap Nx is
                    inserted
           Product: Wireshark
           Version: 1.6.5
          Platform: x86-64
        OS/Version: Windows 7
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: krkos@xxxxxxxxxxxxxxxxx


Build Information:
Version 1.6.5 (SVN Rev 40429 from /trunk-1.6)

Copyright 1998-2012 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, without
SMI, 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 Jan
10 2012), with AirPcap.

Running on 64-bit Windows 7, build 7600, 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

--
Wireshark 1.6.5 fails to run on Windows 7 x64 if AirPcap Nx is inserted during
Wireshark startup, or it freezes / fails displaying window with (null)
description text if AirPcap Nx is inserted later.

Does not happen on Windows 7 32bit with 32bit Wireshark.

Wireshark requires registry keys:
HKLM\SOFTWARE\AirPcap (Read for user)
HKLM\SOFTWARE\AirPcap\GlobalKeyStore (Read, Write for user)

which are created (with these permissions) when Wireshark is ran with
Administrative privileges. Subsequent runs as unprivileged user are successful.

Workaround:
1. Run Wireshark with Administrative privileges for the first time;
2. Create mentioned registry keys with said permissions.

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