Skip to main content
M
mgrobins
May 18, 2025
Question

Browser req pw always, instead of using biometric & windows hellow

  • May 18, 2025
  • 3 replies
  • 225 views

Hi,

I use 1 password on my windows 11 PC. I have a fingerprint reader and my motherboard has TPM 2.0. 

I have setup 1pw to use windows hello to unlock when I use the app or browser and yet every time I need it in Edge or Chrome it wants the password. Every time. 

It used to be that my fingerprint would be requested and pw occasionally based on my settings. Now it just seems stuffed and it's down right annoying. 

Windows hello on login to Windows - it uses my fingerprint... so that's functioning. 

I have tried resetting my TPM data, checked my TPM is functioning properly using CLI.... I'm thinking it's just that 1pw is screwed and this is a long standing bug now.

Am I required to open the 1pw app every time I start my PC as a workaround? I think that will allow the browser plug in to work properly or is that method broken too? 

It used to work so I'm hoping not to be told I have to open the app and login to it each time I boot in. 

I've searched all over for advice and reddit is full of posts with this issue talking about it being broken for months. No one really explains how it's meant to work in detail... just instructions written for people who already know what they are doing or a list of steps that don't explain anything about what the actions trigger.

    3 replies

    TataruTaru
    TataruTaru
    May 18, 2025

    I have the same problem and I followed the same steps, even pulling a diagnostic report, it seems to make mention of Biometrics, but it feels like it's not saving to TPM, only using Windows Hello, once you've added the master password on a new startup.

    Even if we could find out where to check, would be a step to see what's possibly causing this issue.

    I am currently running the MSIX version, so it could have an effect on that.

    2025-05-18T07:48:31.342+00:00 [1P:data\op-account-system-unlock\src\lib.rs:806] Adding system unlock key. Verifying keysets can be decrypted.
    2025-05-18T07:48:31.344+00:00 [1P:data\op-account-system-unlock\src\lib.rs:812] Adding system unlock key. Encrypting muk.
    2025-05-18T07:48:31.344+00:00 [1P:data\op-account-system-unlock\src\lib.rs:818] Adding system unlock key. Updating account.
    2025-05-18T07:48:39.939+00:00 [1P:app\op-app\src\app\backend\lock_screen.rs:93] System unlock is enabled: true
    2025-05-18T07:48:39.940+00:00 [1P:foundation\op-system-auth\src\lib.rs:329] Biometry is available for 1 or more accounts
    2025-05-18T07:48:40.162+00:00 [1P:app\op-app\src\app\backend\lock_screen.rs:93] System unlock is enabled: true
    2025-05-18T07:48:40.162+00:00 [1P:foundation\op-system-auth\src\lib.rs:329] Biometry is available for 1 or more accounts
    2025-05-18T10:56:38.277+00:00 [1P:app\op-app\src\app\backend\lock_screen.rs:93] System unlock is enabled: true
    2025-05-18T12:29:00.745+00:00 [1P:foundation\op-system-auth\src\lib.rs:329] Biometry is available for 1 or more accounts

    •  Algorithm Name: RSA
        Name: S-1-5-{redacted}/ef8{redacted}/S-1-5-{redacted}//1Password-Enclave-Key
        Algorithm Name: RSA
      M
      mgrobinsAuthor
      May 19, 2025

      I'm not sure what to add to this at this point. I know it worked and now it doesn't, yet my TPM is still considered live and correct. 

      I wonder if the 1PW credentials that are meant to be stored in the TPM are not being? 

       

      M
      mgrobinsAuthor
      May 19, 2025

      I thought a workaround may be to have the 1PW app start on windows boot. This only results in the app requesting my fingerprint... then requesting the password /facepalm. 100% of the time.

      Whatever is happening it is definitely an app problem and possibly associated with the TPM / TPM driver. 

      I have an Asus x870 Tuf Wifi Gaming motherboard. Latest bios and drivers. Latest windows 11 install. Windows Hello active and working. I use a "Local account" for windows (by necessity) and sync my browsers. 

      This problem is present on Edge and Chrome.

      1P_Dave
      1P_Dave
      1Password Employee
      May 20, 2025

      Hello @mgrobins and @TataruTaru! 👋

      I'm sorry that you're being prompted for your account password more often than expected. So that I can better understand the situation can you tell me the following: 

      1. When you're asked for your account password in the browser, can you still unlock the 1Password desktop app using Windows Hello? Or does that also prompt you for your account password?
      2. Do you have the "Use the Trusted Platform Module with Windows Hello" option turned on in the desktop app's settings: Manage your settings
      3. Do you have TPM 2.0 enabled: Enable TPM 2.0 on your PC
      4. Are you using the beta MSIX installer? Or the EXE installer?


      I look forward to hearing from you.

      -Dave

      TataruTaru
      TataruTaru
      May 20, 2025

      Issue

      Every time I start my PC and open the 1Password desktop app, it asks for my master password before showing the Windows Hello prompt. This occurs after every reboot or system start, even though Windows Hello is enabled and working normally elsewhere.

      My Current Configuration

      • TPM 2.0 is enabled, activated, and owned.
      • Windows Hello (PIN login) works without issue on Windows login.
      • 1Password's "Use the Trusted Platform Module with Windows Hello" setting is enabled.
      • I’m using the MSIX version of 1Password (from the BETA).

      Troubleshooting Steps Taken

      1. Checked TPM Status:Get-WmiObject -Namespace "Root\CIMV2\Security\MicrosoftTPM" -Class Win32_TPMOutput:
        • IsActivated_InitialValue: True
        • IsEnabled_InitialValue: True
        • IsOwned_InitialValue: True
      2. Reviewed diagnostic logs:
        • Error: Failed to authenticate via Windows Hello: Error code 0x80090014
        • Message: TPM access error or key mismatch
        • Log line: Could not get key from unlocked account!
      3. Tried the following:
        • Uninstalled 1Password and deleted all local app data
        • Removed the browser extension
        • Reinstalled both the MSIX and MSI versions
        • Issue persisted across all reinstall attempts
      4. TPM Reset Test:
        • Booted into BIOS
        • Turned TPM off, rebooted, then turned it on again
      5. Switched to EXE Version:
        • Installed the standalone EXE version from 1Password’s website
        • Windows Hello worked immediately after reboot — no master password required

       Final Outcome

      • The MSIX version consistently asks for the master password after a reboot and does not reliably use Windows Hello to unlock directly.
      • The EXE version, after TPM reset, works as expected and unlocks using Windows Hello even after a full system restart.
      • I’ve decided to stick with the EXE version for now, as it offers stable Windows Hello support on boot.


      (Post was re-written to cut down on the rambling)

      1P_Dave
      1P_Dave
      1Password Employee
      May 21, 2025

      @TataruTaru 

      Thank you for helping us to test the MSIX beta and for the detailed information! I can confirm that you're running into a known issue with the MSIX version of 1Password for Windows that our development team is currently investigating. For the time being being, using the EXE version is the best workaround since it isn't affected by the issue. 

      I'm sorry for the inconvenience. 

      -Dave

      #37637

        Terms & ConditionsAccessibility statement

        ©2026 1Password. All rights reserved.
        4711 Yonge St, 10th Floor, Toronto Ontario, M2N 6K8, Canada