Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
1P_justin
1Password Team
1Password TeamBeta Release: New MSIX Installer for 1Password for Windows
Hello 1Password Community!
We are excited to announce the beta launch of the MSIX installer for 1Password for Windows. The MSIX installer combines the benefits of our existing EXE and MSI installer...
Not sure what's the current state of this issue, but I just stumbled upon this exact issue. I wasn't able to get the Chrome extension to connect to the app as well as using the recently announced Passkey feature for Windows.
I got similar logs to the ones above, which reminded me that I recently moved (possibly by uninstalling and reinstalling) the app from drive C: to D:. I tried moving the app back to drive C:, and this issue magically disappeared.
In case if you still need any help, I'm happy to provide additional debugging information. Please let me know.
I installed 1Password from https://apps.microsoft.com/detail/9nzws5x28p0j yesterday, and that was having issues. So I uninstalled that and installed via msix from https://1password.com/downloads/windows. But the issues are continuing.
💻 System Setup
- Windows 11 Pro x64, 25H2 (26200.6725)
- 1Password installed via MSIX bundle (v8.11.14.20 BETA)
- Browser Extension: 8.11.12.27 in Chrome, Edge
- Windows Settings -> System -> Storage -> Where new content is saved -> New apps will save to > D drive
🪳 Problems
- Even though I have my system set to install to D: drive, the msix is installing 1P to C: drive.
- After installation and login into the app, when I go to the browser extension, it can't connect to the desktop app and throws this error -
- I've uninstalled both browser extensions and the msix app and re-installed them fresh. Same connection issue continues.
- 1P Settings > Autofill > Passkeys option is greyed out.
And 1P doesn't show up in Windows Settings -> Accounts -> Passkeys -> Advanced options.
📄 Logs
(Editor not letting me enter the code)
❓Questions
- Is there a supported way to reinstall the MSIX bundle to a specific drive (e.g., D:) and ensure all components follow that path?
- Is this IPC path mismatch a known issue with MSIX installs across multiple drives?
- Can the browser stub be forced to launch from the same drive as the desktop app?
Would love any insight from the team or other users who’ve dealt with this.
Thanks in advance!
p.s. Before trying out these MSIX versions, I had the exe version installed for months and that was working fine with the browser extension.
Not sure what's the current state of this issue, but I just stumbled upon this exact issue. I wasn't able to get the Chrome extension to connect to the app as well as using the recently announced Passkey feature for Windows.
I got similar logs to the ones above, which reminded me that I recently moved (possibly by uninstalling and reinstalling) the app from drive C: to D:. I tried moving the app back to drive C:, and this issue magically disappeared.
In case if you still need any help, I'm happy to provide additional debugging information. Please let me know.
This really helped me a lot.
After I updated to the lastest MSIX version of 1Password today, I found that the browser extension could not connect to the app no matter what I tried, whether reinstalling or rebooting.
It was only when I followed your instructions and checked that I discovered I had changed the default Windows installation location for new apps to drive D.
After moving 1Password back to drive C, the problem disappeared and everything worked normally.
