/build/static/layout/Breadcrumb_cap_w.png

Windows Installer Bug with old WinZip versions

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:

 

http://216.115.86.232/software/winzip/winzip-1/16-89

 

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   [ + ] Show 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. - anonymous_9363 10 years ago
  • 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 - drose23 10 years ago

Answers (2)

Posted by: ekgcorp 10 years ago
10th Degree Black Belt
1

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.

Posted by: piyushnasa 10 years ago
Red Belt
1

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.

 

Cheers,

 Piyush

 

 http://msiworld.blogspot.com.au/

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ