When I run a program on PowerShell it opens a new window and before I can see the output, the window closes. How do I make it so PowerShell keeps this window open?
-
is this program an exe, or a batch file? Can you give the exact command you are running, perhaps changing the name of the executable?Justin Dearing– Justin Dearing2012-02-11 21:46:13 +00:00Commented Feb 11, 2012 at 21:46
-
It's an exe. I added the folder that the program is in to my path and when I type in the name of the program it runs, except the window it opens in closes too quickly for me to read what it says. The program is a program to test python programs. As for your comment below, I don't know how to wrap a program in a batch file :/Erman– Erman2012-02-11 21:56:15 +00:00Commented Feb 11, 2012 at 21:56
-
I updated my answer to clarify how to do that. It also might make sense to redirect your programs output to a text file.Justin Dearing– Justin Dearing2012-02-11 22:59:52 +00:00Commented Feb 11, 2012 at 22:59
-
Related (duplicate): How to keep the shell window open after running a PowerShell script?Peter Mortensen– Peter Mortensen2016-01-21 15:38:48 +00:00Commented Jan 21, 2016 at 15:38
7 Answers
Try doing:
start-process your.exe -NoNewWindow
Add a -Wait too if needed.
5 Comments
start-process 'full path to\your.exe' -NoNewWindow, the command ran as expected.-Verb RunAs parameter set was causing an AmbiguousParameterSet errorThe OP seemed satisfied with the answer, but it doesn't keep the new window open after executing the program, which is what he seemed to be asking (and the answer I was looking for). So, after some more research, I came up with:
Start-Process cmd "/c `"your.exe & pause `""
I was solving a similar problem few weeks ago. If you don't want to use & (& '.\program.exe') then you can use start process and read the output by start process (where you read the output explicitly).
Just put this as separate PS1 file - for example (or to macro):
param (
$name,
$params
)
$process = New-Object System.Diagnostics.Process
$proInfo = New-Object System.Diagnostics.ProcessStartInfo
$proInfo.CreateNoWindow = $true
$proInfo.RedirectStandardOutput = $true
$proInfo.RedirectStandardError = $true
$proInfo.UseShellExecute = $false
$proInfo.FileName = $name
$proInfo.Arguments = $params
$process.StartInfo = $proInfo
#Register an Action for Error Output Data Received Event
Register-ObjectEvent -InputObject $process -EventName ErrorDataReceived -action {
foreach ($s in $EventArgs.data) { Write-Host $s -ForegroundColor Red }
} | Out-Null
#Register an Action for Standard Output Data Received Event
Register-ObjectEvent -InputObject $process -EventName OutputDataReceived -action {
foreach ($s in $EventArgs.data) { Write-Host $s -ForegroundColor Blue }
} | Out-Null
$process.Start() | Out-Null
$process.BeginOutputReadLine()
$process.BeginErrorReadLine()
$process.WaitForExit()
And then call it like:
.\startprocess.ps1 "c:\program.exe" "params"
You can also easily redirect output or implement some kind of timeout in case your application can freeze...
1 Comment
If the program is a batch file (.cmd or .bat extension) being launched with cmd /c foo.cmd command, simply change it to cmd /k foo.cmd and the program executes, but the prompt stays open.
If the program is not a batch file, wrap it in a batch file and add the pause command at the end of it. To wrap the program in a batch file, simply place the command in a text file and give it the .cmd extension. Then execute that instead of the exe.