PowerShell - Overview of Where-Object basic syntax and its limitations

1 min read · Updated 26 August 2024

Did this guide help you? You can support me by subscribing to the channel, sharing it, disabling your ad blocker or making a donation. Thank you!

The basic/simplified syntax that appeared with Windows PowerShell 3 is easier to understand but more limited than the standard/advanced syntax.

In my tests, it is also slightly faster in PowerShell 7 (7.4.4) and slower in Windows PowerShell 5.1.

# Standard/Advanced Syntax
Get-Service | Where-Object -FilterScript { $_.Status -eq 'running' }
# Basic/simplified syntax
Get-Service | Where-Object -Property Status -eq 'running'
# But they are most often seen in this form (without the argument after Where-Object)
Get-Service | Where-Object { $_.Status -eq 'running' }
Get-Service | Where-Object Status -eq 'running'

But the basic syntax has a few limitations.

The basic syntax can only be used for a single comparison.

# This syntax does not work
Get-Service | Where-Object -Property Status -eq 'running' -and StartType -eq 'Automatic'
# You need to use the standard syntax
Get-Service | Where-Object -FilterScript {$_.Status -eq 'running' -and $_.StartType -eq 'Automatic'}

Related links

Follow me on

Support me

Buy Me a Coffee at ko-fi.com

New site · Reference

The Windows directory tree

Native Windows folders, files and logs: what they are for, what they contain, with commands and Microsoft sources.

Browse the tree

New site · Reference

Group Policy settings

ADMX settings for Windows 10, 11, Server and applications: registry keys, PowerShell commands and use cases.

Browse the policies