Issue with msiexec.exe process - Advanced Installer Community
ramit
Posts: 90
Joined: Thu Dec 18, 2008 11:51 am

Issue with msiexec.exe process

Hi,

When I am running the installer in Process (In Task manager) 2 new process get added

1) msiexec.exe - in SYSTEM user name
2) msiexec.exe - in Local account user name

And when installer gets completed, the process for “msiexec.exe - in Local account user name” will be stopped,
but for Process “msiexec.exe - in SYSTEM user name” will be still running.

I did not understand why.

Please suggest.

Thanks
Amit
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Issue with msiexec.exe process

Hi Amit,

A number of msiexec processes can be running during an installation. The reason for this is that Windows Installer uses a client-server model for performing installations.
Additionally for security reasons, Windows Installer hosts DLL and script custom actions in a "sandbox" process.

Depending on how the install was initiated, one of the msiexec processes can be the client process and the other one is a Windows Installer service.
After the intallation finishes the process that runs under the SYSTEM account will hang for a while, but this is just the normal Windows behavior.

Also other msiexec processes can appear along the installation if the package contains any custom actions, these will be created as child processes.

Please let us know if you have other questions.

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
uday1kiran
Posts: 1
Joined: Sun May 18, 2014 6:52 am

Re: Issue with msiexec.exe process

In any Forum, the client -server model is mentioned for this question.

Could you please elaborate this model for windows installer service.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Issue with msiexec.exe process

Hello and welcome to Advanced Installer forums,

When an MSI is launched, usually Windows Installer open two msiexec processes: a client process and a server process. The client process handles all UI actions (contained by the "InstallUISequence" table). These actions appears in the installation log file preceded by the "(c)' characters group. The server process handles all installation actions contained by the "InstallExecuteSequence" table. These actions appears in the installation log file preceded by the "(s)' characters group. Additionally, Windows Installer could open another process for every custom action launched by the installation package (a DLL custom action, a VBS custom action, etc.).

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”