Same issue here.
In addition to that it seems that it also broke the biometric pairing between the browser extension and the desktop application. As always when biometric doesn’t work, i tried to disable/enable it again in the browser extension but it now fail with the message “Action was cancelled by the desktop application.”
Firefox Browser Extension version 2025.7.1 (no update available)
Desktop application updated to 2025.8.0
@nex84 I just set up biometric unlock for the Firefox extensions 2025.7.1 / desktop app 2025.8.0 successfully. (Windows 11)
Thanks for pointing this out, that makes sense. I do hope a better solution can be found in the future, as the current change does make everyday use less convenient.
You’re right, my earlier wording was inaccurate. What I meant is that the change affects the browser extension, rather than completely breaking it.
@Nail1684 It’s still stuck disabled in the browser extension settings.
I will test again after a complete restart…
Good idea.
Maybe I’m a bit too cautious these days - but maybe also think of resetting BW biometrics again, and start by deleting the “Bitwarden biometrics” entries in the Windows credential manager (Control Panel → User Accounts → Credential Manager).
@Nail1684 It’s working after a reboot of the PC without the need of redo all the Windows Hello setup.
@nex84 To clarify: can you unlock Bitwarden 2025.8.2 with biometrics for the first time after a reboot? I cannot—what action did you take?
@bgeneto To unlock the desktop app with biometrics for the first time after app start is impossible at the moment / with the current versions.
@bgeneto As stated previously, you must first unlock your desktop application or the browser extension with another method than Windows Hello. Then you will be able to unlock the next times using biometrics.
My problem was different : I wasn’t able to re-enable the biometric option in the browser.
To prevent confusion with the biometrics changes currently being discussed in another thread, I’ve moved this discussion into its own thread, and I am closing it as solved.