Home > Articles > Software Development & Management

Windows PowerShell: Peering Through the Pipeline

You've probably done at least a little pipeline work with Windows PowerShell. Did you get the expected results every time? Timothy Warner, author of Sams Teach Yourself Windows PowerShell 5 in 24 Hours, points out how most of us go wrong when piping. Learn more powerful ways to use the pipeline.
Like this article? We recommend

Okay, PowerShell enthusiast. You say you're ready to embrace the "secret sauce" that gives Windows PowerShell its power? I've found that once an IT pro begins to understand the pipeline, his or her effectiveness with PowerShell makes dramatic gains.

By the time you finish reading this article, you should have the following PowerShell skills under your belt:

  • Listing and using the properties and methods of PowerShell objects
  • Intelligently piping the output of one PowerShell command to another
  • Troubleshooting when PowerShell gives you unexpected output

Let's begin!

The 'Pipeline' in Cmd.exe

The Windows command processor, Cmd.exe, provides a tremendously rudimentary pipeline—specifically, what's called "standard in" (STDIN) and "standard out" (STDOUT). There's also a STDERR output, but we won't worry about that here.

In a limited number of cases, we can redirect the current command output (STDIN stream) to another output in addition to the screen (STDOUT stream):

dir "C:\Windows\System32" > "C:\sys32contents.txt"

The preceding example redirects a directory listing from the console to a text file. Perhaps you've done the following to display long directory listings one screen at a time:

dir "C:\Windows\System32" | more

While redirection like these examples can be useful, it's important to understand that in both Windows and Linux pipelines, you're dealing only with text—nothing more. To be sure, you can construct some complex pipelines in Linux. Imagine being able to do the following:

Generate a table showing the top five processes, ordered by CPU consumption in descending order, listing only the process name and CPU value.

Believe it or not, performing this task in Linux is quite difficult, involving a bunch of totally separate command-line utilities like ls, grep, awk, and sed. Even so, all you have in the pipeline is "dumb" text. To do the above in Windows without bringing VBScript to the table is inconceivable.

In PowerShell, Everything Is an Object

I can't stress enough the importance of understanding PowerShell's object orientation. We can look at an object as a "three-dimensional" data structure that has descriptive attributes (called properties), as well as actions that the object can perform (called methods).

In PowerShell, we pipe output to Get-Member to view the members of an object. Check this out:

Get-Service | Get-Member

   TypeName: System.ServiceProcess.ServiceController

Name                      MemberType    Definition
----                      ----------    ----------
Name                      AliasProperty Name = ServiceName
Close                     Method        void Close()
Pause                     Method        void Pause()
Refresh                   Method        void Refresh()
Start                     Method        void Start(), void Start(string[] args)
Stop                      Method        void Stop()
DependentServices         Property      System.ServiceProcess.ServiceControl...
DisplayName               Property      string DisplayName {get;set;}
MachineName               Property      string MachineName {get;set;}
ServiceHandle             Property      System.Runtime.InteropServices.SafeH...
ServiceName               Property      string ServiceName {get;set;}
Status                    Property      System.ServiceProcess.ServiceControl...
ToString                  ScriptMethod  System.Object ToString();

Don't be blown away by the member list. What you see above is actually a truncation of the full output. I just want you to get the feel for this now.

Let me draw your attention to the object data type that's produced by Get-Service:


IT pros tend to use the last part of an object name. Thus, we can say that Get-Service spits out ServiceController objects. Under the hood, ServiceController is a .NET Framework class. You can look it up on the Microsoft Developer Network (MSDN) website.

When you run Get-Service normally, you see a data table like the following (again, I'm truncating output to save space and spare your eyes):


Status   Name               DisplayName
------   ----               -----------
Running  AdobeARMservice    Adobe Acrobat Update Service
Stopped  AeLookupSvc        Application Experience
Stopped  ALG                Application Layer Gateway Service
Running  AMD External Ev... AMD External Events Utility
Stopped  AppIDSvc           Application Identity
Running  Appinfo            Application Information
Running  Apple Mobile De... Apple Mobile Device Service

This is a list of ServiceController objects that the Microsoft folks call a collection. The three columns (Status, Name, and DisplayName) are selected properties from each ServiceController object. The output shows seven ServiceController instances from the entire collection. Do you see how the vocabulary fits together?

'Bookend' Cmdlets

In my opinion, the easiest way to start understanding the PowerShell pipeline is to combine what I call "bookend" cmdlets, which operate directly on the same kinds of objects. For instance, let's say that we want to stop the Spooler service on our computer. We can do this with one line of PowerShell code:

Get-Service -Name spooler | Stop-Service

Likewise, we can start the service:

Get-Service -Name spooler | Start-Service

Interesting. In this case, we already know what object type is produced by Get-Service, but if you aren't sure, you can use the GetType() built-in method:

$spool = Get-Service -Name spooler

IsPublic IsSerial Name                                     BaseType
-------- -------- ----                                     --------
True     False    ServiceController                        System.ComponentM...

Let's turn to the Stop-Service help to investigate how this cmdlet might accept inbound ServiceController objects:

Get-Help Stop-Service -Parameter InputObject

-InputObject <ServiceController[]>
    Specifies ServiceController objects representing the services to be
    stopped. Enter a variable that contains the objects, or type a command or
    expression that gets the objects.

    Required?                    true
    Position?                    1
    Default value
    Accept pipeline input?       true (ByValue)
    Accept wildcard characters?  false

Admittedly, I'm "cherry picking" my attributes. I knew in advance that Stop-Service had a parameter named InputObject that accepts ServiceController objects. But the point is the same.

I want you to notice this line:

-InputObject <ServiceController[]>

What this tells us is that the Stop-Service parameter named InputObject expects ServiceController objects as input. Now look at the following line in the parameter's attribute table:

Accept pipeline input?       true (ByValue)

This is a crucial parameter attribute to understand when we face the PowerShell pipeline. We read that InputObject can in fact accept input (not all parameters can), and it does so ByValue, which really means "by object type." Thus, we see that feeding ServiceController objects to Get-Service fits hand-in-glove with the Stop-Service and Start-Service cmdlets by virtual of the target cmdlet's InputType parameter.

More About Parameter Binding

If you understand what I've explained thus far, you are most of the way toward mastering the Windows PowerShell pipeline. We've learned that PowerShell uses parameter binding to take input from the previous cmdlet and feed it to the next cmdlet in the pipeline.

PowerShell takes care of the binding itself, although you can "help it along" manually if necessary. Although I've found that the ByValue binding type is by far the most common, some cmdlet parameters can accept input ByPropertyName.

I've discovered that PowerShell tends to fall back on PropertyName binding when or if it encounters problems in doing so by value. When I say that PowerShell attempts a bind by property name, I mean that the receiving cmdlet only looks for an output data field (property) with a name that's understandable. Yes, it's that simple!

Let's try a practical example. Create a simple comma-separated value (CSV) file named spooler.csv that contains the following data:


Now let's import the CSV and feed our spooler service data to Stop-Service:

Import-Csv -Path D:\spooler.csv | Stop-Service -PassThru

What happened? You should have seen what Windows PowerShell MVP Jason Helmick calls "blood on the screen." In other words, PowerShell first looked to bind on a ServiceController object; failing that, it looked for an output object property called "Name." No go there, either, so we are hosed.

Let's look at the -Name parameter of the Stop-Service cmdlet:

Get-Help Stop-Service -Parameter Name

-Name <String[]>
    Specifies the service names of the services to be stopped. Wildcards are

    The parameter name is optional. You can use "Name" or its alias,
    "ServiceName", or you can omit the parameter name.

    Required?                    true
    Position?                    1
    Default value
    Accept pipeline input?       true (ByPropertyName, ByValue)
    Accept wildcard characters?  true

By investigating the previous output, we see that the Stop-Service -Name parameter a) expects to receive string values; and b) can accept pipeline input either by property name or by value.

I can tell you that the Import-Csv import gives you a PSCustomObject collection that consists of (drum roll, please) string data. Therefore, to fix the problem, we simply need to rename the column heading in our CSV file:


Done and done.

Troubleshooting and Conclusion

I'm rapidly running out of "white space," so I need to wrap this up. PowerShell MVP Don Jones gave me the best advice concerning how to troubleshoot unexpected pipeline output. He said that you should a) remove the last element from the pipeline; and b) run Get-Member to see what kind of object you're getting.

For example, the following pipeline doesn't give me the CSV I want:

Get-Service | Format-Table -Property ServiceName, Status | Export-Csv -Path "D:\services.csv"

When I open the CSV, all I see is a bunch of formatting codes. Blech! Let's remove the last part of the pipeline and run a Get-Member. Now I get two .NET object classes:


Aha! So this is why Don Jones taught me to "filter left, format right"!

I hope you found this article informative. Happy PowerShelling!

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020