- Notifications
You must be signed in to change notification settings - Fork7.7k
[release/v7.5] Set standard handles explicitly when starting a process with-NoNewWindow
#25324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
[release/v7.5] Set standard handles explicitly when starting a process with-NoNewWindow
#25324
Conversation
Original issue:#24986 |
@daxian-dbw this is consistently failing the build. |
/azp run PowerShell-CI-linux-packaging, PowerShell-Windows-Packaging-CI |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
cd6b4d8
intoPowerShell:release/v7.5Uh oh!
There was an error while loading.Please reload this page.
microsoft-github-policy-servicebot commentedJun 4, 2025 • edited by unfurl-linksbot
Loading Uh oh!
There was an error while loading.Please reload this page.
edited by unfurl-linksbot
Uh oh!
There was an error while loading.Please reload this page.
📣 Hey @@pwshBot, how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗https://aka.ms/PSRepoFeedback |
Uh oh!
There was an error while loading.Please reload this page.
Backport of#25061 to release/v7.5
Triggered by@TravisEz13 on behalf of@daxian-dbw
Original CL Label: CL-General
/cc @PowerShell/powershell-maintainers
Impact
Choose either tooling or Customer impact.
Tooling Impact
Customer Impact
When using
Start-Process
with-NoNewWindow
, the output of the process will be messed up. See the "expected behaviors" and "actual behaviors" in the original issue.Regression
Introduced in 7.5
Testing
Added a test
Risk
[High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]