Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Auto-update should follow the installation path selected by the previous version #7580

Closed
NiceFeather opened this issue Nov 9, 2019 · 4 comments
Closed

Auto-update should follow the installation path selected by the previous version #7580

NiceFeather opened this issue Nov 9, 2019 · 4 comments
Assignees
@dschmidt
Labels
p2-high Escalation, on top of current planning, release blocker packaging regression type:bug
Milestone
2.6.1

Comments

@NiceFeather
Copy link

The program was automatically upgraded a few days ago, but I noticed the installation of the new version didn't follow the installation path selected by the previous version which is located at "E:\ownCloud", it automatically installed into the "C:\ Program Files (x86)" directory of the system, in fact that is actually a brand new installation. I think it should be improved in next installation pack.
@NiceFeather
Copy link
Author

and I noticed the auto-starting feature was not working anymore after auto-updating, because the installed program directory is different with the key value of Registry.

@HanaGemela HanaGemela added this to the 2.6.1 milestone Nov 14, 2019
@HanaGemela HanaGemela added type:bug p2-high Escalation, on top of current planning, release blocker labels Nov 14, 2019
@michaelstingl michaelstingl added the ReadyToTest QA, please validate the fix/enhancement label Dec 19, 2019
@HanaGemela HanaGemela mentioned this issue Jan 8, 2020
Closed
47 tasks
@HanaGemela
Copy link
Contributor

Auto-starting feature still broken in 2.6.1sprint2 (build 12916), Windows 10
Also broken for the first installation, not just for the update

@HanaGemela HanaGemela removed the ReadyToTest QA, please validate the fix/enhancement label Jan 9, 2020
@HanaGemela
Copy link
Contributor

@TheOneRing
When I remove the entry from Registry (Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run), new one is created and the auto start works.
When I change the location when installing new version, the Registry is not updated and auto start doesn't work

@HanaGemela
Copy link
Contributor

Auto start moved into a new issue #7672
Original bug is fixed in 2.6.1sprint2 (build 12916)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dschmidt dschmidt

Labels
p2-high Escalation, on top of current planning, release blocker packaging regression type:bug
Projects
None yet
Milestone
2.6.1
Development

No branches or pull requests
5 participants
@michaelstingl @dschmidt @ogoffart @NiceFeather @HanaGemela