Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unistaller does not remove the MS Windows Registry key for Uninstalling #768

Open
2 tasks done
hsparra opened this issue Mar 28, 2024 · 2 comments
Open
2 tasks done
Labels
type::bug describes erroneous operation, use severity::* to classify the type

Comments

@hsparra
Copy link

hsparra commented Mar 28, 2024

Checklist

  • I added a descriptive title
  • I searched open reports and couldn't find a duplicate

What happened?

The Windows uninstaller created by Constructor when creating a custom installer is not removing the Registry key for uninstalling. This results in the Miniconda application showing up in the MS Windows --> Control Panel --> Programs and Features panel. Each time that a new version of the Miniconda installer is installed/uninstalled, an additional shadow is left in the MS Windows Registry.

a minimal spec portion from constructor.yaml:

keep_pkgs: false

specs:
- anaconda-client 1.12.*
- conda 24.1.2
- conda-build 24.1.2
- conda-repo-cli 1.0.*
- conda-verify 3.4.*
- console_shortcut_miniconda 0.1.*
- menuinst 2.0.*
- powershell_shortcut_miniconda 0.0.*
- python 3.11.*

A manual cleanup of the Registry key entry is required
Get-ChildItem HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*conda* | Remove-Item -Force

Conda Info

No response

Conda Config

No response

Conda list

No response

Additional Context

No response

@hsparra hsparra added the type::bug describes erroneous operation, use severity::* to classify the type label Mar 28, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in 🧭 Planning Mar 28, 2024
@marcoesters
Copy link
Contributor

I am unable to reproduce this. I created an installer with these specs on Windows 11 using constructor 3.6.0 and 3.7.0.

Could you provide the following information?

  • the Windows version
  • constructor version
  • the installation destination
  • installation settings that were used (all users vs. single user, e.g.)
  • how the uninstaller was called (via Apps or using the uninstaller directly)

@hsparra
Copy link
Author

hsparra commented Apr 4, 2024

We are working at isolating which environmental factors are impacting the problem. We have some environments where the issue does not occur.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type::bug describes erroneous operation, use severity::* to classify the type
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants