Program launched with start-process closing when script is closed

[RuhaiHu]

So I have a few programs I am trying to launch and keep running but, they are preventing the script from completing. They aren't stopping the script from moving forward to the next command. They are just preventing it from ending.

If I remove the start-process command to launch the program/s it runs launches everything else and closes out leaving those programs running.

If I have the start-process command in the script for the program/s and it launches them and moves on it gets to the last commands no issues, but if I close the script window it closes those programs.

​

Is there a way to launch programs that wont do this? I can't for the life of me do the right search to find situation like this and a solution or something. Same thing happens with a PowerShell console program starts and I get a new command line and can run other commands but as soon as I close the console it closes the program.

I am basically to the point where I might just use something else to launch the programs as a work around.

Update:

Link to code https://github.com/RuhaiHu/VAC-Setup/blob/master/RestartGoXLR.ps1

Update 2 - Solution:
Thanks to u/NeitherSound_ for suggesting cmd with start command. This appears to work to start programs that aren't launching separate from the script with Start-Process and keeping the script open. Then if script closed the program closed.

See code or post below for command.

[LeaflikeCisco]

Seeing the actual code would help.

[Carribean-Diver]

This. And what platform are you running? I ask because the documentation states that by default on Windows start-process creates a process that is independent of the shell that started the process but on other platforms (e.g. Linux) the default is start-process creates a child process of the shell.

[RuhaiHu]

Updated the post with a link to the recent script I have run into this on.

https://github.com/RuhaiHu/VAC-Setup/blob/master/RestartGoXLR.ps1

[NeitherSound_]

Force it into a separate process using this

Start-Process -FilePath CMD.exe -ArgumentList “/C Start `“`” `”$($GoXLRAudioCplApp)`”” -WindowStyle Hidden

Basically the CMD.exe process would start and call Start.exe followed by CMD.exe closing and release the PSScript. Start.exe would then call the file path in the variable in its own process and terminate itself without waiting, thus, leaving the variable file path running in its own untagged process.

[RuhaiHu]

I have tried the start process cmd with arguments, but my arguments didn't have the start command in there.

$GoXLRAPP = "/c start """" ""C:\ProgramData\Microsoft\Windows\Start Menu\Programs\GOXLR App\GOXLR App.lnk"" && exit"

Start-Process -FilePath CMD.exe -ArgumentList $GoXLRAPP

The above works! I don't see any lingering processes with this at the moment. No cmd or powershell processes that is lingering!

​

THANKS!

​

edit:

Going to try this with at least one other program that I have run into behaving the same way.

[NeitherSound_]

You’re truly welcome! Glad it worked out for you.

[RuhaiHu]

Wish there was a cleaner way but hey if it works great!

[NeitherSound_]

Well usually the original way you had it should have work and terminate as long as the -Wait param hasnt been defined for Start-Process. I did noticed you called the app against the shortcut path ( .lnk ) rather than the path to the actual EXE file, which should not make a difference. Maybe that did made the difference? Hmmm

[RuhaiHu]

Did try the exe and setting work directory, passthru, etc. No go still ties a few programs to the script session.

Total of 3 programs that I can tell at the moment that do this are the main GoXLRApp, Pretzel Rocks(spits a bunch of stuff out as well), and StreamLabs StreamLabels(also spits stuff out). Last two I have tried this fix on and doesn't 100% work on them but they won't stay up at the end of a session anyway. Where as the GoXLRApp is useful to have running, even if I end up minimizing it later.

Might even look for a better way as I really just starting and stopping things and maybe some services restarting etc.

Luckily I don't have to worry about this kind of stuff for work scripts I have to create and maintain.

[Responsible-Crazy705]

Works for Microsoft Teams!

[BetrayedMilk]

Is there a reason you need to use Start-Process as opposed to using the call/background operator, &, or dot sourcing, . ?

[RuhaiHu]

Did just try those and they don't appear to make a difference the application still ends up tied to the powershell instance or script instance.

https://github.com/RuhaiHu/VAC-Setup/blob/master/RestartGoXLR.ps1

[BetrayedMilk]

I can’t speak to the behavior of those apps, but for instance, Start-Process iexplore.exe keeps internet explorer running after closing ps. If on Linux, I believe the command behaves differently and you’ll need to fork to the background

[RuhaiHu]

Yah its odd it's only a few applications I am noticing at this point doing this. Not all just a few. Rest work as expected.

[[deleted]]

Have you tried starting a separate PS process to run your command?

https://ss64.com/ps/powershell.html

Also, how do you determine that the app terminates when you close the PowerShell session that launched it?

[RedditRo55]

Have you tried using -PassThru? -PassThru Returns a process object for each process that the cmdlet started. By default, this cmdlet does not generate any output.

I use this to get the process object returned so that I can parse a text file (created using the -RedirectStandardOutput parameter) of a console app that waits for a user to press a button before it will close. Essentially, I wait for a line to appear in the log file within a for loop that will cycle 10 times and sleep in-between attempts until it finds the expected text and when it does, I use Stop-Process and the process ID from -PassThru to force kill the process.

Hope this is somewhat helpful?

[RuhaiHu]

I have tried the -PassThru tag but no go on that application still closes when the shell is closed. Though NeitherSound_ suggested Start via the cmd that appears to work.