Installation inconsistency (Windows)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.6k
- Forks
- 3.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 61
Description
Currently, installer performs a machine-wide installation (requiring UAC elevation) but writes its uninstall entries to 'HKEY_CURRENT_USER' registry key, which may confuse some software like package managers (WinGet is one of them).
I believe for proper consistency you should either:
- choose to install into user directory and leave HKCU as it is now (also disable UAC elevation in this case);
- choose to install into ProgramFiles as it is now but use HKLM ('HKEY_LOCAL_MACHINE') for uninstall entries so that any admin on PC can uninstall the software, not only the one who installed it.
Also, some installers support both types of installation at the same time via command-line arguments like '/CURRENTUSER' and '/ALLUSERS'.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Windows installer implementation and its handling of ProgramFiles, UAC elevation, and uninstall entries in HKCU or HKLM. Compare the current behavior with the two installation models described, then confirm the chosen model or command-line options and test that installation and uninstallation use consistent scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100