Check for more than 1 running instance of powershell script launched using ".\scriptName.ps1"

Question

The below thread explains how to check for more than 1 instance of a powershell script using get-wmiobject win32_process

Assure only 1 instance of PowerShell Script is Running at any given Time

For get-wmiobject win32_process to list a running powershell script, that script needs to be invoked using powershell.exe scriptName.ps1. How can I check for more than 1 instance of the script running where the script was invoked using .\scriptName.ps1?

Your GWMI call is the same as Get-Process essentially. All it tells you is whether the powershell.exe process is running, not whether a specific script is running. — Maximilian Burszley
– Maximilian Burszley, Commented Nov 14, 2017 at 21:01
On the contraty, GWMI allows me to see not only that the powershell.exe process is running but also shows me the exact commandline (i.e. with arguments), whereas Get-Process only shows me that the powershell.exe is running — Alex Rodrigues
– Alex Rodrigues, Commented Nov 16, 2017 at 1:47

zdan · Accepted Answer · 2017-11-14 21:31:40Z

0

You could use the below and see if the result is > 1

(Get-WmiObject Win32_Process | select commandline | where {$_ -ilike "*scriptName.ps1*"} | measure).Count

edited Nov 14, 2017 at 21:31

zdan

29.6k7 gold badges62 silver badges73 bronze badges

answered Nov 14, 2017 at 21:17

user8168912

692 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

zdan Over a year ago

That could work but has 2 problems: 1- If someone opens a powershell window and then runs the script from the cmd line, this won't detect it. 2 - If someone tries to edit it, by say typing notepad scriptName.ps1, you'll get a false positive.

Maximilian Burszley Over a year ago

Comparison operators are case-insensitive by default. I'm really not sure why they made explicit operators for it

Alex Rodrigues Over a year ago

Get-WmiObject Win32_Process requires that one invoke a powershell script using "powershell.exe <scriptName>", like @zdan said

Collectives™ on Stack Overflow

Check for more than 1 running instance of powershell script launched using ".\scriptName.ps1"

1 Answer 1

3 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related