ISSUE: Windows Hello & 1pw Shortcut

robert1p
robert1p
Community Member

The past 10 days everything was fine; however, today (or possibly yesterday) an issue has arisen. [80600078, on NIGHTLY channel]

I have Ctrl-Shift-P defined to open the 1pw app. With the 8.6.0 Nightly Channel I could Ctrl-Shift-L to lock the app, hit the X to close the app, then press Ctrl-Shift-P to open the app again at any time .. and it would open with the Windows Hello prompt to scan my fingerprint.

However, either yesterday or today this stopped working. After Ctrl-Shift-L and closing the app, the Ctrl-Shift-P no longer works; I have to manually locate and open the app again. And when I do, I must login again; i.e. it won't let me use Windows Hello.

If I simply hit Ctrl-Shift-L and don't close the app, then everything continues to work fine.

I rebooted my laptop, but that did not correct the issue. I checked for a 1pw update, but it says I'm at the latest version.


1Password Version: 8.6.0 80600078
Extension Version: Not Provided
OS Version: Windows 10 21H2 19044.1586

Comments

  • robert1p
    robert1p
    Community Member
    edited March 2022

    Today I see that I'm on 80600079.

    Minor good news .. It appears that when I lock and close the app, my Ctrl-Shift-P now opens the app again.

    HOWEVER, I still find the Windows Hello prompt often missing. It seems to happen when I close the app, even if I don't logout of the app. It also has something to do with the AutoLock feature (e.g. when my screen locks, or the system is idle too long).

    I guess I should turn off the AutoLock feature until this is fixed; i.e. I've already entered my password a couple dozen times today.

  • Hi @robert1p, thank you for letting us know about this, and the detailed description of the issue too. I'd be very interested to look into this further on your behalf.

    Would you be able to send us some diagnostics so we can check out the details? You can reach our team at support+windows@1Password.com, and here's how to create the diagnostic report:

    How to Send Us Diagnostics

    1. Click the Windows icon in the lower-left corner of your screen. A list of programs will pop up.
    2. Select 1Password, which should be located near the very top beneath a # symbol.
    3. When 1Password opens, click the three-line icon in the top-left corner.
    4. Then select Settings > Advanced > Send Diagnostics.
    5. Typically, 1Password saves the file to your desktop. Click Reveal to see for yourself.
    6. Attach that file to your email to us. 👍

    It should look something like this:

    BEJhcVSTMn.gif

    Once we have those in hand, I'll go through the data and let you know what we find! And from there we should be able to either provide you with steps to fix the issue, or let you know if there's some work we need to do internally.

    Thanks, and I'll look forward to hearing from you!

  • robert1p
    robert1p
    Community Member

    Email sent.

  • Thank you @robert1p! Message received; we'll continue over there. 🙌

  • robert1p
    robert1p
    Community Member
    edited April 2022

    It's been a month. I was really hoping this would have been a simple defect and easily resolved. Have they been able to reproduce the issue?

    Again, the issue is that if I Lock and Close the 1pw app, then I must re-enter my credentials the next time I open the app (when I should simply have to use my fingerprint).

    I also see that if I simply Close the app and the AutoLock then locks the app, then I also must re-enter my credentials.

  • Hello @robert1p - thank you for following up by email. I just wanted to confirm receipt on our end, as well as that we're going to look into this as a team, as this isn't an issue we've seen reported elsewhere and so will require some more focused work on our part. But we will get back to you as soon as we can. 👍

  • robert1p
    robert1p
    Community Member

    I'm not sure when it was fixed, but it now seems to work correctly again. Yeaaa!!! 8.8.0 80800018

  • Excellent, thank you for letting us know @robert1p! 🥳

  • robert1p
    robert1p
    Community Member

    My mistake. I forgot to turn of the system tray setting before testing this time. Thus, it's still an issue.

  • Hey there @robert1p sorry for the delay here.

    To confirm, are you turning off the option to keep 1Password in the notifications area? If so, this is the source of the issue - if 1Password is not kept in the system tray, it will not remain running in the background after it is locked and quit. In this situation, when 1Password is closed, the decryption key is abandoned - this means that you'll need to unlock with your account password on the next run of 1Password.

    If your device has a supported trusted platform module (TPM), you can allow 1Password to use this TPM to allow Hello unlock after 1Password has been quit - if your device has a supported TPM, you can enable this feature by opening 1Password's Settings, swapping to the Advanced tab, and enabling Use the Trusted Platform Module with Windows Hello.

    Thanks @robert1p let me know how it goes! 🙂

  • robert1p
    robert1p
    Community Member

    Correct, I do not want the 1pw icon in my system tray. And while I understand the current implementation does not continue to run the background task, it is not a required behavior. There are many daemons that run in the background that do not have an icon in the system tray. And it is far from obvious that hiding the system tray icon will cause this behavior.

This discussion has been closed.