How to run a PowerShell script

Question

How do I run a PowerShell script?

I have a script named myscript.ps1
I have all the necessary frameworks installed
I set that execution policy thing
I have followed the instructions on this MSDN help page and am trying to run it like so: powershell.exe 'C:\my_path\yada_yada\run_import_script.ps1' (with or without --noexit)

which returns exactly nothing, except that the file name is output.

No error, no message, nothing. Oh, when I add -noexit, the same thing happens, but I remain within PowerShell and have to exit manually.

The .ps1 file is supposed to run a program and return the error level dependent on that program's output. But I'm quite sure I'm not even getting there yet.

What am I doing wrong?

Start the `powershell` as you would have started `cmd`. Now you can execute the `myscript.ps1` script as any executable there in (in powershell window), i.e. `.\myscript.ps1` — parasrish, Dec 19 '17 at 03:22

score 976 · Accepted Answer · edited Mar 31 '22 at 17:59

976

Prerequisites:

You need to be able to run PowerShell as an administrator
You need to set your PowerShell execution policy to a permissive value or be able to bypass it

Steps:

Launch Windows PowerShell as an Administrator, and wait for the PS> prompt to appear
Navigate within PowerShell to the directory where the script lives:
```
PS> cd C:\my_path\yada_yada\ (enter)
```
Execute the script:
```
PS> .\run_import_script.ps1 (enter)
```

Or: you can run the PowerShell script from the Command Prompt (cmd.exe) like this:

powershell -noexit "& ""C:\my_path\yada_yada\run_import_script.ps1""" (enter)

according to Invoking a PowerShell script from cmd.exe (or Start | Run) by Kirk Munro.

Or you could even run your PowerShell script asynchronously from your C# application.

edited Mar 31 '22 at 17:59

TylerH

20,799
66
75
101

answered Jan 09 '10 at 22:24

marc_s

732,580
175
1,330
1,459

This indeed works, but I need to do this from within a batch file. Obviously, my way of calling `powershell.exe` and then the script file is somehow screwed up. Do you have any idea how to modify it? – Pekka Jan 09 '10 at 22:26
25

Your blog post link did it. I have to use `powershell -noexit "& "C:\yada_yada\run_import_script.ps1"` (notice the *three* double quotes) I don't really understand why, but at this point, I don't really care :) Thanks a lot! – Pekka Jan 09 '10 at 22:32
22

What exactly does the `"&` do? – BlueRaja - Danny Pflughoeft Jan 25 '12 at 02:00
19

According to http://technet.microsoft.com/en-us/library/ee176949.aspx, the '&' is for "If you actually want to execute that string value (that is, if you want to run the script whose path is enclosed in double quotes) you need to preface the path with the Call operator (the ampersand)." – Doug Dawson May 29 '12 at 14:32
8

Just use the command `powershell c:\mypath\yadayada\myimportantscript.ps1` if your path and file name have no spaces in it but if you put quotes around it powershell will try and interpret the parameter as a string of powershell commands. – BeowulfNode42 Feb 09 '14 at 20:55
Oh, my god! I understand why powershell is so few persons to use, it's the most difficult script to run. – Clock ZHONG May 27 '23 at 06:19

score 314 · Answer 2 · edited Oct 05 '19 at 14:05

314

If you are on PowerShell 2.0, use PowerShell.exe's -File parameter to invoke a script from another environment, like cmd.exe. For example:

Powershell.exe -File C:\my_path\yada_yada\run_import_script.ps1

edited Oct 05 '19 at 14:05

Peter Mortensen

30,738
21
105
131

answered Jan 09 '10 at 23:39

Keith Hill

194,368
42
353
369

6

Is there a way to add parameters to such an invocation? – Alexander Groß Feb 01 '10 at 23:25
13

You should just be able to trail the args after the script file path. From the PowerShell.exe usage - [-File ] – Keith Hill Feb 02 '10 at 01:32
"cannot be loaded because the execution of scripts is disabled on this system. Please see "get-help about_signing" fo r more details." – Pavel Vlasov Oct 21 '16 at 14:26
10

If you haven't enabled PowerShell script execution on your system add the parameter `-ExecutionPolicy Bypass` – Keith Hill Oct 21 '16 at 18:36
5

FYI this also works for PowerShell 1.0 in my experience (Windows 2012 Server) – knocte Nov 08 '16 at 07:55

score 229 · Answer 3 · answered Jan 30 '11 at 22:23

229

If you want to run a script without modifying the default script execution policy, you can use the bypass switch when launching Windows PowerShell.

powershell [-noexit] -executionpolicy bypass -File <Filename>

answered Jan 30 '11 at 22:23

Chingiz Musayev

2,832
1
14
6

14

Also, include the `-nologo` option to get rid of the startup banner – swdev Jun 01 '16 at 06:28

score 114 · Answer 4 · edited Mar 26 '16 at 19:21

114

Type:

powershell -executionpolicy bypass -File .\Test.ps1

NOTE: Here Test.ps1 is the PowerShell script.

edited Mar 26 '16 at 19:21

igr

10,199
13
65
111

answered Feb 05 '15 at 22:38

Sudheesh

1,149
1
7
2

This should be executed in a powershell as `powershell -executionpolicy bypass -File .\Test.ps1` assuming you current working directory contains Test.ps1 – Yeow_Meng Dec 03 '15 at 03:57

score 39 · Answer 5 · edited Nov 30 '14 at 23:27

39

I've had the same problem, and I tried and tried... Finally I used:

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

And put this line in a batch-file, and this works.

edited Nov 30 '14 at 23:27

Peter Mortensen

30,738
21
105
131

answered Mar 08 '10 at 13:47

Dennis

1,810
3
22
42

score 23 · Answer 6 · edited Nov 30 '14 at 23:27

23

If you only have PowerShell 1.0, this seems to do the trick well enough:

powershell -command - < c:\mypath\myscript.ps1

It pipes the script file to the PowerShell command line.

edited Nov 30 '14 at 23:27

Peter Mortensen

30,738
21
105
131

answered Jul 01 '10 at 09:32

AndyM

3,574
6
39
45

3

Useful trick when security policies don't allow script execution. – Aron Lorincz Aug 21 '16 at 14:46

score 22 · Answer 7 · edited Mar 02 '17 at 10:27

22

Pretty easy. Right click the .ps1 file in Windows and in the shell menu click on Run with PowerShell.

edited Mar 02 '17 at 10:27

Peter Mortensen

30,738
21
105
131

answered Aug 23 '16 at 14:51

electronictonic

251
2
2

This works to quickly run a script without having to enable the execution of scripts with execution policy. Thanks! – b01 May 21 '17 at 00:02

score 19 · Answer 8 · edited Jul 28 '22 at 15:00

19

Open PowerShell in administrator mode
Run: set-executionpolicy unrestricted
Open a regular PowerShell window and run your script.

I found this solution following the link that was given as part of the error message: About Execution Policies

Make sure to run set-ExecutionPolicy default once you're done, or you will be exposed to security risks.

edited Jul 28 '22 at 15:00

TylerH

20,799
66
75
101

answered Sep 17 '19 at 16:04

JovanToroman

605
6
16

score 12 · Answer 9 · edited Mar 02 '17 at 10:28

12

If your script is named with the .ps1 extension and you're in a PowerShell window, you just run ./myscript.ps1 (assuming the file is in your working directory).

This is true for me anyway on Windows 10 with PowerShell version 5.1 anyway, and I don't think I've done anything to make it possible.

edited Mar 02 '17 at 10:28

Peter Mortensen

30,738
21
105
131

answered Sep 06 '16 at 19:58

rainabba

3,804
35
35

2

How does this answer the question? – Peter Mortensen Mar 02 '17 at 10:29
5

it absolutely answers the question: how do I run a powershell script? answer: startup powershell console, then execute the script. easy. simple. Works on Linux also. – Thufir Feb 17 '18 at 18:31
5

This absolutely answers the question, and was exactly what I was looking for. as `myscript.ps1` did not work, threw an error, but with `./` it's executing. – Jeff Mar 31 '18 at 22:16

score 11 · Answer 10 · answered Nov 17 '14 at 09:04

Using cmd (BAT) file:

@echo off
color 1F
echo.

C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy Bypass -File "PrepareEnvironment.ps1"

:EOF
echo Waiting seconds
timeout /t 10 /nobreak > NUL

If you need run as administrator:

Make a shortcut pointed to the command prompt (I named it Administrative Command Prompt)
Open the shortcut's properties and go to the Compatibility tab
Under the Privilege Level section, make sure the checkbox next to "Run this program as an administrator" is checked

score 11 · Answer 11 · edited Mar 02 '17 at 10:29

11

An easy way is to use PowerShell ISE, open script, run and invoke your script, function...

edited Mar 02 '17 at 10:29

Peter Mortensen

30,738
21
105
131

answered Nov 01 '16 at 16:39

Jose Evaristo Cepeda Barrera

127
1
2

score 11 · Answer 12 · edited Nov 11 '18 at 06:02

11

In case you want to run a PowerShell script with Windows Task Scheduler, please follow the steps below:

Create a task
Set Program/Script to Powershell.exe
Set Arguments to -File "C:\xxx.ps1"

It's from another answer, How do I execute a PowerShell script automatically using Windows task scheduler?.

edited Nov 11 '18 at 06:02

Peter Mortensen

30,738
21
105
131

answered May 24 '18 at 08:07

Eugene

10,627
5
49
67

score 8 · Answer 13 · edited Nov 30 '14 at 23:29

8

Give the path of the script, that is, path setting by cmd:

$> . c:\program file\prog.ps1
Run the entry point function of PowerShell:

For example, $> add or entry_func or main

edited Nov 30 '14 at 23:29

Peter Mortensen

30,738
21
105
131

answered Jun 16 '13 at 09:28

pkm

2,683
2
29
44

Running your commands from a cmd prompt: `>$ . c:\program file\prog.ps1 '.' is not recognized as an internal or external command, operable program or batch file.` and `>$ add or entry_func or main 'add' is not recognized as an internal or external command, operable program or batch file.` – Suncat2000 Dec 09 '19 at 21:15

score 3 · Answer 14 · answered Aug 23 '20 at 07:30

3

You can run from cmd like this:

type "script_path" | powershell.exe -c -

answered Aug 23 '20 at 07:30

Wasif

14,755
3
14
34

score 2 · Answer 15 · edited Nov 11 '18 at 06:02

2

Use the -File parameter in front of the filename. The quotes make PowerShell think it is a string of commands.

edited Nov 11 '18 at 06:02

Peter Mortensen

30,738
21
105
131

answered Aug 01 '18 at 11:17

Engineer

834
1
13
27

score 2 · Answer 16 · answered Mar 31 '22 at 08:19

I've just found the method what Microsoft do when we right click on a ps1 script and click on "Run with PowerShell" :

"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" "-Command" "if((Get-ExecutionPolicy ) -ne 'AllSigned') { Set-ExecutionPolicy -Scope Process Bypass }; & 'C:\Users\USERNAME\Desktop\MYSCRIPT.ps1'"

score 0 · Answer 17 · answered Jan 06 '22 at 03:03

With the appropriate execution policy, you should just be able to call the file directly and Windows will associate it with PowerShell

C:\my_path\yada_yada\run_import_script.ps1

That does not do so well with arguments. The real answer to your question is that you are missing the & to say "execute this"

powershell.exe '& C:\my_path\yada_yada\run_import_script.ps1'

How to run a PowerShell script

17 Answers17

Linked

Related