You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default installation path is "C:\Program Files," regardless of whether the installer is in all-user mode or current-user mode. The installer cannot modify the Program Files directory when in current-user mode, so I have to manually change the installation path.
"%LocalAppData%\Programs\CopyQ" (or somewhere the installer can modify without the UAC prompt) would be better for current-user mode.
To Reproduce
Run the installer.
Click "Install for me only."
Continue installing until the "Select Destination Location" section
Notice that the default location is "C:\Program Files."
Expected behavior
The default path is "%LocalAppData%\Programs\CopyQ" when in current-user mode.
Not sure if this is worth fixing. Looks like a problem in Inno Setup that can be easily worked around by user providing a different path. I do not know where apps should be installed if not in "Program Files" and if Inno Setup itself cannot provide an alternative path.
But if you can provide a fix (a pull request), I would be probably OK with accepting it.
Describe the bug
The default installation path is "C:\Program Files," regardless of whether the installer is in all-user mode or current-user mode. The installer cannot modify the Program Files directory when in current-user mode, so I have to manually change the installation path.
"%LocalAppData%\Programs\CopyQ" (or somewhere the installer can modify without the UAC prompt) would be better for current-user mode.
To Reproduce
Expected behavior
The default path is "%LocalAppData%\Programs\CopyQ" when in current-user mode.
Version, OS and Environment
Additional Context
The developer mentioned in #1912 that Inno Setup should handle this issue previously, but it seems that a solution is now available.
https://jrsoftware.org/ishelp/index.php?topic=consts ("Auto Constants" section)
The text was updated successfully, but these errors were encountered: