After installing KeePass 2.38 on Windows XP it does not automatically open the last used file on Windows startup. Downgrading to 2.37 fixed the problem. Maybe you want to look into it, even if the OS is (carbon) dated ...
Make sure Remember and automatically open last used database on startup is checked in Tools>Options>Advanced(tab)>Start and Exit(section)
Tools>Options>Advanced(tab)>Start and Exit(section)
Was checked, didn't work. Worked immediately again after downgrade, though.
It is still most likely a configuration issue. I can't reproduce it, and there have been no other complaints.
Make sure that you are not trying to save the active configuration file (keepass.config.xml) in the protected Program Files or Program Files (x386) folders. See https://support.microsoft.com/en-us/help/927387/common-file-and-registry-virtualization-issues-in-windows-vista-or-in
Program Files
Program Files (x386)
Verify that the config file is being correctly updated. Each state (checked and unchecked) should be retained through a restart.
Make sure you don't have any command line startup switches set.
Disable all triggers if you use them.
Remove any plugins if you have them.
I have just updated to 2.38 from 2.37 (this thread reminded me) and auto-open is working as expected.
cheers, Paul
Log in to post a comment.
Make sure Remember and automatically open last used database on startup is checked in
Tools>Options>Advanced(tab)>Start and Exit(section)Was checked, didn't work. Worked immediately again after downgrade, though.
It is still most likely a configuration issue. I can't reproduce it, and there have been no other complaints.
Make sure that you are not trying to save the active configuration file (keepass.config.xml) in the protected
Program FilesorProgram Files (x386)folders. See https://support.microsoft.com/en-us/help/927387/common-file-and-registry-virtualization-issues-in-windows-vista-or-inVerify that the config file is being correctly updated. Each state (checked and unchecked) should be retained through a restart.
Make sure you don't have any command line startup switches set.
Disable all triggers if you use them.
Remove any plugins if you have them.
Last edit: wellread1 2018-03-24
I have just updated to 2.38 from 2.37 (this thread reminded me) and auto-open is working as expected.
cheers, Paul