Forum Discussion

1P_justin's avatar
1P_justin
Icon for 1Password Team rank1Password Team
8 months ago
Solved

Beta 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...
betas
discussion
windows
  • kasiditi's avatar
    kasiditi
    23 days ago

    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.

1Passworder1's avatar
1Passworder1
New Contributor
2 months ago

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. 

1P_justin's avatar
1P_justin
Icon for 1Password Team rank1Password Team
2 months ago

1Passworder1​ Thanks for all the info. Let's try to figure out the first issue first regarding the installation location as there could be a relation to the browser extension integration issue.

What was the original issue you ran into with the MSIX from the Microsoft Store that caused you to download and install from our website instead? From your previous post, it seems like the browser extension issue was present with that version as well. As far as Nightly/Beta goes, the Microsoft Store version only supports the Stable channel due to the Microsoft Store's update policies.

I believe the setting that you mentioned (Windows Settings > System > Storage > Where new content is saved > New apps will save to > D drive) only applies to applications downloaded from the Microsoft Store. In order to move MSIX installations from outside the Store, it is a little more involved requiring PowerShell. Here's a Microsoft article that has more information. If you haven't yet, I would raise a support ticket so that we can provide more direct help.

  • 1Passworder1's avatar
    1Passworder1
    New Contributor
    2 months ago

    First I had installed from MS Store. It wasn't being discovered by the browser extension. So I thought maybe the issue is fixed in beta version. So I uninstalled the MS Store version and installed the beta from 1P website. Unfortunately it too has the same issue. 

    I even tried powershell command methods - 

    PS C:\WINDOWS\system32>  Get-AppxVolume                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              
Name                                             PackageStorePath             IsOffline IsSystemVolume
----                                             ----------------             --------- --------------
\\?\Volume{Long Alpha-numeric} C:\Program Files\WindowsApps     False           True
\\?\Volume{Long Alpha-numeric} D:\WindowsApps                   False          False

    Tried moving the existing installation to D: 

    Move-AppxPackage -Package "Agilebits.1Password_8.11.14.20_x64__amwd9z03whsfe" -Volume "D:\"

    It still shows installation path as C: 

    Uninstalled and reinstalled with this - 

    Set-AppxDefaultVolume -Volume "D:\"
$D_Volume = Get-AppxVolume | Where-Object { $_.PackageStorePath -like "D:\*" }
Add-AppxPackage -Path "D:\OneDrive\Legion\Downloads\1PasswordSetup-latest.BETA.msixbundle" -Volume $D_Volume

    Still the same. Weird thing is, when I go to Windows Settings -> Apps and click the "Move" option for 1Password, it says "This app is currently installed on D:

    I'll create a support ticket, as you suggested.

    • 1P_Dave's avatar
      1P_Dave
      Icon for Moderator rankModerator
      2 months ago

      Thank you! Please continue the conversation with our support team via email. 

      -Dave