When installer fails #10

chrissie1 opened this Issue Sep 12, 2011 · 11 comments


None yet

7 participants


When an installer fails to install the package should not be put in the lib folder or be removed from the lib folder.


Migrated notes from #15:

I tried to install cUrl, but the package was not found and thus the install failed.

When running cup all, I'm getting this:
curl does not appear to be on (https://go.microsoft.com/fwlink/?LinkID=206669). You have 7.21.7 installed. Interesting...

chocolatey member

@henningc - I did log another issue for you on what you are experiencing - #16 - I also closed it with chocolatey (which you can get with cup)


Just wanted to comment on this as I had the same issue. Installed ruby, went to install compass and the install failed due to PS not being sourced - exited and reopened PS, gem list showed no compass installed, cinst compass said it was already installed, cinst compass -force and all set (Or just remove from /lib).

chocolatey member

Yeah, definitely want to address this in the upcoming version.


When using meta packages this is quite painful. The meta package downloads all the dependencies; one of them fails; chocolatey thinks that all of the dependencies are installed.

Each one needs to be "-forced" installed one by one when error condition is fixed.

Semi-related to #199

@ferventcoder ferventcoder added a commit to ferventcoder/chocolatey that referenced this issue May 22, 2013
@ferventcoder ferventcoder moving bad installs when an installer fails #10 54e44a1
chocolatey member

This is fixed...


In what release was this fixed? I am running Chocolatey I tried installing 7zip, but I don't have administrator rights on my machine at the moment, so it failed. But when I run "cver all -localonly", I see 7zip installed. Moreover, if I try to uninstall 7zip using "cuninst 7zip", I get the error message saying that the package has not provided an uninstallation script, and I have to uninstall it manually. But 7zip stays in the installed list, and there seems to be no way to remove it.


Yeah I just ran into this, I don't think it's fully fixed.

chocolatey member

@mkmurray let's chat on chocolatey/choco, ensure you are on 0.9.10.x.

@ferventcoder ferventcoder locked and limited conversation to collaborators Jun 28, 2016
chocolatey member

What you are seeing is likely a different issue and definitely not over here on the old POSH version. Https://github.com/chocolatey/choco/issues/new

@ferventcoder ferventcoder unlocked this conversation Jun 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment