"Update Login" don't work

BITWARDEN

BITWARDEN

(For what the HTML-block above? On top is a one-liner HTML with lightweight Style + JS embedded (Rotate Y + Scale)

It’s a pity. There are forums with fully working HTML. And they are in Russia, not like in the advanced BITWARDEN forum :slight_smile:)

  1. It is not clear why this window constantly appears at the top. This started recently. I will update the login after 10 years. So what, now BW will constantly ask me to update my login for 10 years?

    This reminds me of the most annoying situation with constant PUSH to the phone when entering mail portals. What is this for? What if I lose my phone? I’m going to lose him in exactly 10 years. And in many Russian portals it is impossible to disable this.

  1. I believe that the window on top is not needed, and if 1 user on the forum asked the developers for this, this does not mean that it needs to be introduced for all the other 99.99999%. I am one of these 99.99999% and I don’t need it.
  2. And even more so, it doesn’t work exactly when it’s really NECESSARY!
    I enter a new password, then go into the login itself and nothing has changed !

Personally, I definitely don’t need this. Even if everything worked perfectly

That seems to be a current bug – see here: Frequent notices to 'Update existing login' / 'Save (new) login' with latest browser extensions

And that the “updating” doesn’t work seems to be also part of this bug.

and this problem is from 2019? Both notifications (saving a new login and updating the old one) is a useful mechanism. And it’s already done and it’s a pity to turn it off.

When the developers made it. they knew exactly how. BW must compare the entered passwords with those stored in the database.

And now, only 7 years have passed, and they confess that this doesn’t work ???

This window on top appeared (for me) a 2 months ago. And it always hangs. And it seems to me. that 2 months ago everything worked - passwords were tracked correctly.

For most people, this bug first cropped up with the installation of extension version 2025.11, which first hit the streets two weeks ago, on November 13th.

Some people have reported success by rolling back to 2025.10, others have chosen to disable auto-save/auto-update. Feel free to do either, or just click “cancel” until the bug has been fixed.

Yes, I agree, 2 weeks is a realistic time frame for this error. I just don’t understand why the topic Frequent notices to ‘Update existing login’ / ‘Save (new) login’ with latest browser extensions has existed since the end of 2018???

No, I won’t turn it off. I’ll just ignore the error, I still have faith in the BW developers .

I think you misread the date – the first post there is from Nov 18, 2025 (so, from about 9 days ago – and not from November 2018)…

1 Like

yes, that’s right, I just spent half an hour developing code that won’t work in the forum engine anyway. The forum owners have disabled styles and basic JS. Although they could somehow isolate the execution environment.

I do not know how to read the dates. :slight_smile:

1 Like