Keepassxc: KeePassXC not minimized when launched at system startup

[0ecd3e]

Overview

KeePassXC is not staying minimized to tray on system startup. Once it loads, the window will show in the foreground prompting the user to unlock the database. KeePassXC is minimized when launched from a shortcut, such as the Start menu entry.

Steps to Reproduce

1. Enable "Automatically launch KeePassXC at system startup"
2. Enable "Minimize window at application startup"
3. Reboot system

Expected Behavior

KeePassXC will launch at startup, but stay minimized in the system tray. This was the behaviour for all versions up to but excluding 2.6.0.

Actual Behavior

KeePassXC launches and displays its window in the foreground, and is not minimized. Launching KeePassXC from the Start menu or a shortcut will keep the program minimized to tray as expected.

Context

My settings have not changed since I updated from the previous 2.5.x version of KeePassXC. This feature has always worked perfectly.

KeePassXC - 2.6.0
Revision: 0765954

Operating System: Windows 10 1909 (x64)

[droidmonkey]

You have it both in your startup folder and enabled to start in your registry. Remove the shortcut from your startup folder.

[0ecd3e]

This is not correct. KeePassXC was not in my startup folder, and never has been.
The fix is, unintuitively, disabling the KeePassXC startup entry through Task Manager.

[droidmonkey]

We add it per system standards

[droidmonkey]

Did you setup keepassxc to startup on login before 2.6.0? If so, that means you most likely had it starting twice after you upgraded (once from your original method, again from the registry entry we make). The second startup causes the program to gain focus because of single instance.

This is the same thing that happened to the user in #5061.

[0ecd3e]

EDIT: Previously, there did not seem to be a built in way to start KeePassXC on boot. A workaround was to use a Task Scheduler entry, which is what I did and subsequently forgot about because it worked with no problems.

KeePassXC 2.5.x and below never had a startup entry in Task Manager for me, which is why it was working fine until now as it was only being launched by Task Scheduler.

The current behaviour of adding a registry entry in Task Manager when the auto start is enabled, and removing it when it is disabled is the expected behaviour.

[droidmonkey]

We never had a task scheduler entry, where did you pull that from? 2.6.0 is the first version to introduce an option to start on login.

[phoerious]

We have never had such a feature.

[droidmonkey]

That setting only ever appeared in 2.6.0. Did you download from some third party source like PortableApps or something?

[0ecd3e]

Interesting, so it was never there. I just checked 2.5.4 on my Linux machine.
My suggestion now is to make this evident in the changelog, as it stands it doesn't have enough emphasis. It could use some bold font, along with a link to this issue or #5061 in case someone else runs into what I or they have.

[0ecd3e]

Nope, I have only downloaded it from the official website. I have probably forgotten about the task entry because it has worked fine for all this time.

Thanks for being responsive and helping me figure this out.