Comment # 2
on bug 12712
from Gerald Combs
(In reply to Brendan Batchelder from comment #1)
> Looks like this might be a bug with the redistributable from Microsoft.
>
> https://support.microsoft.com/en-us/kb/3138367
Thanks! I think you've found the missing piece of the puzzle.
This has been reported in several places, so I'll try to summarize the issue
here.
We follow the "Central deployment by using redistributable packages" guideline
described at https://msdn.microsoft.com/en-us/library/ms235316(v=vs.120).aspx.
Specifically, we build Wireshark using Visual C++ and include the most recent
version of vcredist_x64.exe and vcredist_x86.exe with our respective 64-bit and
32-bit Windows installers and run them at installation time. We've been doing
this since 2007 without any major issues until now.
We currently build Wireshark with Visual C++ 2013 Update 5. It includes version
12.0.30501.0 of the redistributables. These are also the versions available on
the "Visual C++ Redistributable Packages for Visual Studio 2013" download page
at https://www.microsoft.com/en-us/download/details.aspx?id=40784
Name Version SHA1
vcredist_x64.exe 12.0.30501.0 8bf41ba9eef02d30635a10433817dbb6886da5a2
vcredist_x86.exe 12.0.30501.0 df7f0a73bfa077e483e51bfb97f5e2eceedfb6a3
Except these aren't really the most recent redistributables. As Brendan points
out, KB3138367 says
"When you install an updated redistributable package, binaries for non-target
architectures are removed. For example, after you install an update for an
x86-based application, the x64 Visual C++ 2013 runtime libraries are missing.
This fix makes sure that both versions of the Visual C++ redistributable are
visible when you add or remove programs after installation of the update."
and gives you the following English versions:
Name Version SHA1
vcredist_x64.exe 12.0.40649.5 c990b86c2f8064c53f1de8c0bffe2d1c463aaa88
vcredist_x86.exe 12.0.40649.5 a2889d057d63da00f2f8ab9c4ed1e127bdf5db68
I've pushed version 12.0.40649.5 of the redistributables to our build servers.
Hopefully this will fix the issue.
You are receiving this mail because:
- You are watching all bug changes.
