[Cyberduck-trac] [Cyberduck] #9782: Cyberduck auto-updater ignores custom installation locations on Windows

[Cyberduck]

#9782: Cyberduck auto-updater ignores custom installation locations on Windows
---------------------------+----------------------
 Reporter:  Hackintosh HD  |         Owner:
     Type:  defect         |        Status:  new
 Priority:  normal         |     Milestone:
Component:  installer      |       Version:  5.2.2
 Severity:  normal         |    Resolution:
 Keywords:  Auto-Updater   |  Architecture:  Intel
 Platform:  Windows 7      |
---------------------------+----------------------
Description changed by Hackintosh HD:

Old description:

> '''Details'''
>
> The Cyberduck Windows installer accepts custom installation locations:
> Providing an installation path like e.g. ''D:\Program Files
> (x86)\iterate\Cyberduck'' within the installer's GUI is definitely
> possible.
>
> Once Cyberduck is installed, however, and a new version number gets
> available through the auto-updater, the '''auto-update feature
> ''ignores'' custom installation locations''' and updates any Cyberduck
> installation to %ProgramFiles(x86)%\Cyberduck, no matter which
> installation path was initially chosen on setup. In the end, this results
> in ''two'' Cyberduck instances on the very same machine:
>
> * The remaining old version in the custom installation path provided in
> the initial setup,
> * The new up-to-date version in ''%ProgramFiles(x86)%\Cyberduck''.
>
> '''Reproducibility'''
>
> * Install any Cyberduck version for Windows prior to the current 5.2.3
> (21496) and provide a custom installation location on this initial setup,
> e.g. ''C:\Program Files (x86)\iterate\Cyberduck''.
> * Once this older Cyberduck version for Windows is installed, start it
> and choose '''Help → Check for Update…'''.
> * When the update to the current Cyberduck version is detected, install
> it: No matter which installation location you provided in step 1, the up-
> to-date Cyberduck version just installed by the auto-update will reside
> in ''%ProgramFiles(x86)%\Cyberduck''.
>
> '''See also'''
>
> As of version 1.6.3 (5079), the '''Mountain Duck''' auto-updater shows
> the very same behaviour.

New description:

 '''Details'''

 The Cyberduck Windows installer accepts custom installation locations:
 Providing an installation path like e.g. ''D:\Program Files
 (x86)\iterate\Cyberduck'' within the installer's GUI is definitely
 possible.

 Once Cyberduck is installed, however, and a new version number gets
 available through the auto-updater, the '''auto-update feature ''ignores''
 custom installation locations''' and updates any Cyberduck installation to
 ''%ProgramFiles(x86)%\Cyberduck'', no matter which installation path was
 initially chosen on setup. In the end, this results in ''two'' Cyberduck
 instances on the very same machine:

 * The remaining old version in the custom installation path provided in
 the initial setup,
 * The new up-to-date version in ''%ProgramFiles(x86)%\Cyberduck''.

 '''Reproducibility'''

 * Install any Cyberduck version for Windows prior to the current 5.2.3
 (21496) and provide a custom installation location on this initial setup,
 e.g. ''C:\Program Files (x86)\iterate\Cyberduck''.
 * Once this older Cyberduck version for Windows is installed, start it and
 choose '''Help → Check for Update…'''.
 * When the update to the current Cyberduck version is detected, install
 it: No matter which installation location you provided in step 1, the up-
 to-date Cyberduck version just installed by the auto-update will reside in
 ''%ProgramFiles(x86)%\Cyberduck''.

 '''See also'''

 As of version 1.6.3 (5079), the '''Mountain Duck''' auto-updater shows the
 very same behaviour.

--

--
Ticket URL: <https://trac.cyberduck.io/ticket/9782#comment:2>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows