-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
MSI installer always creates a desktop shortcut #8711
Comments
Can't reproduce this at all, are you sure this is happening from our installer or something setup on your computer specifically. Your other issue seems highly suspect as well, not reproducible. |
I get the same behaviour on Windows 10 with the MSI installer for KeePassXC 2.7.4 and 2.7.3 (I can't remember whether I had this on previous versions). |
Yes. This happens to me with your installer. |
Looking in my registry, KeePassXC has set a property "DesktopShortcut" with a value of 1: presumably from a previous install. When I run the installer, the checkbox for "Create Desktop Shortcut" is checked by default, which seems reasonable given the registry entry. The problem is that manually unchecking that checkbox does not stop the creation of a desktop shortcut for the current install (and nor does it remove or change the value of that registry entry). I'm guessing that if I deleted the registry key, subsequent installs would work correctly. But the current behaviour seems suboptimal: my choice on a past install means that only by going into the Registry Editor can I ever suppress the creation of the shortcut in future. |
That's a good finding but certainly not unique to 2.7.3. The installer code to add desktop shortcut hasn't changed for years. |
Sure, I definitely wouldn't swear to it not being an issue on previous versions :) Looks like the WIX config was overhauled in June 2021 - possibly the |
well seen! |
Steps to Reproduce
Expected Behavior
Desktop shortcut not created.
Actual Behavior
Desktop shortcut is created.
KeePassXC - 2.7.4
Operating System: Windows 10
The text was updated successfully, but these errors were encountered: