I recently migrated from LastPass to Bitwarden. I used Lastpass for many years. My primary use is Windows desktop with Chrome / Edge. I also use it on Android and iOS.
By far, the biggest frustration I have with Bitwarden (which is the same as LastPass) pertains to the interaction between the browser and the browser extension, specifically password inconstancies between the browser and the browser extension, especially when updating the password. I find that often the password that the extension stores in the vault isn’t the same as the password that is filled in the browser. The website accepts the filled password, but the password in the vault isn’t the same, so next time I try to fill the password, it gets rejected, so I have to go through password reset (again).
This often happens when the website initially rejects the password because it doesn’t meet the requirements. A new password is generated and filled, but the extension stores the version that was rejected. Often, it’s not possible to verify that the passwords are consistent because the Bitwarden “widget” obscures the widget to show the password.
To get around this, I’ve gotten into the habit of opening a sticky note, then generating the password, copying it, pasting it into the sticky note, then finally pasting it into the website. That way, if the wrong password ends up in the vault, I saved the correct one. This should not be necessary.
I hope the developers will tighten up the interaction between the browsers and the browser extension. In particular, the Bitwarden widget should not obscure the website widget to show the password.
Can you explain more about your situation? What version of the browser extension are you using, and how have you configured Settings > Autofill and Settings > Notifications?
IMO, the best approach to update or create a password is to start in the browser extension pop-up window, generate and save a password there, and then use autofill (e.g., Fill button or Ctrl+Shift+L shortcut) to transfer the new password into the website’s password change form. If the form requires the old password to be entered as well, then either copy it from the browser extension before generating the new password, or copy it from the password history.
Speaking of:
The correct password should be present in the generator’s password history. That being said, I need the information requested above to fully understand and reproduce your issue.
OK, I have experimented in the Edge browser extension (2025.6.1) with the options “Show autofill suggestions on form fields” and “Display suggestions when icon is selected” enabled (and “Ask to add.update existing login” disabled), and may have reproduced your problem.
If I click the Bitwarden icon in the Password input field, and then select “Fill generated password” and “Save to Bitwarden” in the inline menu, this opens a pop-out window containing the generated password in a New Login view; notably, the newly created login item is not yet saved into the vault.
If I then submit (or clear) the web form without first clicking Save in the New Login screen in the extension pop-out, and then repeat the process of clicking the Bitwarden icon in the Password input field, then selecting “Fill generated password” and “Save to Bitwarden” in the inline menu, then the New Login item in the extension po-out window still retains the old username and password (from when “Save to Bitwarden” was originally selected). If the user then clicks Save, the wrong credentials are saved in the vault.
Personally, I would consider this a bug. You may want to consider reporting it as a “New Issue” in Bitwarden’s Github repo.
If your preference is to keep using the inline menu and “Fill generated password” function when creating new accounts, then the best work flow to avoid problems is:
Type the desired username in the website account registration form.
Open the inline menu in the website’s password field, and select “Fill generated password”.
In the inline menu, click “Save to Bitwarden”.
In the extension pop-out window, click the Save button (this closes the pop-out window).
Submit the web form.
If there is a password error, click the on the inline menu in either the username or password field of the web form (which opens the previously saved login item in a pop-out window).
In the extension pop-out window, click the (Delete) icon in the lower right corner, and then confirm deletion by clicking Yes; close the pop-out window by clicking its button.
Start over at Step 2 (or Step 1 if the username was cleared from the web form).
An alternative work flow (using the inline menu and the “Fill generated password” function) would be as follows:
Type the desired username in the website account registration form.
Open the inline menu in the website’s password field, and select “Fill generated password”.
In the inline menu, click “Save to Bitwarden” (but do not click Save in the pop-out window).
Submit the web form.
If there is a password error, close the pop-out window (without saving anything) by clicking its button; click Leave to confirm.
If there was a password ewrror, then start over at Step 2 (or Step 1 if the username was cleared from the web form); if there was no password error, then remember to click Save in the pop-out window.
In my opinion, the method that I had mentioned above is much easier than either of these two work flows using the inline autofill menu.
on the inline menu in either the username or password field of the web form (which opens the previously saved login item in a pop-out window).
(Delete) icon in the lower right corner, and then confirm deletion by clicking Yes; close the pop-out window by clicking its 
button.