T. Bug Reporter

Implementing pre-screening for weak passwords other than the master password would be difficult to implement, because there's no agreement among Web sites and other password-protected facilities as to what constitutes "weak". I have several passwords in my database that had to be deliberately dumbed down to get the Web site to accept them as valid. Setting a single overall definition of "weak" would prevent me from saving the passwords for these poorly-designed sites, and setting this individually...

Actually, my first thought was that KPEEV would be the place to implement this functionality, but then I changed my mind. Group data is an under-utilized feature of KeePass, and this is most likely because getting to it is so difficult - and not easily discoverable.

And again, you are accusing @wellread1 of being unhelpful while being minimally helpful yourself. If we can understand why you're asking, we can probably avoid much of the back-and-forth. Specifically, the changes to the database format in the newer versions of KeePass were programmed to be invisible to the user (to the extent that that's possible); if you've found some instance where this isn't true, we'd like to know the details so it can be reviewed, addressed, and corrected if necessary.

I think @wellread1's point is that if you have an unrelated question, you should have made a new topic - or discuss why you think it IS related.

Unfortunately, the only thing we can say to this is that if it's that important, you should do a manual save immediately after entering it and not depend on the computer staying functional until it shuts down and tells KeePass to do the save on its own. As you found out, the chance of this "save just before shutdown" sequence failing is miniscule but not zero.

Add-ins to change the window title only work for browser windows; I know of no add-in that can modify the title of a Windows Security dialog - and I suspect that Windows itself would actively thwart any add-in that attempted to do so.

{T-REPLACE-RX} is unlikely to help, because anytime Chrome (or Edge, or whatever) receives "http://{...}", it automatically rewrites it to "https://{...}". You rewrite it, Chrome rewrites it back. For example, I have a router that only does HTTP for its config pages, so I'm always getting errors whenever I want to see or change its config - and that "Allowed to show insecure content" setting doesn't help because it doesn't stick - and I keep getting error messages about using an "unsupported opt...

So as to make this thread not be an ad for just one developer's KeePass compatible app, here's a pointer (almost★) to Dominik's list of compatible apps at the bottom of his KeePass download page. (★I can't point you to that list directly, because Dominik doesn't have an anchor on that section of the page.)