I’ve noticed this “Update existing login” notification behavior in various places, but below I’ll list various sites that trigger it after submitting my password:
https://www.wordfence.com/sign-in is another one, after submitting password, which is before submitting 2FA, and the notification pops up again after submitting 2FA.
Hmm. Did you refresh the respective website after you added the domain to the excluded domains? (and did you actually click “save” to save the domain?) – In my tests, the popups do get suppressed when the domain was added to the excluded domains.
Thanks, and yes, I clicked Save. It’s either save or cancel, and the saved domain remains in the box where it’s first entered. And I refreshed the target site and even exited it and tried later with the same result. The domain is Stifel dot com, but you’d need an account to create access to the client pages.
Actually, it’s not save or cancel: you can also use the back button in the top left corner – equivalent to “cancel” – and as in the “Settings” section of the extension you don’t have to click save, but in the excluded domains section you have to click save, that’s indeed a confusing dark corner… and I only added it to my previous post, because more than one time I myself clicked back and thought it would be saved.
Thanks for that addition! It seems, this bug comes in many flavours.
Happening to me also: Windows 11 Pro 25H2, Firefox 145.0.1, Various sites
Autofill not working on Vanguard.com , hitting the fill button doesn’t work properly either. I need to copy and paste the user-id and password manually else i get incorrect userid or password error. This seems to have started on 11/19 , i notice that there was a browser extension update on that date. Any chance of rolling that back until the problem is fixed?
… though, autofill issues per se are not the topic of this post. – There are other threads about this… - or probably better: open a new thread about your specific autofill issue(s).
Apologies, my original post was unclear. I am experiencing the issue which is the topic of this thread - Frequent notices to ‘Update existing login’ - as well as the other issues I noted and they all began on 11/19.
Firefox does have the ability (in their store) to download old extension versions and also to turn off auto-updates. You can do this in your browser if you wish, but do remember to turn it back on at some point because Bitwarden does have limits preventing old extensions from logging in and downloading ones vault.
However, there are also good things added in 2025.11, so you might also consider implementing one of the work arounds in the staff-notice at the very top of the conversation, before the first post.
Please discuss autofill over on this other thread, so that we are not repeating our collective selves and are not causing confusion by discussing two things at once.
Has been happening all day for me. The last website it happened to was for store.steampowered.com. It also happened for Microsoft’s Office online website as well. I only store cookies for the session, so it has been happening to most of the website I logged into today.
I am using BitWarden on Firefox with version 2025.11.00 version of the addon.
Remember to turn off “allow automatic updating” in the firefox extension manager for Bitwarden extension. And remember to turn it back on after this is fixed
Instead of rolling back the extension, one can also simply turn off these two settings (under “notifications”), as suggested in the mod notice at the top of this conversation.
After you do this, you still can create new entries using the inline auto-fill menu, by clicking on the shield after you generate or manually enter the password; it just won’t remind you anymore.
Even after this bug is fixed, I may keep the two “Ask to…” settings off because I much prefer to validate my passwords are in the vault before hitting the web page’s submit button, while I still have a chance to intervene.
since version 2025.11.0, Bitwarden has been suggesting that I save or update the login I used for many logins. I only use existing logins, and this was not the case before 2025.11.0.
