same thing with Firefox extension Desktop 2025.2.0, Extension 2025.2.0 Windows 10, Windows hello opens flashing on the taskbar. reinstalled extension, logged out of desktop app etc etc.
I’m logged in to bitwarden desktop app. Biometrics is working fine to unlock the desktop app on my MacBook Air w M3 chip.
I used to be able to use biometrics to login to the chrome plugin.
Are you saying that I should uninstall and reinstall the chrome plug in to match the same version of the desktop app?
Well, that’s one reason why I corrected the title of this topic… There is no “login with biometrics” with the Bitwarden apps…
(Well, to be exact: the only thing that maybe could be called “login with biometrics” with Bitwarden would be “login-with-passkey”, as such a login-passkey – with biometrics as User Verification – can login someone to the Bitwarden account/vault with biometrics (and as “login-with-passkey” is still in Beta, it’s currently still possible only for the web vault). → But that is something very different to the “unlock with biometrics” between desktop app and browser extension…)
So, if you didn’t do it now, I would suggest, to first login in the browser extension (in whatever way you want or can - just not with biometrics, as it’s currently impossible 
)
As you didn’t write the version of your Chrome Bitwarden browser extension, I don’t know if you have to uninstall and reinstall it. If it is already on the current version 2025.2.1, you don’t have to.
On the other hand, deinstalling and reinstalling is not a bad idea when something doesn’t work, so you could try it. – Either way, you should also make sure, you have everything set up as it should be (in the desktop app and the browser extension): Unlock with Biometrics | Bitwarden
This is my browser plug-in “About” info:
Version 2025.2.1
SDK: ‘main(287e29)’
Server version: 2025.2.0
this is my bitwarden desktop app “About” info:
Version 2025.2.0 (37899)
Do they need to match? I dont see any new version in the apple app store for macbook.
No, they don’t need to match. Luckily… because not every new version arrives on all systems immediately…
… ah, that can be… then for the Mac/Chrome extension, 2025.2.0 is the latest at the moment.
I believe I have found a workaround. After getting the error message below, I click on “More choices” and then PIN. In addition to letting me in, I am subsequently able to lock/unlock the same browser with Hello-Face. This does survive a browser-restart, but have not tested a system reboot nor how long the “workaround” persists found that that the fix is not permanent. After having rebooted a machine and let it sit for the weekend, Face did not work and I once again had to resort to PIN..
My failure mode is that Unlock with Windows Hello Facial Recognition fails with the message above, but Unlock with Windows Hello PIN succeeds.
I have been able to reproduce this problem plus workaround on the following browsers (all current), and often times using a fresh install of the extension.
- Chrome 134.0.6998.89 (Official Build) (64-bit) 2025.2.2
- Edge 134.0.3124.68 (Official build) (64-bit) 2025.2.2
- Opera 117.0.5408.93 Bitwarden 2025.2.1
- Firefox 136.0.1 (64-bit) Bitwarden 2025.2.4
All on Windows 24H2 (OS Build 26100.3476), Bitwarden Desktop 2025.2.1
If anyone has a Windows Hello Fingerprint reader, I would like to know if you have the problem in the first place and if this workaround helps.
Note: given the above testing results, I’m changing the title from “Unable to unlock with biometrics using Chrome Extension” to “Unable to unlock browser extensions with Hello+face biometric”
2 Likes
Hi,
Same here. I can succesfully access windows app with windows face hello every time a try. It is very difficult to access bitwardens firefox browser extension after that. Face hello doesnt work but I can log in with PIN. I used to have no problems in the past. Since maybe two or three weeks same issue on two windows computers.
I’m experiencing the exact same issue as the OP. This has been happening for 1-2 months. Some additional details in my case:
- Face Unlock works fine in the first of my Chrome user profiles, but not in the 2nd one.
- In the 2nd Chrome profile, PIN unlock works reliably.
- Chrome version: Chrome is up to date - Version 134.0.6998.89 (Official Build) (64-bit)
- Bitwarden Desktop: Version 2025.2.1 SDK ‘main (6008e90)’ Shell 34.0.0 Renderer 123.0.6834.83 Node 20.18.1 Architecture x64
- Bitwarden Extension: Version 2025.2.2.
Today, I updated my Edge extension to 2025.3.2 (from 2025.3.1) and have 3 times now been able to unlock with Hello+face. Note that my desktop version is unchanged from my earlier report.
- Edge 135.0.3179.54 (Official build) (64-bit)
- Bitwarden 2025.3.2 Hello+face WORKS!
- Windows 24H2 (OS Build 26100.3624)
- Bitwarden Desktop 2025.2.1
A few caveats:
- My results are very young, so consider them preliminary.
- This version is not yet available for other browsers.
- I did a fresh install (uninstalled the old extension, installed the new extension and then reenabled Biometrics in settings). Unknown if an in-place upgrade is sufficient.
that time shows Extension 2025.3.2 fixes this issue.
2 Likes
Unfortunately the latest firefox extension update 2025.3.2 still doesn’t fix it for me. Still gives me the “Something went wrong” message when trying Windows Hello face, the Windows Hello pin workaround still works but isn’t ideal. Tried reinstalling the extension and same results. Bitwarden Desktop 2025.3.0
1 Like
I also still have this problem with different browsers like Google Chrome, Microsoft Edge and Firefox. Can you please fix it. It makes me crazy.
Regards,
Stefan
2 Likes
A post was merged into an existing topic: Windows Hello bitwarden extension - face recognition: “Something went wrong”
I authenticate with Windows hello face recognition to logon in the desktop app. It works fine.
When I try to do it in the browser extension it doesn’t work. I must type the Windows PIN. Face recognition tries to authenticate but stops. “Something went wrong”.
I’ve tried in edge, chrome, firefox and on different computers. No luck.
It has worked some time ago.
Hello Mike and welcome to the community!
This is unfortunately an on-going issue, try following the thread here:
Any progress on this? I’m experiencing this as well and can’t reinstall the extension every 2 days.
Do you want any logs? I want to assist you in anything needed or else I’m being forced to look for alternatives.
Please check this asap.
Windows 11 Pro
|Version|24H2|
|OS build|26100.4061|
|Experience|Windows Feature Experience Pack 1000.26100.84.0|
Bitwarden
Version 2025.3.0
SDK ‘main (50f5a17)’
Shell 34.0.0
Renderer 132.0.6834.83
Node 20.18.1
Architecture x64
Bitwarden Chrome extension
Version: 2025.4.0
SDK: ‘main (50f5a17)’
Server version: 2025.5.0
Chrome
Version 136.0.7103.114 (Official Build) (64-bit)
@mikegnorp @Neuron5569 I now moved your posts into this thread.
Still an issue for me. Posted temporary workaround works, unclear what state breaks the workaround. Sometimes it works for a few days, sometimes for a few hours.
OS: Win11 24h2 26100.4061
BW App: 2025.3.0
BW Ext: 2025.5.1
Browser: Edge 136.0.3240.92
My Windows Hello facial recognition fails because the UAC window pops up behind the browser window and when I switch it, it fails. The Windows Hello PIN works still functions but it’s been over half a year since I was able to get facial recognition login work. It doesn’t work for the Firefox browser extension and it doesn’t work for the Windows application either.
We’re approaching the 6 month mark since this topic was raised, and it’s far from the only one. Is there any acknowledgment or communication from BW on this issue?
Bug reports #13291 and/or #14608 may be relevant. Bitwarden reps have engaged with both threads.
I would suggest that users affected by this issue should do the following:
-
Contact support. Even if they are unable to solve the problem, you may get information about the status of the issue; contacting customer support will also give Bitwarden a better sense of how many users are affected by this bug.
-
Subscribe to notifications about updates to the above-referenced GitHub issues.
-
If you have additional information to provide, contribute a comment to the discussion of the most relevant GitHub issue.