Hello everybody,
I currently trying to find the best way to update one of the application I installed with the k1000 appliance on Windows 7. I'm talking about application than you can't keep up to date with the k1000 lunention package.
I'm interested to know how you do that's.
For now I'm trying to update an application called Total Commander using the scripting function of the k1000.
I created a script called "Total Commander update to 7.57" to uninstall the software and then install it again


Task 1
Verify that the file “C:\win32app\totalcmd\TOTALCMD.exe”
On Success
Launch “C:\win32app\totalcmd\unins-Totalcmd_IHEID.exe” with params “”
Launch “$(KACE_DEPENDENCY_DIR)\Totalcmd-7.57-1_setup-IHEID.exe” with params “/S”

My script start correctly but before the software had time to uninstall the next line start and install my software again.
Is there a way to avoid this behavior ?

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


I would try running a batch file instead. Just put this in the batch file.

Totalcmd-7.57-1_setup-IHEID.exe /S
Answered 03/01/2012 by: darkhawktman
Green Belt

Please log in to comment
You could also try start /wait C:\win32app\totalcmd\unins-Totalcmd_IHEID.exe.

If worst comes to worst, you could add a manual wait:
ping -n 1 -w 5000
Would wait for 5 seconds.

Answered 03/01/2012 by: cmccracken
Orange Senior Belt

Please log in to comment
ON the "launch a program" step there is a checkbox for "wait for startup". Unless the exe is spawning another process itself and not waiting for it that would work. If it is actually an exe wrapped around another installer then try extracting the true installer and running the command for that. Use task manager to see what actually runs and wmic to see how that program was started and use that directly in your extracted package. You may also find some information out about that software here on Appdeploy.

WMIC /OUTPUT:C:\ProcessList.txt path win32_process get Caption,Processid,Commandline

Then look in the c:\processList.txt file

Or if you want a specific process name (e.g. svchost), pid, etc then something like

WMIC path win32_process get Caption,Processid,Commandline | find /I "svchost"
Answered 03/04/2012 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
Hello everyone,
Thank you for your responses.
GillySpy in fact I'm in the situation of an exe wrapped around another installer. My exe file is in charge of launch the uninstaller (an exe file) and cleaning different things I created during the install process.
This behaviour is due to the way I've packaged my software with NSIS. Am I the only one in this situation ?
What are you using to package your software ? The way you do it, make the problem disapear ?
Thanks again for your help.
Answered 03/12/2012 by: tahcor
Yellow Belt

Please log in to comment