I was going to post about this but I guess it’s a known issue and I assume it will be fixed in an upcoming update. I don’t want to disable the update login option because it is useful and I may forget to turn it back on. ![]()
All this extra work, and thread triaging here, github, and other places. Just imagine if the browser extension went thru rigorous testing BEFORE being released to a huge install base.
Vote for a stable browser extension here
I have the exact same issue.
I use the Bitwarden extension with my Brave browser and periodically, a prompt will appear on screen asking if I want to update my existing password. I don’t like the prompt as sometimes it pops up multiple vault entries and I’ve already managed to change the password on the wrong entry. I believe that it also crates additional, duplicate vault entries by creating a URL based name as opposed to the name of the existing vault entry. Is there a way to not show this prompt?
Hi @Moondoggy,
I moved your thread into a relevant topic. Please see the mod notice at the top, and this last update.
I actually like that the extention is prompting about updating the login, this is sometimes helpful when i update the credentials for a site. I think what would be helpful to see in the pop up is what field(s) are being updated. Not the values themselves but just the field name for example if the extension detected a new url, or username or password. This way I as the user can determine if I want to make this update or choose to ignore the notification.
Update is starting to roll out later this week, thanks for your patience everyone!
It’s not just that it asks to update, its that I can’t see what entries it wants me to update
This is when I logged into Linkedin, where I only have one entry.
I guess it’s because I have scaling turned on, but Bitwarden should respect that.
That’s a separate issue – you can add your details here: `8ef7951` renders `/notification/bar.html`'s entrants too short. · Issue #17588 · bitwarden/clients · GitHub
I’ve been noticing for weeks/months that BW prompts me to Update Password when I simply login to a website, even though I’m not changing the password. Anyone else seeing this? Would prefer this only show up whenever logging in with a new password. Thanks. (I’m using Edge browser)
@humblepie Welcome to the forum!
I moved your post into the relevant thread to that issue. Please have a look at the mod notice attached to the first post here – and a fix is on it’s way (next release of the browser extension).
Recently the Bitwarden browser extension had a new “smart” feature added / enabled by which it proposes to update ALL similar entries to the one you are logging into, even if the credential are the one your just used…
Typically (but just an exemple) I have a dozen Google accounts and if I log into one of them I get prompted to update ALL of them with the credentials I just used. If, god forbid, I click “yes” all my entries are trashed.
Is there any way to restore the previous (and IMHO logical) behavior by which only the CURRENT entry is updated and ONLY if the credentials that have been used are actually different from what is stored in the vault ?
I moved your thread into a relevant topics. See the mod notice at the top. I think the rolling-out v2025.12.0 may have the fix.
It “fixes” the issue - at the cost of (somewhat) degraded functionality. This was working just fine till recently.
I feel QA is on downslope as of late. There was the bug with the handling of Passkeys and now this mess about updating passwords ![]()
Disappointed
Happening for me too. Seems like on every URL. Annoying enough I did a search and found this. So - Me too.
This is doing my head in. Not only is it on every single login, but the dialog isn’t even styled properly.
Extension version 2025.12.0, which fixes this issue, is in roll-out. It was released for all browsers on GitHub on Dec 11 and now the browser’s extension stores have to approve and “release” it in their stores.
(as far as I know, extension 2025.12.0 is already available on Edge and in the Chrome web store now)
A post was split to a new topic: Item update – “Resource not found“
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
