You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you are in Windows (I have tested it with Windows 11 and 10), make sure you have the option 'Unlock with Windows Hello' selected and Windows Hello configured on your Windows PC.
Exit Bitwarden Windows client:
right click on Bitwarden system tray icon | Exit
Start Bitwarden for Windows. You are being automatically prompted by Windows Hello to unlock your vault.
Now, lock your vault:
right click on Bitwarden system tray icon | Lock
Open Windows start menu, then double click on Bitwarden for Windows icon. Bitwarden for Windows open itself and does not auto-prompt Windows Hello (like your other apps do). You are forced to do that manually by clicking on the button "Unlock with Windows Hello":
We should have to click on that button to get Windows Hello when the vault is locked, we should get auto-prompt Windows Hello (like on your Chrome extension for example and your Android app)
Expected Result
The expected result is to be automatically prompted by Windows Hello each time Bitwarden Windows client is locked:
Here is the technical solution: The Windows Hello trigger has been added into the Bitwarden for Windows start event, instead of putting it into the Bitwarden unlock event. If I exit Bitwarden completely, I get the auto Windows Hello prompt. Users should also get it for unlocking their vault (like your Android app and Chrome extension are doing).
Operating System
Windows
Operating System Version
Windows 11
Installation method
Direct Download (from bitwarden.com)
Build Version
2022.5.1
The text was updated successfully, but these errors were encountered:
Thanks for the information everyone, the team has confirmed that this is currently working as expected (ei not broken) and that changing this behavior can be discussed and voted on in this feature request.
dwbit
changed the title
Bitwarden Windows desktop client does not auto-prompt Windows Hello after lock, only when 1st starting
Biometrics auto-prompt on Window Focus (after locking vault)
Aug 1, 2022
Thanks for the information everyone, the team has confirmed that this is currently working as expected (ei not broken) and that changing this behavior can be discussed and voted on in this feature request.
What is the argument to claim it is expected ?
If not modified, the Bitwarden desktop app would be inconsistent on this point with Bitwarden for Chrome. For information Bitwarden for Chrome auto-prompt Biometrics.
The renaming in "Biometrics auto-prompt on Window Focus (after locking vault)" is incorrect with the conversation below Is it not on Windows focus, but on relaunching the app. I think you should reconsider with this in mind.
Steps To Reproduce
right click on Bitwarden system tray icon | Exit
right click on Bitwarden system tray icon | Lock
We should have to click on that button to get Windows Hello when the vault is locked, we should get auto-prompt Windows Hello (like on your Chrome extension for example and your Android app)
Expected Result
The expected result is to be automatically prompted by Windows Hello each time Bitwarden Windows client is locked:
Actual Result
Currently this is not what happens
Screenshots or Videos
No response
Additional Context
This bug has been fully discussed in the Bitwarden Community thread: https://community.bitwarden.com/t/windows-hello-auto-prompt-in-bitwarden-for-windows/42293
Here is the technical solution: The Windows Hello trigger has been added into the Bitwarden for Windows start event, instead of putting it into the Bitwarden unlock event. If I exit Bitwarden completely, I get the auto Windows Hello prompt. Users should also get it for unlocking their vault (like your Android app and Chrome extension are doing).
Operating System
Windows
Operating System Version
Windows 11
Installation method
Direct Download (from bitwarden.com)
Build Version
2022.5.1
The text was updated successfully, but these errors were encountered: