Sure, that’s all I was hopefully expecting. Sounds good. Thanks.
I changed it to “Host. That took care of it 
. Thanks.
1 Like
Just curious about the progress about this bug. I still getting prompts to add literally everywhere, I had a situation the other day where there were two different logins for the same page. When I logged in with the correct one, and then went back to Bitwarden to remove the incorrect on, there were now a dozen duplicates of the correct one, but the false entry was not displayed.
v2025.11.2
Browser extension 2025.12.0 fixes that bug – and is already rolling out (the browser stores have to approve it – if you’re on Edge, the new version is already there).
ok, and their still working on the other stuff?
What exactly are you referring to?
The multiple login entries, many of which that should have been updated but remained in the list with their obsolete data, along with other entries that somehow were added containing data such data as both website account pass codes and temporary 2fa codes, in the same entry, in place of the usernames and passwords for a site.
As an example, I just ran across a well known retail business site card account info page for which BW shows six different entries of that type, but no entries with the proper credentials. In the shopping pages, I show no login credentials whatsoever.
However, If I do a vault search for that business, on both the account and shopping pages, I get multiple/duplicate results for both the proper account and shopping logins.
I also just discovered multiples in the Identities section
Bitwarden is not going to fix individual users’ vault data. If there are significant problems with the data in your vault, then your best bet would be to restore your vault from a backup that was made prior to the start of these issues.
My inquiry was not about the current contents of my personal vault. Those are just symptoms.
What would be the point of restoring a backup. I don’t know how many months I’d have to go back for a backup replacement, and for what? Just so I wouldn’t have duplicates, etc.? All the problems would still exist, and I would be nullifying all the updates made since that backup. At least, in the current state, the latest data still exists, even if it is a jumbled mess.
You asked me what I was referring to. I simply requested an update on fixing what is causing those numerous vault issues I mentioned, over and above the “update” prompts.
That was asked by @Nail1684, not me.
There is no known bug causing your “numerous vault issues”, other than the save/update prompt issue that is being fixed with version 2025.12.0.
Commonly, duplicates are created by importing data more than once (or by importing data that already contained duplicate entries), or by saving new login entries when prompted while the vault is locked (because by design, the locked Bitwarden extension has no access to information about what entries already exist in your vault).
It may be challenging to troubleshoot the peculiarities of what has caused the duplicate or redundant vault entries in your specific case, but we can certainly try to investigate this further, if you are willing to participate in fact-finding and testing.
or by saving new login entries when prompted while the vault is locked
I’m on a PC. Importing data = update login?? I don’t understand “vault is locked”, unless you mean not logged in to the Firefox BW app?
I’m happy to participate in the investigation. What’s next?
One other thing I noticed. The “badge” says “2”, but there is only “One” autofill suggestion
I don’t understand the question. Importing data does not in any way merge or combine the imported items with the existing items — if the imported file contains an item already present in the vault, then the import will create a duplicate.
When the icon looks like this, the Bitwarden browser extension is logged in, but locked:
If the browser extension is logged out, then the icon will be gray.
Typically, users set the Timeout Action (under Settings > Account Security > Vault Timeout) to “Lock”, and then configure a timeout interval that specifies when the vault will be locked after a period of inactivity.
This might be a glitch due to caching — try to refresh the web page, open and close the browser extension, or restart the browser. If the issue persists and is reproducible, you may have found a bug in the Firefox extension.
The difficult part is going to be to attempt to uncover the circumstances under which your duplicates are being created. How often do you notice new duplicates appearing? Do such incidents correlate with any specific actions that you have recently taken (e.g., clicking Save on a “Save Login” prompt? Importing data into your vault from file?).
You may be able to get some clues by looking at the “Created” date/timestamp for each item in a set of duplicate items. Were multiple items created on the same date? Do you recall what actions you may have taken in the vault on that date?