Author Posts

September 16, 2014 at 1:03 pm

I'm running a script that kicks off many different processes. From what I can see, all of the external process that my script kicks off have a parent process ID of the powershell.exe instance they came from. For some reason, an insane software installer starts it's standard setup.exe, terminates, waits a few seconds and spawns another setup.exe process. Because of this, my -Wait param on Start-Process won't work and neither will Wait-Process. I did find that every process that setup.exe spawns has a parent process ID of the powershell.exe instance it's running under.

I can get the powershell.exe process ID directly by just finding all IDs with a name of powershell.exe but I don't want to do that. I want to prevent a problem if another powershell.exe instance is running at the same time and my script just hanging forever. So...

Anyone know of a way to get the process ID for powershell.exe from a running script?

September 16, 2014 at 1:06 pm

I never realized it'd be this simple. There's a variable of $pid that represents the current powershell instance I can use. Now that makes me wonder if I've ever used that reserved variable and not thought about it.

September 17, 2014 at 2:44 am

🙂 I like those self-resolving issues 🙂