Skip to main content
November 24, 2025
Solved

Integration Status Connection Problem W11

  • November 24, 2025
  • 2 replies
  • 204 views

Hello,

I started encountering this issue out of nowhere a couple of days ago. I didn't actively update any of the software involved in this problem.

This was working fine before, and then all of a sudden it stopped, I'm getting the following error:

1Password is both running and unlocked.

I've tried reinstalling 1Password, installing the beta msix file, enabling and disabling the browser setting. I also restarted the computer between attempts. I also tried the beta browser extension
Nothing has worked so far to connect the app to the browser extension.

This is seemingly affecting all of my browsers (Vivaldi, Chrome).

I'm on Windows 11, with Windows Defender as the AV with default settings.

Any help to get the integration back working would be greatly appreciated.

Best answer by ninja0n3

After communicating with support, we managed to resolve the issue.

It seems like the chrome extension looks for the windows app to be installed in the C drive, and I had all my Windows App installs defaulted to my D drive.

I temporarily switched the install drive to C, uninstalled and reinstalled 1Password, switched the setting back to D, and now it seems to be working.

I've had this setting in place for a number of years now; and I can't be the only one with a setup like this (non default install drive). I feel like the extension shouldn't rely on a hardcoded location to determine the connectivity; at the very least having a setting to point to the right location would be workable.

I don't think this requirement is documented anywhere.

In any case, this issue is resolved for me.

2 replies

1P_Dave
1Password Employee
November 25, 2025

Hello @ninja0n3! 👋

I'm sorry that the integration between the 1Password app and 1Password in the browser aren't working properly. Did you recently move to the MSIX from the EXE version? 

As a first step, can you try the suggestions in this article: If the 1Password browser extension doesn’t unlock when you unlock the 1Password app

Let me know if that doesn't work and I can help further. 

-Dave

Issue=PA-878

ninja0n3Author
November 26, 2025

Did you recently move to the MSIX from the EXE version?

No, I've been running the MSIX version for a while; it just stopped working for me some reason on Friday.

As a first step, can you try the suggestions in this article: https://support.1password.com/connect-1password-browser-app/

I tried all of this as well as installing the beta, uninstalling, reinstalling, disabling the extension, installing the beta extension, rebooting, etc.

So far none of the solutions suggested online have worked for me.

1P_Dave
1Password Employee
November 26, 2025

@ninja0n3 

I'm sorry that none of the suggestions worked. I'd like to ask you to create and share a 1Password diagnostics report from 1Password in your browser:

Send a diagnostics report (browser extension)

Attach the diagnostics to an email message addressed to support@1password.com

With your email please include:

  • A link to this thread: https://www.1password.community/discussions/1password/integration-status-connection-problem-w11/164879
  • Your forum username: ninja0n3


You should receive an automated reply from our BitBot assistant with a Support ID number.  Please post that number here.  Thanks very much!

-Dave

ninja0n3AuthorAnswer
November 27, 2025

After communicating with support, we managed to resolve the issue.

It seems like the chrome extension looks for the windows app to be installed in the C drive, and I had all my Windows App installs defaulted to my D drive.

I temporarily switched the install drive to C, uninstalled and reinstalled 1Password, switched the setting back to D, and now it seems to be working.

I've had this setting in place for a number of years now; and I can't be the only one with a setup like this (non default install drive). I feel like the extension shouldn't rely on a hardcoded location to determine the connectivity; at the very least having a setting to point to the right location would be workable.

I don't think this requirement is documented anywhere.

In any case, this issue is resolved for me.

1P_Dave
1Password Employee
November 27, 2025

Thank you for sharing the solution with the community. Our support team, who you're working with over email, will make sure that your feedback gets to our development team. 

-Dave