Extension wrongly shows Windows Hello as unavailable

[bilogic]

Steps To Reproduce

1. Quit BW Windows desktop (App), Chrome Extension window (Ext) and Chrome
2. ✅Start App, ensure that Windows Hello is available (Log in, but lock the vault)
3. Quit the App and start it again, do nothing else
4. ✅Open Ext and see that Windows Hello is available
5. ✅Quit App, Windows Hello becomes unavailable in Ext
6. Close the Ext, but leave Chrome running
7. Start App, again, do nothing else
8. ❌Open Ext again but Windows Hello is still unavailable. Wrong because the App is running and vault locked from step 7
9. If I restart Chrome, Ext shows Windows Hello is available again

Expected Result

Opening the Ext in step 8 should show that Windows Hello is available. If step 5 can react when App has quit, step 8 should also react when App is started.

Actual Result

Opening Ext shows Windows Hello is unavailable

Screenshots or Videos

No response

Additional Context

No response

Operating System

Windows

Operating System Version

No response

Web Browser

Chrome

Browser Version

No response

Environment Versions

Version: 2025.12.0

SDK: 'main (0107af7)'

Server version (Third-party): 2025.12.0

Connected to third-party server implementation, Vaultwarden. Please verify bugs using the official server, or report them to the third-party server.

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-30323
Link (for internal use): https://bitwarden.atlassian.net/browse/PM-30323

[pamperer562580892423]

Server version (Third-party): 2025.12.0

Connected to third-party server implementation, Vaultwarden. Please verify bugs using the official server, or report them to the third-party server.

Another user here.

When you use Vaultwarden instead of Bitwarden, you should have a look at this info from Vaultwarden about reporting potential bugs: https://github.com/dani-garcia/vaultwarden/wiki/Bitwarden-clients-troubleshooting

[bilogic]

Well reporting to vaultwarden assumes the server being the problem, instead I have basis to think that this to be between the desktop and chrome extension.