Workaround: try to start KeepassXC one more time from the taskbar. will stick to what is more relevant describing the behaviours, ant then it may be narrowed down to App or the QT framework config or a bug. Latest windows 20H2, 64 bit, KpXC 2.6.3 release etc blabla.
Dear, I confirm this behavior is still present in the most recent 2.6.3 release, and that is why I write into this thread and not to QT ticket issue thread as it related to this behaviour exactly as described here.Īsof breaking my production machine workflow to send debug data etc just for this simple observation - I can not do that, noticing is ienough, and full belief it is the truth.
