Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Support additional browsers outside of 'Program Files' on Windows
I've just installed the latest nightly version of 1Password, which finally introduced the 'Connect to additional browsers' feature on Windows. I wanted to try it out right away, but sadly Chromium (forks) usually install under AppData at user level. This shouldn't be a problem, since 1Password supports other Chromium browsers, such as Comet, which install under AppData. However, if you try to pick a browser outside of 'Program Files', you get this error:
I'm sure there's a security reason behind this, but please let me decide what I see as secure on my system. So far, the only way I've managed to install a Chromium (fork) browser in the 'Program Files' folder was to use Winget with the '--scope machine' argument. However, smaller browsers often aren't really up-to-date on Winget (or aren't available at all) but I guess that's what 1Password wants me to use then, an outdated winget version of such browser...
At least allow browsers installed under AppData/local, so that this feature will actually be useable for most people (many non techsavvy people aren't even aware of Winget).
5 Replies
+1 for TheJon19. Our admin install most apps into C:\Program Files (x86) , for example Edge. With the current restriction, plugin communication don't work for us.
- 1P_Dave
Moderator
Hello TheJohn19! 👋
We are indeed actively testing the additional browsers feature in the nightly build of the 1Password for Windows app. This has been one of our most requested enhancements, and it's now available for early testing by those using the nightly channel. Just a heads-up: the nightly channel isn’t tested as rigorously as the beta or production channels. If you’d rather steer clear of unexpected bugs or quirks, it might be best to wait until this feature reaches the more stable channels.
In this initial release, which was built specifically for Windows, supported browsers must be admin-installed in the Program Files directory. This requirement is in place for security reasons. However, our team is looking into expanding support to include code-signed browsers installed elsewhere, as well as refining the security checks this feature currently performs to ensure the right balance between safety and flexibility.
For everyone testing this feature, let us know how it works for you and your preferred browser!
-Dave
Hello 1P_Dave the feature on nightly build works exactly as expected on my zen browser. Kudos to the team for finally bringing this much awaited feature on windows.
I just want to know if you have an estimated timeline to roll out this feature to beta and then to prod? tentative timeline would really help..- 1P_Dave
Thank you for helping us to test the new feature in the nightly version! If testing continues to go well in the nightly then we hope to release the feature to the beta soon. I don't have any specific timelines to share at the moment.
-Dave
Having looked into this further, I noticed that even if you change the default drive for new apps in Windows 11, which creates a new Program Files and WindowsApps folder on the new drive with the same (!) security parameters as on the C:\ drive, 1Password still refuses to connect to any app within that folder. It can only be in Program Files (not even Program Files x86) and only on the C:\ drive.
While I understand why you might limit this to 'Program Files' for security reasons (though, again, this decision essentially prevents most Chromium forks to work with this unless you start 'tinkering'), you should at least allow it (and 'WindowsApps'), no matter which drive it is on.
