How to run PowerShell in CMD

Question

I'm trying to run a PowerShell script inside cmd command line. Someone gave me an example and it worked:

powershell.exe -noexit "& 'c:\Data\ScheduledScripts\ShutdownVM.ps1'"

But the problem is my PowerShell script has input parameters, so I tried, but it doesn't work:

powershell.exe -noexit "& 'D:\Work\SQLExecutor.ps1 -gettedServerName "MY-PC" ' "

The error is:

The term 'D:\Work\SQLExecutor.ps1 -gettedServerName "MY-PC" ' is not recognized as the name of a cmdlet, function,

How can I fix this problem?

Are you sure you want to use -noexit ? This means when your script completes the shell will hang around, possibly blocking the execution of the batch file in CMD. — x0n
– x0n, Commented May 8, 2013 at 15:56

Shay Levy · Accepted Answer · 2013-05-08 12:49:34Z

121

You need to separate the arguments from the file path:

powershell.exe -noexit "& 'D:\Work\SQLExecutor.ps1 ' -gettedServerName 'MY-PC'"

Another option that may ease the syntax using the File parameter and positional parameters:

powershell.exe -noexit -file "D:\Work\SQLExecutor.ps1" "MY-PC"

edited May 8, 2013 at 12:49

answered May 8, 2013 at 9:09

Shay Levy

128k34 gold badges193 silver badges210 bronze badges

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

1 Comment

DustWolf Over a year ago

So basically you just need to add -file.

Matt · Accepted Answer · 2021-04-13 10:24:00Z

15

I'd like to add the following to Shay Levy's correct answer: You can make your life easier if you create a little batch script run.cmd to launch your powershell script:

run.cmd

@echo off & setlocal
set batchPath=%~dp0
powershell.exe -noexit -file "%batchPath%SQLExecutor.ps1" "MY-PC"

Put it in the same path as SQLExecutor.ps1 and from now on you can run it by simply double-clicking on run.cmd.

Note:

If you require command line arguments inside the run.cmd batch, simply pass them as %1 ... %9 (or use %* to pass all parameters) to the powershell script, i.e.
powershell.exe -noexit -file "%batchPath%SQLExecutor.ps1" %*
The variable batchPath contains the executing path of the batch file itself (this is what the expression %~dp0 is used for). So you just put the powershell script in the same path as the calling batch file.

edited Apr 13, 2021 at 10:24

answered Oct 16, 2017 at 11:29

Matt

27.4k19 gold badges131 silver badges202 bronze badges

2 Comments

Nuno André Over a year ago

You can do the same with @powershell.exe -noexit -file "%~dp0SQLExecutor.ps1" "MY-PC".

Matt Over a year ago

If you want to get rid of the varialble batchPath, yes of course you can do so. But due to setlocal the variable does not harm, since the variable's lifetime ends when the script exits. @NunoAndré

Peter Mortensen · Accepted Answer · 2019-06-17 07:10:48Z

7

Try just:

powershell.exe -noexit D:\Work\SQLExecutor.ps1 -gettedServerName "MY-PC"

edited Jun 17, 2019 at 7:10

Peter Mortensen

31.4k22 gold badges110 silver badges134 bronze badges

answered May 8, 2013 at 9:12

CB.

61.3k9 gold badges171 silver badges165 bronze badges

Collectives™ on Stack Overflow

How to run PowerShell in CMD

3 Answers 3

1 Comment

2 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

1 Comment

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related