Where to start debugging this? app fails to load properly at startup and requires system is rebooted to work

[lectrical]

Hello, i have had an ongoing Windows 11 x64 issue for some time, across various versions of Windows 11 and currently on

This is the problem.

When windows starts, if the taskbar icon does not load, then keepassxc will never work for me until i reboot the system. If the taskbar icon loads things are fine.

If the taskbar icon failed to load, the program will be running in task-manager, i can kill the process and start it. If i load a browser with the extensions the proxy exe loads but i cannot interact with the application in any meaningful way.

• The extensions cannot connect to the main db.
• I cannot open the ui of the app.
• There is no taskbar icon.
• logging out of session and back in does not fix it.
• reinstalling does not fix it.
• installing vs redistributable does not fix it.

I seem to have at a ratio of about 70% success at the minute and that is why i tolerated it for all this time. Recently it's been happening more often than not and it's starting to really bug me. I'll be in the middle of doing something and need to use keepassxc only to realize it didn't load this session and have to reboot.

I need to resolve this but don't know where to start to debug. I don't know if something else is doing this to keepassxc or the result of a bug in the program itself.

Reinstalling the app does not fix it. Installing vrcred does not fix it. Only restarting the system will fix it, potentially.

How do I go about debugging this issue please?

[droidmonkey]

Kill KeePassXC from the task manager. There should be no need to reboot. Delete %localappdata%/KeePassXC/keepassxc.ini. start keepassxc again. Exit. Reboot. See what happens.

[lectrical]

I'll do more checks next time it happens to see if there is something reproducible.

In hindsight I do occasionally have some issues where gpg4win was not loading keys i had to restart kleopatra and the smartcard services to be able to use the keys to sign commits.

I had not connected the two issues as possibly related though so i will try to check if there if there is some relationship between the two programs where the issue next occurs.

[droidmonkey]

There is a problem on our end because keepassxc is not behaving in the presence of this issue, but it's hard to pin down where that failure is right now.

[lectrical]

OK, next time it happens i'll try killing off gpgwin and related services to see if that allows keepassxc to start without removing the usb hub.

I kind of know what i'm looking for now so i'll try to see if i can narrow the cause down further.

[droidmonkey]

Do you have more than 4 yubikeys conected to your computer?

[lectrical]

No, I have 3. 2 v5 via one hub and a v4 via another.