This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: WaitForSingleObject() not waiting for setup.exe to exit(IS2016 SP2)
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 08, 2017
04:34 AM
WaitForSingleObject() not waiting for setup.exe to exit(IS2016 SP2)
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
- Tags:
- installshiled2016sp2
(6) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 14, 2018
01:49 PM
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.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 15, 2018
01:14 AM
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
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
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 29, 2018
05:29 AM
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.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 29, 2018
06:24 AM
My setup is an basic MSI as well, so it seems to work.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 30, 2018
01:10 AM
Georg1 wrote:
My setup is an basic MSI as well, so it seems to work.
Thank you. /clone_wait is working.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 26, 2018
08:07 AM
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
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
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)