WaitForSingleObject() not waiting for setup.exe to exit(IS2016 SP2)

[vijaykumbhani]

Hi Team.

Previously, I am used IS2014 Professional.
The WaitForSingleObject() is waiting for setup.exe to exit. (working)

After that,
I have upgraded from IS2014 Professional to IS2016 SP2 Professional. (The .ism file has been upgraded automatically when open the file in IS2016 SP2 & build installer)
The WaitForSingleObject() is not waiting for setup.exe to exit (not working)

The WaitForSingleObject() is Microsoft API.
https://msdn.microsoft.com/en-us/library/windows/desktop/ms687032(v=vs.85).aspx

Could you please check on this, This issue has blocked my work.

Thanks in advance.

Thanks!
Vijay Kumbhani

[scottd72]

I am having the same experience using WaitForSingleObject() on a setup.exe built with Installshield 2016 SP2. I wonder if this is fixed in 2018.

[Georg1]

I had the same problem some time ago after updating to IS2016

the clone_wait parameter fixed it in my case

https://flexeracommunity.force.com/customer/articles/en_US/ISSUE/Installer-Does-Not-Wait-For-Child-Process-By-Command-Line-start-wait-setup-exe

[vijaykumbhani]

Georg1 wrote:
I had the same problem some time ago after updating to IS2016

the clone_wait parameter fixed it in my case

https://flexeracommunity.force.com/customer/articles/en_US/ISSUE/Installer-Does-Not-Wait-For-Child-Process-By-Command-Line-start-wait-setup-exe

/clone_wait -- InstallScript -- This parameter indicates that the original setup should wait for the cloned setup process to complete before exiting.

based on documentation. Clone_Wait for InstallSctipt. I am using BASIC MSI project.

please let me know, is it working for Basic MSI project.

[Georg1]

My setup is an basic MSI as well, so it seems to work.

[vijaykumbhani]

Georg1 wrote:
My setup is an basic MSI as well, so it seems to work.

Thank you. /clone_wait is working.

[jameslite]

I would guess setup.exe is starting another process and then exiting. I seriously doubt there is a bug that causes WFSO to return prematurely. What do you find in the Task Manager process list? I take it you're initializing STARTUPINFO in the code you didn't show?

Tip: Don't use printf to print plain old strings. Use puts for that. The danger with printf is that you might add an unescaped % sign later and unintentionally create a bogus format string. liteblue