Comment # 3
on bug 12990
from Alan Adams
(In reply to Guy Harris from comment #1)
> It is, however, Windows-specific.
Agreed.
(In reply to Alexis La Goutte from comment #2)
> It is strange because work before... (need to retry with last 2.2.x) you
> don't use msi packages ?
When I have downloaded the installation set "manually" for use on upgrading
multiple machines, I download the .EXE installer. (I don't even see where
there is an .MSI installer option? Not even decompressing the .EXE shows me an
.MSI, so maybe I'm missing the point of what the .MSI question is.)
More typically though, I'm just using the upgrade offer or upgrade option that
Wireshark itself offers. So the installer I'm using is "whatever Wireshark
chose to download", and I have no idea that it's specifically .EXE or .MSI.
I don't recall a time when this behavior worked, but it very well might have
worked in the past. I tested just now on a clean Windows 7 Pro SP1 x64 US
English machine and installed "Wireshark-win64-1.10.0.exe" as the initial
version. During installation I changed the selection to NOT create a Quick
Launch icon and to DO create a Desktop Icon.
After successful installation of Wireshark and WinPCAP I rebooted, and then ran
the "Wireshark-win64-1.10.1.exe" to upgrade. The uninstall of 1.10.0 prompted
to "Default (keep personal settings)", which is what I let it do. During the
subsequent 1.10.1 install, the icon offer did not remember my previous
selections, and I had to again de-select Quick Launch icon and select Desktop
icon.
So the issue is there at least as far back as 1.10.1, and happens to pre-date
the integration of the "Wireshark v2 vs. Wireshark Legacy"-related concurrent
installation and icon options.
You are receiving this mail because:
- You are watching all bug changes.