Updating ignores previous install and creates duplicate entry in "Programs and Features"

Backspaze

I had version 6.0.206 installed and clicked the update banner to install 6.0.214. Now I have two separate installs of the app.

I suspect this has to do with the fact that I switched install folder to C:\Program Files\1Password 6\ when I installed the .206 version, and that the update ignores that and installs into the default folder under C:\Users...

I assume that in future versions it will check where the app is installed and apply the update to the correct location?

---

1Password Version: 6.0.214
Extension Version: 4.5.9
OS Version: Windows 10
Sync Type: Families

AGAlumB

@Backspaze: I'm pretty sure this isn't anything you've done. That's expected. We had to make substantial changes under the hood these last few weeks and that resulted in the "new" 1Password 6 app you're seeing. Once you're all up and running in the new app, you can uninstall the old one. Part of the reason we've done all of this is to avoid making you jump through so many hoops in the future. Thanks for bearing with us, and participating in the beta! :)

Backspaze

Which version do you consider marked the start of this "new" 1Password 6 app? And shouldn't the app respect the users choice of installation folder (why have the option otherwise?) or are there any specific reasons and/or benefits to have the app install to the User folder?

I did a complete uninstall and reinstall when my 6.0.186 install stopped receiving updates (even though the download page showed that a couple of updates had been released after it) and installed 6.0.199 which, if I remember correctly, had the new default installation folder configured, and got bumped up to 6.0.204 during the installation process. So if .199 (or .204) was part of the "new" app I should already have fresh install of it in my folder of choice: C:\Program Files\1Password 6\, yet the updates ignore that and installs a duplicate in the Users folder.

AGAlumB

@Backspaze: Indeed, especially on multi-user systems (or virtualized environments), it's important to have a separate installation of the app for each user account (so that you don't have to quit it and logout completely for another user to access 1Password). So while previously the app installed for "everyone" by default, it is now per user account. And this also goes for browser integration. This change came with the database reset in build 197.

And you're absolutely right that the user-defined installation settings should carry over. That's why we wanted to get this setup during the beta, prior to the stable release. After all, beta testers know that they're signing up for what can be a bumpy ride at times, whereas a stable release needs to make as few major changes like this as possible. And since we migrated to a new database setup, the new installation uses a separate database. That way if anything went wrong, the previous version was still intact to fall back on. I'm sorry for the confusion that this has caused! Our goal with this change was to get it out of the way so it isn't necessary in the future. Thanks for your understanding!

MikeT

Hi @Backspaze,

We're finding out all sorts of issues with the MSI installer we're using and we've decided to embark on a side project to develop a custom installer to address all of these issues. Right now, the installer does not pay attention to the previous path that the user has chosen, doesn't handle shortcuts well on the desktop, doesn't gracefully handle various .NET versions and many more.

We've changed to the %LOCALAPPDATA%\1Password path because it kills the need to have a UAC prompt, which also means it could be used by standard users without admin rights. Unfortunately, the installer itself still needs admin rights, even though we don't want it.

We're doing what we can to minimize these issues with the current installer but we will ship a new installer in the near future once we can confirm it can handle everything we need.