Wireshark-bugs: [Wireshark-bugs] [Bug 12789] New: Installer damages existing VS2013 redistributa
Date: Thu, 25 Aug 2016 20:40:23 +0000
Bug ID 12789
Summary Installer damages existing VS2013 redistributables installation
Product Wireshark
Version 2.0.5
Hardware x86-64
OS Windows Server 2008 R2
Status UNCONFIRMED
Severity Normal
Priority Low
Component Build process
Assignee bugzilla-admin@wireshark.org
Reporter zsdtumybfu@snkmail.com

Build Information:
Version 2.0.5 (v2.0.5-0-ga3be9c6 from master-2.0)

Copyright 1998-2016 Gerald Combs <gerald@wireshark.org> 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.3.2, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.11.0, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.

Running on 64-bit Windows Server 2008R2 Service Pack 1, build 7601, with
locale
English_United States.1252, with WinPcap version 4.1.3 (packet.dll version
4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008), with
GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz (with SSE4.2), with 8179MB of
physical memory.


Built using Microsoft Visual C++ 12.0 build 40629
--
I ran Wireshark-win64-2.0.5.exe on a WS2008R2 server that had never had
Wireshark installed before. Both WinPcap and Wireshark were installed. After
the installer had completed, a 32-bit program on that server that depends on
MSVCP120.DLL would no longer start. Windows error was that MSVCP120.DLL could
not be found. I ran the redistributables installer (vc2013redist_x86.exe) again
and afterward the the program was again able to start and run. Wireshark
started and ran fine before and after the redistributables reinstall.

The Component list doesn't offer an obvious choice for reporting installer
problems, but I chose Build process because the description mentions NSIS.


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