Powershell executable isn’t outputting to STDOUT

by

As Ansgar’s comment implies: On Windows, Start-Process runs console programs in a new console window by default, asynchronously.

If that program completes quickly, you may see the new console window flash only briefly, as it opens and closes soon thereafter, or you may miss the flash altogether – either way, its output will not show in the caller’s console window.

Adding -Wait to the Start-Process call would make the invocation synchronous, and adding -NoNewWindow would make it run in the same console, yet the calling PowerShell session wouldn’t be able to capture or redirect the invoked program’s output – see below.

Taking a step back: Do NOT use Start-Process[1] if you want to run a console program synchronously, with its standard streams connected to PowerShell’s streams – just invoke such a program directly:

packages/mdoc/tools/mdoc.exe --version

If the external program’s path / name must be quoted (because its path contains spaces) and/or it is stored in a variable, simply use &, the call operator, to invoke it:

# Via a quoted string:
& "packages/mdoc/tools/mdoc.exe" --version

# Via a variable:
$exePath = "packages/mdoc/tools/mdoc.exe"
& $exePath --version

Using the direct-invocation approach gives you synchronous execution for free, as well as the ability to capture and/or redirect the invoked program’s stdout and stderr streams.

To put it all together (based on your later comments):

nuget install mdoc -OutputDirectory packages -ExcludeVersion

$exePath = "packages/mdoc/tools/mdoc.exe"

& $exePath --version

"done"

This prints the version number – mdoc 5.7.2 as of this writing – just before printing done (verified on Windows PowerShell v5.1.17134.48 on Microsoft Windows 10 Pro (64-bit; Version 1709, OS Build: 16299.371)).

Optional reading: capturing stdout / stderr output from external programs:

To capture stdout output, simply assign the call to a variable:

$version = & $exePath --version  # $version receives stdout output as an *array of lines*

$version receives either a string scalar (single string) if there was only 1 line of output, or an array of strings representing the output lines.

To also capture stderr output, use redirection 2>&1:

[string[]] $allOutput = & $exePath --version 2>&1

Note the cast to [string[]], which ensures that the stderr lines are captured as strings too.

  • By default, they are captured as [System.Management.Automation.ErrorRecord] instances, which in Windows PowerShell will somewhat confusingly print them as if they were PowerShell errors – this problem has been fixed in PowerShell Core.

  • Conversely, however, if you don’t convert the type of the elements of the array that is returned to strings, you can examine each element with -is [System.Management.Automation.ErrorRecord] to determine whether it originated from stdout or stderr.

Note: When PowerShell communicates with external programs, character-encoding issues come into play: see this answer for details.

[1] Or the underlying .NET API, System.Diagnostics.Process.
For guidance on when Start-Process is or isn’t appropriate, see GitHub docs issue #6239

More Related Contents:

  1. Get-Aduser -Filter will not accept a variable
  2. In what scenario was Invoke-Expression designed to be used?
  3. Using PowerShell credentials without being prompted for a password
  4. PowerShell and the -contains operator
  5. Running a powershell command using full path and arguments from command line [duplicate]
  6. Character-encoding problem with string literal in source code
  7. How to handle failed variable assignments in powershell? [duplicate]
  8. Redirecting standard input\output in Windows PowerShell
  9. How to perform keystroke inside powershell?
  10. Reload the path in PowerShell
  11. INI file parsing in PowerShell
  12. Export-CSV exports length but not name
  13. Timing a command’s execution in PowerShell
  14. How to properly -filter multiple strings in a PowerShell copy script
  15. Write-Host vs Write-Information in PowerShell 5
  16. Why does “Get-ChildItem -File | Get-FileHash” work?
  17. Get the drive letter of USB drive in PowerShell
  18. Is there a way to pass serializable objects to a PowerShell script with start-process?
  19. Powershell Using Start-Process in PSSession to Open Notepad
  20. CMD or Powershell command to combine (merge) corresponding lines from two files [duplicate]
  21. Powershell Get-ChildItem most recent file in directory
  22. Powershell – Reboot and Continue Script
  23. Hashtables and key order
  24. Executing powershell command directly in jenkins pipeline
  25. Should $null be on the left side of the equality comparison? (-eq with arrays)
  26. How can I redirect stdout and stderr without polluting PowerShell error output
  27. How to recursively remove all empty folders in PowerShell?
  28. What is the difference between [pwsh] and [Powershell Integrated Console] on VS Code?
  29. What is `$?` in Powershell?
  30. Running tasks parallel in powershell

Leave a Comment