Prerequisite extraction folder not correct when MSI running under SYSTEM account - Advanced Installer Community
sbaird
Posts: 57
Joined: Tue Sep 01, 2015 2:08 pm

Prerequisite extraction folder not correct when MSI running under SYSTEM account

When an MSI contains a feature-based or post-install prerequisite, and that MSI is run under the SYSTEM account (such as when using Group Policy Software Installation), bad things happen. The Download/extraction folder set on the Prerequisites page is not honored. Instead, the prerequisites are extracted to C:\<Company_Name>\<MSI_Name>\prerequisites\.... Also, there are two cmd.exe processes left after the install that are pegging the CPU (100% usage).

There are multiple ways to get into this state. The easiest is probably to create an MSI project with any feature-based prerequisite and run the MSI using the SYSTEM account (you can use a scheduled task to do this). Another way is to have two MSI projects: A and B. A contains a feature-based prerequisite, and B contains A as a feature-based prerequisite. Run B in silent mode, which causes the "aipackagechainer" to be launched using the SYSTEM account, and thus A will be in the bad state. This also happens if a deferred custom action is used to launch the second MSI asynchronously and the Run under the LocalSystem account... option is checked.

Because of this issue, we cannot deploy using Group Policy.
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Prerequisite extraction folder not correct when MSI running under SYSTEM account

Hi,

I tested the scenario and I was able to reproduce the behavior.

The redirection of the prerequisites' extraction path is normal. Since the setup is launched under the SYSTEM account the extract location will be resolved to the following path:

Code: Select all

C:\Windows\System32\config\systemprofile\AppData\Roaming\
Due to a security measure, Advanced Installer prevents the extraction to "Windows" folder and the extraction path is changed to a non-system folder. As a workaround, you can use a per-machine extract location for the prerequisites (e.g. "[CommonAppDataFolder][|Manufacturer]\[|ProductName]\prerequisites").

The two "cmd.exe" processes are, indeed, left after the installation and it seems to be an Advanced Installer issue. However, we need more time to investigate this and we'll get back to you as soon as we have a conclusive answer.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
sbaird
Posts: 57
Joined: Tue Sep 01, 2015 2:08 pm

Re: Prerequisite extraction folder not correct when MSI running under SYSTEM account

As a workaround, you can use a per-machine extract location for the prerequisites (e.g. "[CommonAppDataFolder][|Manufacturer]\[|ProductName]\prerequisites").
I was already using [CommonAppDataFolder] when I discovered the problem -- your suggestion does not work. I've also tried a literal path, such as "C:\ProgramData\..." which also does not work.
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Prerequisite extraction folder not correct when MSI running under SYSTEM account

Hi,

Indeed, the installer ignores the extract location written for the prerequisites when it runs under the SYSTEM account. I'm not sure why this happens, but I will investigate this and come back when I will have a conclusive answer.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Prerequisite extraction folder not correct when MSI running under SYSTEM account

Hello,

This was fixed in version 12.5 of Advanced Installer released on October 21st, 2015.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”