I'm trying to silently install an application that launches once the install is completed.
Is there any command line parameter for setup.exe to stop the application launch?

Thank you for your help.

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


Try setup /?
It may give you a list of command lines you can use.
Answered 02/15/2009 by: reds4eva
Second Degree Blue Belt

Please log in to comment

What i suggest you can first try to find out wether any msi is wrapped into that setup.exe.If msi would be there then there would be a custom action which would be after InstallFinalized that would be launching any executable.Check this out first then we could analyzed more abt it..

Answered 02/16/2009 by: anks_09
Orange Senior Belt

Please log in to comment
My first post on this forum...
Not enough information here, let me see if I can expand things a bit.
- There is no MSI files present or created during the install, it's just a setup.exe with .cab file.
- I have not been able to find a command line variable to stop application launch
- I would like to know if lines can be inserted into the setup.iss file to prevent the application launch
- I'm using setup.exe /s /sms /f1"z:\setup.iss" /f2"C:\Install-app.log" This works fine apart from starting the application on completion.
- the application is eSentinel Roster, a resource scheduling application

Once again thanks for all the help.

Answered 02/16/2009 by: RussC
Yellow Belt

Please log in to comment
How about launching a script to check for the process being started and terminate it at once?
run it prior to launching setup.exe

(You may want to change the MaxAllowedRunTime and WatchForProcessName value)

Const MaxAllowedRunTime = 120 '// if process has not started in 120 seconds then exit script
Const WatchForProcessName = "notepad.exe" '// process name to look for

Dim WaitForNotificationRequest, WMIService, Sink

Set WMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" _
& ".\root\cimv2")

Set Sink = WScript.CreateObject("WbemScripting.SWbemSink","SINK_")


Sub WatchForProcessNameExecutionAndTerminate(Name)
Dim WMIQuery, ElapsedRunTime

WMIQuery = "SELECT * FROM __InstanceCreationEvent " & _
"WITHIN 1 WHERE TargetInstance ISA 'Win32_Process' " & _
"AND TargetInstance.Name = '" & Name & "'"

WMIService.ExecNotificationQueryAsync Sink, WMIQuery

ElapsedRunTime = 0 : WaitForNotificationRequest = True

While WaitForNotificationRequest
ElapsedRunTime = ElapsedRunTime + 1

If ElapsedRunTime > MaxAllowedRunTime Then
End If
End Sub

Sub SINK_OnObjectReady(wmiObject, wmiAsyncContext)
Call TerminateProcessByProcessId(wmiObject.TargetInstance.ProcessId)

End Sub

Sub EndNotificationRequest()
WaitForNotificationRequest = False

End Sub

Function TerminateProcessByProcessId(ProcessId)
Dim ProcessList, Process

Set ProcessList = WMIService.ExecQuery("SELECT * FROM Win32_Process WHERE ProcessId = '" & ProcessId & "'")
For Each Process in ProcessList
End Function
Answered 02/16/2009 by: AngelD
Red Belt

Please log in to comment
You'll be here 'til Doomsday with this. Re-package it! :)
Answered 02/17/2009 by: VBScab
Red Belt

Please log in to comment
You could start the setup with:

start /wait setup.exe /s /SMS /f1"z:\setup.iss" /f2"C:\Install-app.log"
I have also seen different results with /SMS needing to be in ALL CAPS to work properly on some installs.
Answered 02/17/2009 by: Foleymon
Orange Senior Belt

Please log in to comment