You can prevent updates with an environment variable:
setx ELECTRON_NO_UPDATER 1
I’ve gone back to 2025.7.0 this way. I hope there will be a solution to the problem soon.
1 Like
Hey @dwbit, thanks. It’s probably better if we move this to another thread but, yes, I need to login on the desktop app before I am ever able to use biometrics in-browser.
Thanks, very valuable information. I’ll give the old version a try—giving Bitwarden one last chance.
I was reading this thread now for a while and my impression, and don’t get me wrong, is somehow Bitwarden vs. Community. I realy appreciate the work of the Team, so it only feels like this.
On the one hand:
- Security by Design, so do everything to be secure!
On the other hand:
- Easy and effortless Workflow!
So, what is best for our all security:
- Guess depends from person to person but having the weakest behaviour in mind.
In Detail, we all know, people are lazy and lazyness was always the most critical issue in security (phishing is one of the best example or even creation of master passwords I guess).
So changing the behaviour of the people and telling them it is just an little change more or less not mentionable change, is the solution … wait, realy?
By this point I think most of us know reaction of people who feel kind of betrayed (removing a function working for years) or even being forced to do it different now (Losing so much comfort), probably will not work.
So final decision is on Bitwarden developers team, or isn’t it (who is using Bitwarden…)?
Only wanted to mention this even if I’ve read the team is again thinking about the topic.
At least I’d like to have the oportunity to overrule an extrem strong security by some lazy workflow with a real present Warning while enabling this.
Finally, keep going on the good work, thanks for all the effort and trying to give us the best product possible!
Hey @indiana the team added more context regarding exploring ways to bring the functionality back both reliably and securely as there were multiple reasons the change was made, but most importantly we hear the feedback and we will share updates on progress made (for exploring restoring functionality or alert etc..), thanks for your patience!
4 Likes
@Anthony_Marchese I must say I am in complete agreeance with you here. Using a local PIN or Biometrics is a passwordless login method that is essential to account security when on the road. A good example is being at an airport where there are people everywhere, cameras all over the place, and having to type your full password in could be captured by all kinds of watching devices or just an observant person who’s in close proximity.
I really like Bitwarden, and I have been pushing for this to become my company’s default recommendation to clients for password management. However, this change undoes all of my faith in what has been an awesome product until now. Forcing this kind of change without giving the end user the choice to decide on their “risk” status based on their workflow is both an ignorant and arrogant standpoint that needs to be corrected asap.
1 Like