PowerShell does not correctly capture stdout from a windows app when redirecting to a file

Open
#28,113 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
powershell

Research direction

Start with the reproduction in discussion 25875 and the example code in rhubarb-geek-nz/pipe-dream; compare t1.exe, t2.exe, and t3.exe using file redirection and Out-String -Stream on Windows. The payload names no PowerShell source file or test, so trace the output-redirection and child-process handling from the reproduction. Done means stdout from a Windows app is written completely to the redirected file rather than producing an empty file.

Written by the indexing model from the issue text.

Description

Needs-Triage
Prerequisites
Steps to reproduce

https://github.com/PowerShell/PowerShell/discussions/25875

See example code at https://github.com/rhubarb-geek-nz/pipe-dream

t1 is a console app
t2 and t3 are window apps

All three write to stdout.

With PowerShell piping output from t1.exe to a file works.

With PowerShell redirecting output from t2.exe and t3.exe to a file creates an empty file.

The working assumption is that PowerShell creates a pipe for stdout and does the writing to the file itself rather than handing the file handle to the child.

Because the app is not a console app it does not wait for the process to finish.

However, because it should be reading from a pipe and writing to a file, when the process terminates is irrelevant, it should wait for the end of file on the pipe.

Using

.\t2.exe | Out-String -Stream

Does work as expected and shows that the stdout can be processed from a windows application.

Expected behavior
That redirecting output from a windows app will write all stdout content to a file.
Actual behavior
Redirection output from a windows app to a file creates an empty file
Error details
File contains zero bytes
Environment data
Name                           Value
----                           -----
PSVersion                      7.6.6
PSEdition                      Core
GitCommitId                    7.6.6
OS                             Microsoft Windows 10.0.26200
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.4
SerializationVersion           1.1.0.1
WSManStackVersion              3.0
Visuals

No response

Dominant language
C#
Stars
56.1k
Forks
8.5k
Avg merge
12h 33m
Merged PRs (30d)
73

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PowerShell/PowerShell

All issues in PowerShell/PowerShell

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.