Forum Discussion

1P_justin's avatar
1P_justin
Icon for 1Password Team rank1Password Team
6 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
1Passworder1's avatar
1Passworder1
New Contributor
4 days 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
    3 days 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
      3 days 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.

  • 1Passworder1's avatar
    1Passworder1
    New Contributor
    4 days ago

    Logs

    INFO  2025-10-07T23:23:16.848 👍 Finished initializing 1Password
INFO  2025-10-07T23:34:18.239 💫 Looking for desktop app com.1password.1password7
INFO  2025-10-07T23:34:18.239 📤 Sending <NmRequestAccounts> message to native core <some-number>
INFO  2025-10-07T23:34:18.240 Desktop app port disconnected. Error: Specified native messaging host not found.
    ERROR 2025-10-08T01:13:31.984+00:00 main(ThreadId(1)) [1P:foundation\\op-startup\\src\\windows.rs:432] Installer=Unknown (UnknownInstallerType)
ERROR 2025-10-08T01:13:31.996+00:00 main(ThreadId(1)) [1P:foundation\\op-startup\\src\\windows.rs:90] Error HRESULT(0x00000000): The operation completed successfully.
INFO  2025-10-08T01:13:32.000+00:00 main(ThreadId(1)) [1P:native-messaging\\op-browser-support\\src\\main.rs:269] Starting 1Password-BrowserSupport 8.11.14-20.BETA production build no. 81114020.
INFO  2025-10-08T01:13:32.008+00:00 main(ThreadId(1)) [1P:native-messaging\\op-browser-support\\src\\browser_verification\\windows.rs:62] Verifying browser \"C:\\Windows\\System32\\cmd.exe\"
ERROR 2025-10-08T01:13:32.018+00:00 main(ThreadId(1)) [1P:native-messaging\\op-browser-support\\src\\browser_verification\\windows.rs:71] WinApi(Error HRESULT(0x80092009): Cannot find the requested object.)
INFO  2025-10-08T01:13:32.020+00:00 main(ThreadId(1)) [1P:native-messaging\\op-browser-support\\src\\browser_verification\\windows.rs:81] name: cmd, publisher: Unknown Publisher, pid: 6796, version: 10.0.26100.6725
WARN  2025-10-08T01:13:32.033+00:00 main(ThreadId(1)) [1P:native-messaging\\op-browser-support\\src\\browser_verification\\windows.rs:50] Failed to verify process parent. ParentVerificationFail(WinApi(Error HRESULT(0x800B0100): No signature was present in the subject.))
INFO  2025-10-08T01:13:32.041+00:00 main(ThreadId(1)) [1P:native-messaging\\op-browser-support\\src\\browser_verification\\windows.rs:62] Verifying browser \"C:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe\"
INFO  2025-10-08T01:13:32.055+00:00 main(ThreadId(1)) [1P:native-messaging\\op-browser-support\\src\\browser_verification\\windows.rs:81] name: msedge, publisher: Microsoft Corporation, pid: 25780, version: 141.0.3537.57
INFO  2025-10-08T01:13:32.107+00:00 main(ThreadId(1)) [1P:native-messaging\\op-browser-support-lib\\src\\communication_logic.rs:153] Starting SLS communication (attempting connection to desktop app)
WARN  2025-10-08T01:13:32.754+00:00 main(ThreadId(1)) [1P:foundation\\op-windows\\src\\windows\\security\\cert.rs:251] operation WinVerifyTrust: Verify primary signature took more than 300 ms (633 ms)
WARN  2025-10-08T01:13:32.755+00:00 main(ThreadId(1)) [1P:foundation\\op-windows\\src\\windows\\security\\cert.rs:206] operation verify_trusted_file_certificate took more than 300 ms (633 ms)
ERROR 2025-10-08T01:13:32.793+00:00 main(ThreadId(1)) [1P:op-ipc\\src\\ipc\\windows.rs:460] peer process and app install paths are not the same. peer process path: D:\\WindowsApps\\Agilebits.1Password_8.11.14.20_x64__amwd9z03whsfe install path: C:\\Program Files\\WindowsApps\\Agilebits.1Password_8.11.14.20_x64__amwd9z03whsfe
ERROR 2025-10-08T01:13:32.793+00:00 main(ThreadId(1)) [1P:native-messaging\\op-browser-support-lib\\src\\communication_logic.rs:201] Failed to connect to the main app: PipeAuthError(InvalidPeerProcessPathLocation)
INFO  2025-10-08T01:13:32.794+00:00 main(ThreadId(1)) [1P:native-messaging\\op-browser-support-lib\\src\\communication_logic.rs:222] Desktop app not running, no connection established
INFO  2025-10-08T01:13:32.794+00:00 main(ThreadId(1)) [1P:native-messaging\\op-browser-support-lib\\src\\communication_logic.rs:559] Attempting to re-establish a connection to the 1Password app
WARN  2025-10-08T01:13:32.794+00:00 main(ThreadId(1)) [1P:native-messaging\\op-browser-support-lib\\src\\communication_logic.rs:484] Tried to re-establish connection with the 1Password app (but it might not have been running): Io(Os { code: 2, kind: NotFound, message: \"The system cannot find the file specified.\" })
INFO  2025-10-08T01:13:32.795+00:00 main(ThreadId(1)) [1P:native-messaging\\op-browser-support-lib\\src\\communication_logic.rs:245] Reached end-of-stream for receiving messages from b5x. Ending SLS communication.
INFO  2025-10-08T01:13:32.795+00:00 main(ThreadId(1)) [1P:native-messaging\\op-browser-support\\src\\main.rs:287] Shutting down 1Password-BrowserSupport 8.11.14-20.BETA production build no. 81114020.