November 15th, 2005

Waiting for msiexec.exe to Finish

Heath Stewart
Principal Software Engineer

Since Windows Installer 1.0 was first released, msiexec.exe has always run in the Windows subsystem. That means that when it is executed from the console or by a batch script control returns to the console or script immediately. If you depend upon the %ERRORLEVEL% variable being set accordingly it won’t be.

In this scenario I like to use start /wait from the command line or a batch script. This will create the process and wait for it to exit, and the return code from the process is passed through and returned from the start command such that %ERRORLEVEL% is set accordingly. Just type start /wait before the command line you’d normally pass to msiexec.exe like in the following example:

start /wait msiexec.exe /i netfx.msi /l*v netfx.log

A batch script would be blocked, then, until msiexec.exe finishes. Programmatically this is no different than invoking msiexec.exe with CreateProcess and waiting for the process handle to be signaled with WaitForSingleObject with no timeout.

Author

Heath Stewart
Principal Software Engineer

Heath is an application architect and developer, looking to help educate others to learn professional development. Besides designing and developing applications he enjoys writing about intermediate and advanced topics. Heath also consults for deployment packages and scenarios within Microsoft and for external customers.

1 comment

Discussion is closed. Login to edit/delete existing comments.

  • Jeevan Jyot Singh

    Great help. Thanks