"-useraccount" does not work

[Norman Schmitz]

Hello!
Because KeePass still doesn't take "or" for an answer, redgarding authentication, i tried to use a workaround for connect my database with my Windows Login while maintaining the ability to use it on android.

Therefore I created a dummy database that than via KeeAutoExec opens my actual database.
This last part worked splendidly.

I did this because i read that you can set up KeePass via the parameter -"useraccount" to open the predestined Database with the current Windows Account. I planned to dump a shortcut with said configuration in the startup folder. This part didn't work at all.

I used the following Syntax:
[Code]"C:\Program Files (x86)\KeePass Password Safe 2\KeePass.exe" "C:\Users\User\Documents\zuender.kdbx" -useraccount[/Code]
It simply ignores the added useraccount. It opened KeePass minimized with the declared Database preselected, but it did not move a finger to unlock it. I than tried some misspells on useraccount to see if it makes a difference, until i realized that it doesn't give a fiat what i appended behind it. I does not complain either.

So do those parameters still work? If, what did I do wrong?

[wellread1]

All shared database copies must use the same master key. A database whose master key includes the Windows User Account is not portable. You can't use this database (or its copies) on both Windows and Android. If you need a portable database you can use a master key that includes a master password and/or a key file.

---

You are using the -useraccount command line option incorrectly.

The -useraccount command line option passes the Windows User Account to the database specified on the command line.

• If the command line does not specify a database, KeePass ignores the -useraccount command line option.
• If the command line specifies a database, but the database master key does not include the Windows User Account, then the -useraccount command option is supplying the wrong master key and you will receive the "composite key is invalid" error. The database will not open.

[wellread1]

The Windows User Account (WUA) master key is an expert option. You should not use this master key component unless you understand and have verified that you can successfully backup and restore a database whose master key includes the WUA. See the KeePass Composite Master Key documentation and KeePass Backup wiki for more information.

[Norman Schmitz]

I knew that i cant copy that database.
I knew that it would not be portable.
I knew that it is an export option.
I've used KeePass for many years, just got tyred of typing in another Password directly after the Windows one for my otherwise encrypted and hardened Windows machines.
But thank you for not reading my post.

The Database that gets opened by -useraccount, does not contain any other Passwords than the one for my actual database. If it gets corrupted, deleted oder unaccessable, i simply dont care. It only opens my "real" database via the plugin Autoexec.
This Database on the other hand, containing all the actuall passwords, remains portable.

I used the commandline "-useraccount correctly" and I had a database specified.

But it conflicted with some settings made in the gui. Thats the error I made and that I now want to save others from:

If you choose: "Startup locked and minimized", "-useraccount" does not work. These are obviously conflicting instructions, and KeePass, rightfully so, takes the safe exit.

Afterwards I recommend: "minimze after opening a database". On a sufficiently quick machine the whole opening will take place in a split second.

That way, one of to my knowledge biggest flaws of KeePass, can be circumvented.