Dominik Reichl

Great, thanks for testing it! Your RDP issue is probably not related to UIAccess. Maybe the following helps? https://sourceforge.net/p/keepass/discussion/329221/thread/a5d738aa81/ Best regards, Dominik

I'd suggest to delete the 'File/URL - Filter' from the event of the 'Prueba' trigger, because the current database may already differ from the triggering one at this point and you want it to run for all databases. With the filter removed, everything looks fine to me, i.e. I cannot reproduce the issue. Here's a complete package for testing: https://keepass.info/filepool/KeePass_260319_Test.zip The package contains KeePass 2.61, KeeAutoExec 2.6, three databases (all with master password '123', and...

The {DB_NAME} placeholder returns the name of the current database, which may differ from the one matching a trigger event. As plugin events (used by KeeAutoExec) are raised before trigger events here, we get the behavior that you described. This is correct, not a bug. If you want to see a message box for each opened database, you need to insert another action before the 'Show message box' action: 'Activate database (select tab)' with the filter set to 'Triggering' (and leave 'File/URL' empty). Best...

The next KeePass version will support UIAccess. This Windows feature allows KeePass to perform auto-type into high integrity windows (such as certain 'Windows Security' dialogs) when running as standard user only (not as administrator). It has turned out that enabling UIAccess results in various problems, but I think I was able to implement workarounds for all of them (see [1] for details). If you have some free time, it would be great if you could test the latest development snapshot: https://keepass.info/filepool/KeePass_260318.zip...

Add support for apps with a higher integrity level.

After implementing various workarounds, KeePass finally seems to run fine with UIAccess now. If you have some free time, it would be great if you could test the latest development snapshot: https://keepass.info/filepool/KeePass_260318.zip For UIAccess, KeePass must be started from a secure directory (such as a folder in %ProgramFiles%). Whether it works can be seen by performing auto-type into a 'Windows Security' dialog of an up-to-date Windows 11 system. One way to display such a dialog is via...

KeeAutoExec mess up triggers

The documentation is correct and up-to-date. The cited part describes that KeePass needs to handle such special characters internally in a different way, but that doesn't mean that users cannot use TCATO with them. Best regards, Dominik