Powershell in NonInteractive mode

Question

I use Octopus for our deployments. I have a problem with one of the Powershell scripts to control the deployment:

# stops running processes
$processes = @("Notepad",
               "Firefox")
foreach ($process in $processes)
{
    $prc = Get-Process -Name $process -ErrorAction SilentlyContinue
    if (-not($prc -eq $null))
    {
        Write-Host "Stopping " $prc.ProcessName
        Stop-Process -InputObject $prc -ErrorAction SilentlyContinue
    }
}

The programs I try to stop are not the ones you see in the script above, but they represent what I am trying to do. Now the problem I have with it, is that it works well on one server, but not on another. Where it does not work, I get the error message:

Stop-Process : Windows PowerShell is in NonInteractive mode. Read and Prompt functionality is not available.

The script that works runs on Powershell 3.0, the one that does not work on Powershell 2.0. I cannot upgrade to Powershell 3.0 everywhere yet because the old servers run with Windows Server 2003. How can I make it work on PS 2.0?

Can you post the value of get-executionpolicy and $confirpreference from the server with version 2.0? — CB.
– CB., Commented May 16, 2013 at 7:03
get-executionpolicy RemoteSigned $confirpreference There was not output for $confirpreference. — tobre
– tobre, Commented May 16, 2013 at 7:59
I was able to try it today. The Stop-Process worked without a problem. It works with -Force, it works with -confirm:$false and with both together. Thank you! — tobre
– tobre, Commented May 22, 2013 at 15:23

Cheeso · Accepted Answer · 2017-05-03 03:16:30Z

40

Run with -Force:

Stop-Process -InputObject $prc -ErrorAction SilentlyContinue -Force

As C.B. suggested in the comment: -confirm:$false should also work. Rationale for this is as follows: -Confirm is a switch parameter. Switch parameters can only take arguments if you specify the parameter with a trailing colon and a value.

edited May 3, 2017 at 3:16

Cheeso

193k106 gold badges486 silver badges734 bronze badges

answered May 16, 2013 at 7:02

Davor Josipovic

5,5632 gold badges46 silver badges64 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

tobre Over a year ago

I will give this a try as soon as I can. Our users are using the system frequently for testing and I cannot do deployments often. I ran the script this morning from Powershell ISE stopping Notepad and it worked well. Therefore the only way to check if the problem is resolved is to do an actual deployment.

Andrew Young Over a year ago

Correction. Run with the -Force

Ian Yates Over a year ago

I had Remove-Item with -Force in a DevOps deployment powershell script but was still getting this message. So I'm going to try the -confirm:$false switch too.

gek · Accepted Answer · 2020-03-06 08:06:45Z

5

I just tried to use Remove-Item on the directory with children and got same message: Remove-Item : PowerShell is in NonInteractive mode. Read and Prompt functionality is not available. In my case -Recurse key has helped.

answered Mar 6, 2020 at 8:06

gek

5548 silver badges18 bronze badges

Comments

EspressoCode · Accepted Answer · 2024-05-01 01:55:54Z

0

I had this issue with running an inline PowerShell command on Azure Devops PowerShell deployment task. I could only fix the issue by running the PS command in a Command Line Script Task instead, see documentation here.

Add the following to the scripts field of the task for example:

Powershell -Command "Install-Module -Name SqlServer -Force -Confirm:$false"

In other words, put your PS command in double quotes, then run PowerShell -Command "MyPSCommand...".

answered May 1, 2024 at 1:55

EspressoCode

3653 silver badges12 bronze badges

Collectives™ on Stack Overflow

Powershell in NonInteractive mode

3 Answers 3

3 Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

3 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related