I'm working on a script that will update WinZip from various previous versions, to the current version of 17.5.10480.  Installing the new version by itself works fine.  Installing on a machine with an older version, causes Windows Installer to crash.  I can't seem to find anything on this in particular except for the 4th deployment tip here:


There has to be a way around this, other than upgrading current versions in place (which I can't do).

Does anyone have additional details on this bug, or how I can resolve?  I wasn't able to find release notes on this version which may reference more detail.

2 Comments   [ - ] Hide Comments


  • It wasn't very helpful of the tip's poster to do absolutely ZERO research into finding out what was causing the WI crash. How hard can that be? That job now falls to you. I'm 99% certain that a CA will be the culprit but regrettably I don't have the time to help you out.
  • Thanks for all the input guys - surprisingly this has not recurred. It did on about 50% of the first deployment wave, but re-attempts on those and further deployments haven't yet suffered this issue. I do have verbose logging setup by default, and will post back with additional details if it happens again
Please log in to comment

Answer this question or Comment on this question for clarity



Have you tried the following?

- Installing vendor msi unedited

- checking out the UninstallString in HKLM\software\microsoft\windows\currentversion\uninstall\{winzip guid}

- confirming vendor's uninstall works without silently switch (I realize this is highly unlikely fail, but if it does Im sure the vendor would want to know)

- Check component table, InstallExecuteSequence, CustomActions for any conditions that would Run during REMOVE

There could also be some LaunchConditions not meet, after all there are a ton of Properties being set via CMD on the first couple deployment tips.

Answered 08/08/2013 by: ekgcorp
Tenth Degree Black Belt

Please log in to comment

Create a log and you will get to know where the issue lies. Post the issue here then someone will try to resolve it.

I  would suggest you to check if the upgrade is happening correctly.

If previous package is leaving behind any junk values then you can remove them from your package or by script.






Answered 08/16/2013 by: piyushnasa
Red Belt

Please log in to comment