Question

Support additional browsers outside of 'Program Files' on Windows

Forum|Forum|7 months ago
November 21, 2025
5 replies
426 views

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).

T

TheJohn19Author

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.

1P_Dave

1Password Employee

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

P

preetgill

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

1Password Employee

@preetgill

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

J

jborch10

+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

1Password Employee

@jborch10

Welcome to the community! This thread is discussing a new feature for 1Password for Windows, called additional trusted browsers, where you can add unsupported browsers to the 1Password desktop app in order to allow the desktop app to communicate with 1Password in that browser.

Microsoft Edge is already a supported browser and you don't need to add it as a trusted browser. It should work fine when installed in C:/Program Files(x86). Are you seeing issues when using 1Password in Microsoft Edge? Can you tell me more about the issues that you're seeing?

-Dave

C

cp1000

+1 on this

I use scoop to install software on windows. Can confirm that the 1Password gui client (8.11.23) doesn't accept "$HOME\scoop\apps\zen-browser\current\zen.exe".

I tried using a junction to map "C:\program files\zen" into the app folder, and a lone hardlink to the exe, as possible workarounds - no joy

edit: also tried using a junction with the latest beta 1Password GUI 8.12.0-14 (81200014) - no joy

C

cp1000

+1 for allowing install locations outside of 'C:\program files'. I primarily use scoop to install applications (C:\users\<user>\scoop\apps\zen-browser\current).

An additional +1 if I could do a portable install of 1Password as well - right now, the BrowserSupport binary can't find the desktop app if they're extracted from the installer into a non-standard place

Sign up

1Password employees: Sign in with SSO

Login to the community

1Password employees: Sign in with SSO

Scanning file for viruses.

This file cannot be downloaded