Home > PowerShell, PowerShell Quick Tip > PowerShell Quick Tip: Creating wide tables with PowerShell

PowerShell Quick Tip: Creating wide tables with PowerShell

November 11, 2010 Leave a comment Go to comments

A few weeks back I took a trip to Columbus, Ohio where I had the opportunity to meet with the members of the Central Ohio PowerShell Users Group and talk about PowerShell and PowerGUI®.  During that event, one of the attendees highlighted a problem they were having.  The problem he highlighted is a fairly common one, so I wanted to share the problem and solution here.

When using PowerShell to generate tabular output, the table that is generated is limited by the width of the buffer.  This is intentional so that the tables always fit in your console window so that they can be easily understood, and for the most part this doesn’t get in the way too much because you can control which columns are shown in the table so that you get the data that is most important to you or you can use Format-List to generate list output when you really want a lot of data.  It can get in the way though if you want to share data from a large table with someone else, store data in a text file for archival purposes, etc.  In these cases you are faced with a challenge because Format-Table does not appear to allow you to create large tables like this due to a few issues that get in your way.

Issue #1: PowerShell truncates table output by default

Let’s say you want to create a table showing a list of aliases for Invoke commands and you want to view all properties for those aliases.  The command to do this seems pretty straightforward, simply calling Get-Alias -Definition Invoke-* and passing the results to Format-Table -Property * to show all of the columns.  Here are the results of that command, showing a table with column names that span multiple lines and rows with data that is not useful:


As you can see, the content of the table is truncated so you can’t really tell what the data is in the table, and if you output the results of that command to a file where the lines can be longer you still get the same results.

Issue #2: Auto-sized tables are limited to the width of your screen buffer

If you try to solve this problem by looking at the help for Format-Table, you may come across the AutoSize parameter.  The AutoSize parameter allows you to tell PowerShell that you want the formatter to automatically size the table columns, showing as much data as possible.  Here is what happens if you add the AutoSize parameter to the same command you just ran:


This is on the right track for what you are after, but notice the warning text that is output at the top of the resulting table.  It indicates that 10 columns do not fit into the display and were removed.  If you pipe the results of this command to Out-File, PowerShell will simply pass what you see on the screen to the file you are writing to, which is not sufficient for your needs.

Solution: Strings are not subject to the limitations of other objects in PowerShell

When you pass the results of Get-Alias to Format-Table, the Alias data is converted into objects that describe how the table should look.  These objects are then passed implicitly to the Out-Default cmdlet which renders the objects according to their format configuration as well as the current console configuration.  In fact, every PowerShell command you run ends with the results being implicitly passed to Out-Default.  Even if you pass the results of our Format-Table call to Out-File instead, Out-File will render the objects according to their format configuration and the current console configuration.  This is the limitation that is making this seemingly simple task so difficult.  What we need to do then is to make sure that the data that is sent to Out-File or Out-Default is pre-formatted so that it is not limited by the size of the screen buffer.  How do you do that you ask?  The answer is simple: use Out-String.

Out-String is a cmdlet that allows you to convert any output to string format, and you can specify the width of that string using the Width parameter which allows you to exceed the limitations of the PowerShell console buffer size.  When strings are passed into Out-Default and Out-File they are simply written as is without any truncation or automatic text wrapping.  With that additional piece of knowledge you can pass the results of your Format-Table cmdlet call to Out-String using a width that is large enough for the table output, which successfully forces the objects to be rendered with the width that you want without having to change the buffer size.

Here is a screenshot showing what happens when you pass your Format-Table output to Out-String, specifying a width of 4096 characters:


That might not look very useful either, but look what happens when you take this one step further and pass the results to Out-File.  Here is the command to do this:

Get-Alias -Definition Invoke-* `
| Format-Table -Property * -AutoSize `
| Out-String -Width 4096 `
| Out-File C:\aliases.txt

Opening the resulting aliases.txt file shows the following contents:


This is only showing part of the results, but did you notice the horizontal scroll bar at the bottom of the window?  It illustrates that you have achieved your goal, creating a table wide enough to show all data in the table inside of a text file that can then be sent to others, stored for archival logging purposes, etc.

Sidebar: If you have a specific property that contains a collection of items, that property may still show an ellipsis in the file produced here if the number of items in that collection exceeds the number assigned to the built-in $FormatEnumerationLimit variable.  In this case, if you want to see the entire collection of items, you should temporarily change the value in $FormatEnumerationLimit to something large enough to show your collection (-1 if you want to see all items) and then run a command similar to what I have shown you above.  The default value of $FormatEnumerationLimit is 4, which can be limiting when generating a file like this.  Increasing this value will give you a full report of what you have in the data you are processing.

With that knowledge in hand, the takeaway for you here is to make sure that you autosize your Format-Table results and that you pass them to Out-String with an appropriate width before you write it to a file if you want to output large tables in text format.

Thanks for listening!

Kirk out.

About these ads
  1. November 11, 2010 at 12:04 pm

    Or use Export-CSV. ;)


    • Kirk Munro
      November 11, 2010 at 12:36 pm

      Sure, but Export-CSV is only useful if you’re going to Excel or some other product that accepts CSV files with your data. Being able to export tables as well formatted text files is a completely separate need that needs to be filled as well.


  2. DPC
    November 11, 2010 at 6:09 pm

    Great Kirk – thanks,

    So the take away from this is –

    [1] Collect and refine your deliverable first –
    [1a] Using Get-xxx, Select, Sort and other cmdlets upstream in the pipeline
    [1b] Shape the presentation of the payload using Format-Table,
    Format-List, Format-Wide … (or possibly with an expression in Select)
    [1c] Lastly send this to Out-String to get each row on the console without breaking up each row at the 79th column (or routing it to a file as well).


    [2a] Are there any caveats to the behavior of Out-String such as –
    [2b] Null values comprising what comes out?
    [2c] Will the output be padded with spaces if the data (in this example of 4,096) doesn’t extend as wide as 4,096.
    [2d] If one wants to display the last 100 lines of 80 meg file of a wide file to the console, one might type –

    get-content {filename} | select-object -last 100 | out-String -width 4096



    • Kirk Munro
      November 11, 2010 at 6:40 pm

      Hi David,

      Regarding the take away, you got it.

      Now to your questions:
      2b. $null is interpreted as an empty string when passed to Out-String.
      2c. Output is not padded to the value you specify in Width. There may be some padding though as the table formatter lines up columns (for example, if the value in the last column is null, there will be spaces to make the width of that column equal to the width of all other values in that column.
      2d. Almost. Only use Out-String when you want to specifically convert to a string because you are pushing data into a file, an email message, etc. To view the last 100 lines of any file, just pipe the results of Get-Content to Select-Object -Last 100. If you want to only get a preview of those lines (i.e. control wrapping) in your console, use the trick I just shared in my answer to your question on the previous post. Or if you want to search the file for rows containing something specific use Select-String to limit the output to those rows.

      Let me know if you have more questions.

      Kirk out.


  3. Rich Beckett
    November 12, 2010 at 9:42 am

    Thanks Kirk. That was very informative and helpful. As usual, you were very clear and concise. David’s take away was also good.


  4. November 14, 2010 at 6:29 am

    Without the parameter -Property * I didn’t get all the column IN SQLPSX.
    Now I get all the columns
    $datarow | ft -Property * -auto | Out-string -width 10000 -stream
    and a few addition too, as described in


  5. DPC
    November 14, 2010 at 3:21 pm

    I’ve been testing the recommendations (thank you for your advise) and for one specific combination, the above settings aren’t quite as effective as needed.


    Here’s the real test:

    *-Create an ASCII file in notepad with 3 rows/lines of text in the file.

    These lines of text represent the column values from position 1 to column 200 or so. For our example, I can only provide a column width of 79+ for this web page, but on your pc take each row out a couple hundred columns.

    Save the file to c:\1-to-200.txt
    Then PowerShell ‘type’ the file with the PS commands:

    Get-Content C:\1-to-200.txt

    How can you tell PowerShell to display all 200+ columns only on three rows?
    For the other constraints, see above



    • Kirk Munro
      November 15, 2010 at 8:26 am

      In this case, when you call Get-Content you are actually getting 3 rows back. Those rows are automatically wrapping in PowerShell because they exceed the size of the buffer in the PowerShell console. You can’t tell PowerShell to display all of the contents on single lines without changing your buffer size.

      If you want to eliminate that wrapping though and only see enough characters from each line that you don’t get the wrapping in the console, pass the results of Get-Content to ForEach-Object and truncate the output yourself, like this:

      Get-Content filename.txt | ForEach-Object {
      if ($_.Length -gt $host.UI.RawUI.BufferSize.Width) {
      (-join $_[0..($host.UI.RawUI.BufferSize.Width – 5)]) + ‘…’
      } else {

      That’s the best you will be able to do without changing your buffer size.

      Kirk out.


  6. Peter Dornauer
    July 20, 2011 at 6:58 pm


    I’m just learning Power-Shell and run now exactly into this, because i wanna evaluate Robocopy Logs. In this Logs there are lots of pathnames longer than 220 Chars.

    So i was frustrated, as i have seen the output of my commands is cropped to the window length of PS.

    And here came your Site into the Story….

    THANK YOU KIRK, you saved my belief that PS is a great piece of SW.

    Regards from Vienna



    • Kirk Munro
      July 21, 2011 at 8:47 am

      Thanks for the great feedback Peter, that made my day. :)


  7. Nik Conwell
    January 25, 2012 at 11:18 am

    Hi. Great post, worked fine for me on the powershell cmdline but when I run powershell through perl, I still get things truncated at 79 characters…

    get-counter -counter “\\server\MSExchange RPCClientAccess\RPC Requests”

    If I add | out-string -width 120 it works perfectly fine in the powershell console.

    But, if I run it via a perl script which runs powershell as c:\windows\…\powershell.exe -PSConsoleFile “c:\Program Files\…\exshell.psc1″ -command “[above command | out-string -width 120]” things still get truncated at 79…


    • Kirk Munro
      February 8, 2012 at 7:54 pm

      Hi Nik,

      Don’t forget, between your call to Get-Counter and Out-String, you need to use Format-Table * -AutoSize to get the proper results.

      For example:

      C:\windows\…\powershell.exe -PSConsoleFile “C:\Program Files\…\exshell.psc1″ -Command “Get-Counter -Counter “”\\server\MSExchange RPCClientAccess\RPC Requests”” | Format-Table * -AutoSize | Out-String -Width 120″

      I hope this helps.

      Kirk out.


  8. Dexter
    February 8, 2012 at 6:09 pm

    I have been working on this all day, This is awesome. finally got what I needed and a full explanation of why it hasn’t been working all day. Wish I’d have founf this earlier today.



    • Kirk Munro
      February 8, 2012 at 7:43 pm

      Glad it helped you out Dexter! :)


  9. Parag
    April 11, 2012 at 1:10 am

    Thanks Kirk, this was just the thing i was looking for. Keep up the good work.


    • Kirk Munro
      April 11, 2012 at 8:36 pm

      Thanks for letting me know it helped. I love this trick!

      Kirk out.


  10. Jaa5
    May 4, 2012 at 10:55 am

    Hi, need some quick help here. How can I get this output to all be on 1 line? (keeping 1 liner approach).

    gci “C:\Program Files\” -recurse -force | ? {!$_.PSIsContainer -and $_.lastwritetime -gt (get-date).addDays(-365)} | foreach {$_.FullName, ($_.lastwritetime).ToShortDateString()} | ft -a


    • Kirk Munro
      May 4, 2012 at 3:33 pm


      Your one-liner is emitting two separate objects, which is why they appear on different lines. You want one object, so use select instead of foreach and build the object you want, like this:

      gci “C:\Program Files\” -recurse -force | ? {!$_.PSIsContainer -and $_.lastwritetime -gt (get-date).addDays(-365)} | select FullName,@{Name=’Date';Expression={($_.lastwritetime).ToShortDateString()}} | ft

      Note if you add -auto to this, and if your filenames are long, you might not see the Date column in your PowerShell host. Lots of ways to solve that though. Here are a few possibilities:
      1. Export to csv, open in Excel.
      2. Add -Auto, then Convert to string (Out-String -Width 4096) then write to text file (Out-File), then open in notepad.
      3. Use an expression for the filename, and if it exceeds some width (say, 60 characters), return a truncated version that has … either at the beginning of the file or somewhere in the middle.

      There are of course other ways too, such as stripping off a prefix for the folder you’re searching to make the paths shorter, and I’m sure plenty more, but this should get you started. If you want help with one of these alternatives or some other method, let me know.

      Kirk out.


  11. Jaa5
    May 5, 2012 at 7:10 am

    Kirk, thanks so much for the solution and detailed explanation! Really appreciate you taking the time to pass along your knowledge while providing some ‘schoolin’


    • Kirk Munro
      May 5, 2012 at 8:03 am

      My pleasure! I’m glad it helped solve your problem.

      Kirk out.


  12. Liping
    June 8, 2012 at 9:21 am

    Kirk, ran into the same problem and glad that I found your article. Thanks for sharing. I tested your sample command in our environment, but noticed that the last column is still truncated (with …). I have tested this on Windows 7, Windows 2008 R2, Windows 2003, same results, just like what’s on your screenshot. Even if there is scroll bar in the notepad file, the last column is still like what’s show on the screen – truncated. Here is the command I used:
    get-alias -definition invoke-* |Format-Table -Property * -AutoSize|Out-String -Width 8000|Out-File test.
    Any insight will be greatly appreciated!


    • Liping
      June 8, 2012 at 10:46 am

      I found the answer using tip 1 from the following post: http://www.powershellcommunity.org/Forums/tabid/54/aft/3498/Default.aspx


      • Kirk Munro
        June 15, 2012 at 7:44 am

        Excellent, I’m glad you found that post I wrote on the PowerShellCommunity.org forums. I just added a note to this blog post letting people know that they can expand individual properties that are collections using the $FormatEnumerationLimit variable so that they can find all of the details in this post.

        I’m happy you found your answer, and thanks for sharing! :)

        Kirk out.


  13. EJH
    September 19, 2012 at 6:30 pm

    Thanks so much!!!


    • Kirk Munro
      September 19, 2012 at 11:49 pm

      Glad I could help!

      Kirk out.


  14. Scotty
    November 23, 2012 at 10:33 am

    Thank you, thank you Thank you ! You rescued my day… Ah c’mon …WEEKS !
    This is what I’ve been searching/googeling/yahooing/ for so long and it nearly drove me nuts !

    Thanks again and If you make it some day to Germany, I owe you a beer .

    Scotty out.


    • Kirk Munro
      November 23, 2012 at 10:40 am

      This comment made my day today. Thanks for letting me know this blog post was able to help you out! :)

      Kirk out.


  15. April 19, 2013 at 6:32 pm

    Mr. Kirk, I was wondering if you could help with a simple script, I’m trying to format the output of an exchagne 2010 PS comlet and I’m having a hell of a time doing it. What I would like to do is use the “Get-MoveRequestStatistics” cmlet and I want the following objects:


    I need them out in a csv file neatly tabulated with headers from the cmdlet to show only one time in the top of the file, followed by the data tabulated in each column:

    Here’s what I have thus far: I’ll mark the start of each new line with a – since screen is so narrow.

    -$filename = Read-Host “Enter file name of Run:”
    -$headers = @(“displayname”, “BadItemsEncountered”, “QueuedTimestamp”, “StartTimestamp”, “OverallDuration”, “TotalFinalizationDuration”, “TotalInProgressDuration”, “MRSServerName”, “TotalMailboxSize”, “TotalMailboxItemCount”, “BytesTransferred”, “BytesTransferredPerMinute”, “ItemsTransferred”, “PercentComplete”)
    -$Completed = Get-Content C:\Download\stats\completed-users.txt
    -$outfile = “C:\Download\stats\$filename”

    -foreach ($u in $completed)
    -Get-MoveRequestStatistics -Identity “$u” | select displayname,BadItemsEncountered,QueuedTimestamp,StartTimestamp,OverallDuration,TotalFinalizationDuration,TotalInProgressDuration,MRSServerName,TotalMailboxSize,TotalMailboxItemCount,BytesTransferred,BytesTransferredPerMinute,ItemsTransferred,PercentComplete | ft -Property * -auto |Out-String -Width 4096 |Out-File $outfile

    I’m kinda of new working with PS, but I’ve worked with Sun OS 8 in bash scripts before so I have some idea about scripting.. but this has me stumped

    thank you in advance in any advise.


    • Kirk Munro
      April 20, 2013 at 9:38 am

      Hello Moreno,

      Have you seen the Export-Csv cmdlet? That cmdlet will export an object or a collection of objects to a csv file. It automatically creates the headers for you. You will want to use that cmdlet with the -NoTypeInformation parameter so that the type information is not written at the top of the csv file above the headers. Here’s an untested example of what that might look like:

      @(foreach ($u in $completed) {Get-MoveRequestStatistics -Identity $u | Select-Object -Property $headers}) | Export-Csv -NoTypeInformation -LiteralPath $outfile

      This script breaks down as follows:
      1. Get the move request statistics for every user, selecting the properties you care about, and store those in an array).
      2. Export the contents of that array to a csv outfile, omitting the type information.

      Another way to do this that might be a little more clear:

      # Declare the array to hold the user move request statistics
      $moveRequestStatistics = @()
      # Add the statistics to the array
      foreach ($u in $completed) {
      $moveRequestStatistics += Get-MoveRequestStatistics -Identity $u | Select-Object -Property $headers
      # Now export the data
      $moveRequestStatistics | Export-Csv -NoTypeInformation -LiteralPath $outfile

      Also, just FYI, a better forum for asking questions like these can be found on PowerShell.org. I answer questions there, as do many others, plus the answers are then visible for others coming to the site. This is visible as well, sure, but the forums are just a better medium for Q&A because you have more people paying attention to them. You can find a link to the forums on the main page.

      I hope this helps!

      Kirk out.


  16. April 22, 2013 at 8:41 am

    Kirk, I was working on this for days, with no luck, my frustration level (or ego LoL) broke me down to ask someone bigger.. lol, thank you soooo much I was so happy to see it work as it should…. if I could do anything to repay you… i would lol.. :)



    • Kirk Munro
      April 22, 2013 at 10:27 am

      Excellent, I’m glad that I was able to help solve your problem. Thanks for letting me know!

      Kirk out.


  17. ovm
    June 14, 2013 at 5:19 pm

    Excellent ! – Thank you so much – I was struggling with this all day – You made my day!


    • June 14, 2013 at 10:08 pm

      I’m glad I was able to help you out! :)


  18. Andreas
    July 30, 2013 at 7:18 am

    Hey, thank you so much!

    What I do not understand: Get-VMHost | Foreach-Object {Get-Compliance -Entity $_ -Detailed | Format-Table -AutoSize} | Out-File D:\report.txt in the console works fine, but as scheduled Task table rows are removed


    • July 30, 2013 at 9:56 am

      Can you explain in more detail what you mean by “table rows are removed”? Are you getting some data but not all data? Are you running the scheduled task in the same context as your local user when you run the command in the console?


      • Andreas
        August 1, 2013 at 3:53 am

        The above Command is part of a script. When I start this script from a PowerShell Console the Output is complete (7 Table rows) but when I create a scheduled Task which runs the same script, then the Output only has 5 table rows and that is waht I don’t understand. I use the same user for running the schedtask and the console.


  19. TMan
    October 9, 2013 at 6:16 pm

    Hi Kirk, I just wanted to drop a FREAKIN THANK YOU!.. line. I had spent days trying to get this outupt from a ps1, not a quick script. Like Scotty said above, I scowered high and low, close and far and you teenee tiny post had exactly what I just could not find.


  1. October 27, 2011 at 9:48 am
  2. January 27, 2013 at 10:49 am
  3. October 12, 2013 at 5:55 pm

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


Get every new post delivered to your Inbox.

Join 283 other followers

%d bloggers like this: