Opened on Dec 8, 2016 at 11:10:12 PM
Closed on Jun 23, 2017 at 1:06:32 PM
Last modified on Oct 21, 2018 at 2:51:02 PM
#9782 closed defect (fixed)
Auto-updater ignores custom installation locations on Windows
Reported by: | Hackintosh HD | Owned by: | dkocher |
---|---|---|---|
Priority: | normal | Milestone: | 6.1.0 |
Component: | installer | Version: | 5.2.2 |
Severity: | normal | Keywords: | Auto-Updater |
Cc: | Architecture: | Intel | |
Platform: | Windows 7 |
Description (last modified by Hackintosh HD)
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.
Change History (11)
comment:1 Changed on Dec 8, 2016 at 11:10:54 PM by Hackintosh HD
- Summary changed from Cyberduck Auto-Updater ignores custom installation locations on Windows to Cyberduck auto-updater ignores custom installation locations on Windows
comment:2 Changed on Dec 8, 2016 at 11:24:13 PM by Hackintosh HD
- Description modified (diff)
comment:3 Changed on Dec 9, 2016 at 10:13:40 AM by dkocher
- Milestone set to 6.0
- Owner set to dkocher
- Status changed from new to assigned
- Summary changed from Cyberduck auto-updater ignores custom installation locations on Windows to Auto-updater ignores custom installation locations on Windows
comment:4 Changed on Dec 15, 2016 at 1:03:05 PM by dkocher
comment:5 Changed on Jan 11, 2017 at 8:33:37 AM by dkocher
- Milestone changed from 6.0 to 5.3
Milestone renamed
comment:6 Changed on Jan 11, 2017 at 3:32:21 PM by dkocher
- Milestone changed from 5.3 to 6.0
Ticket retargeted after milestone closed
comment:7 Changed on Feb 1, 2017 at 9:24:06 AM by dkocher
- Owner changed from dkocher to yla
- Status changed from assigned to new
comment:8 Changed on May 5, 2017 at 1:45:11 PM by dkocher
- Milestone changed from 6.0 to 7.0
Ticket retargeted after milestone closed
comment:9 Changed on Jun 23, 2017 at 8:24:16 AM by dkocher
- Milestone changed from 7.0 to 6.1
- Owner changed from yla to dkocher
- Status changed from new to assigned
comment:10 Changed on Jun 23, 2017 at 1:06:32 PM by dkocher
- Resolution set to fixed
- Status changed from assigned to closed
In r41524.
comment:11 Changed on Oct 21, 2018 at 2:51:02 PM by dkocher
- Milestone changed from 6.1 to 6.1.0
Milestone renamed
Similiar report for the Cyberduck CLI installer