Software Deployment

atsecurity,

It sounds like an aspect of Winzip is still open when you're calling the uninstall. The tray icon/helper springs to mind.
Have a look in Task Manager to see if you can see anything obvious.

It may just require a taskkill to close this down before running your uninstall.

As VBScab says "Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you."

Hope this helps,

Dunnpy

Nothing is running in the background no tray icon nothing. no services. this is a clean machine with nothing more then the OS on it. just a test machine where i test software. but it has been reloaded fresh everytime for a new test.

ORIGINAL: atssecurity
Nothing is running in the background no tray icon nothing. no services. this is a clean machine with nothing more then the OS on it. just a test machine where i test software. but it has been reloaded fresh everytime for a new test. Well, *something* is holding that file open or, at least, WI *thinks* that's the case. Run ProcMon while you uninstall and when you get prompted with the error, see what file activity has taken place.

File activity is showing nothing more than winzip going through the process of trying to remove itself. gets to that point and stops. i have all the options turned on. nothing is referring to winzip or that file that is out of the ordinary nor anything running that would prevent that file from running. i don't see how it would be running anyways as its nothing more then a help file.

Another nice utility I keep on my pen drive is WhoLockMe. It shows who (user) and what (process) has a file open.

Sounds like it's something similar to as at http://itninja.com/question/summation-lg-gold-2.5.204

So as i am not the most savy person

Preventing the CA from being executed during a repair (ex. by adding a condition as NOT REINSTALL) or just preventing it from being executed at all; condition to resolve to false (ex. 1=0) or remove the CA from the InstallExecuteSequence table and the repair is a success.
This time any running winzip process will also be closed automatically to perform the repair without any files in-use.


how do you apply that to the uninstall command? is this a registry change or where does this get changed?

ORIGINAL: atssecurity
how do you apply that to the uninstall command? is this a registry change or where does this get changed? Use the condition "IF REMOVE ~= "ALL"

so this would be Winzip32.exe /uninstallx "IF REMOVE ~= "ALL"

First find out which process that is locking the winzip.chm file.
Run the uninstall string and when you get the error message fire up process explorer, hite CTRL-F and search for winzip.chm.

Hi...

Since i had the same problem previously ,with winzip11... the process which holds is EXPLORER.EXE it clearly shows in process monitor tool...

so use kill process Vb script ,this will kill the process and then it uninstalls and explorer.exe starts again... then it will be a clean uninstall of the winzip...

hope it gets the solution...

thanks... [:)]

ORIGINAL: atssecurity
so this would be Winzip32.exe /uninstallx "IF REMOVE ~= "ALL" Apologies, on two counts. One, that I missed this question somehow and two, I missed the fact that you're not using an MSI, but the executable. If you were using the MSI, you would add this condition to the Custom Action mentioned in the link which Kim posted.