DetectProcess launch condition fails for passive or quiet - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

MarkEverest
Posts: 3
Joined: Mon Feb 08, 2010 6:31 pm

DetectProcess launch condition fails for passive or quiet

I want to check that a process is not running when I run the installer. I have got this to work by:
  • Adding a DetectProcess to the Custom Actions InstallUISequence -> Begin with Action Data of 'notepad.exe'
  • Adding a custom launch condition with a condition of 'AI_PROCESS_STATE = "Stopped"' and a description of 'Please close notepad'
This works for attended installations but fails for /passive and /quiet installations - for quiet and passive the log always says "Please close notepad" even when notepad is not running.

Any ideas?
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: DetectProcess launch condition fails for passive or quie

Hello,

To solve this you can try to share( hold Shift + drag & drop ) the custom action from the InstallUISequence Begin standard action with the InstallExecuteSequence Begin as well. Also, you should enable the "Execute if present in both sequence tables" scheduling option.

Here is the user guide article that explains this.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
MarkEverest
Posts: 3
Joined: Mon Feb 08, 2010 6:31 pm

Re: DetectProcess launch condition fails for passive or quie

Perfect - that has sorted it.

Thanks :)

Return to “Common Problems”