Information on the forthcoming new installer
Hi,
I noticed in the release notes for the 6.3.360 beta, that this update is preparing the way for a new installer.
I'm just wondering if you could shed more light on this, as I'm interested in why this change is being made? :chuffed:
What benefits does the new installer bring - will it solve the problem of having to re-pin 1Password to the taskbar, when the app is updated?
Many thanks, Paul
1Password Version: 6.3.360
Extension Version: Not Provided
OS Version: Windows 10 Anniversary x64
Sync Type: Not Provided
Comments
-
@pbryanw new installer fixes a number of issues we have with the current:
- install at any folder
- update at the same folder where app was installed
- autostart 1Password after install
- install exactly the files we want to install, not the wrongly picked dependencies (infamous HTTP dll issue, when on some systems app simply crashed because of the wrongly picked dependency)
- have all files signed
Soon you will be able to see it for yourself. Also, I do believe it will help with the pinning issue ;)
0 -
@SergeyTheAgile - Thanks for your reply & for the extra information about the new installer (it certainly sounds like a considerable improvement over the current one) :+1: I'll keep a keen eye on my 1Password 6 beta, and look forward to trying the new installer for myself in the near future :+1:
0 -
On behalf of Serg, you're welcome.
0 -
Will the new installer let us install for a computer rather than a user? We use virtual desktops which get reimaged to deploy updates, we also do not allow users to install any software and forbid executables from running inside the C:\users* folders. We really need to preload 1Password on the gold/master image and deploy.
0 -
@scooter7057 yes, you can install in any folder. One note though, installer runs without elevated privileges by default, that will prevent installation to Program Files by default. Just run installer as administrator to install to Program Files. Keep in mind, app runs without elevation and it runs update without elevation too, you will have to run elevated updates manually. Which I believe your workflow anyway.
P.S. you may want to play with 1password.json to limit autoupdater checks on your images.
0
