Powershell' is not recognized as an internal or external command, operable program or batch file

Question

I am trying to run a powershell -Command to execute a powershell file as a post build event in Visual studio 2013 But i am getting

'Powershell' is not recognized as an internal or external command, operable program or batch file

error on output window and

Powershell -Command exited with code 9009 error

Full Error Message:

'Powershell' is not recognized as an internal or external command,
10>  operable program or batch file.
10>C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(4429,5): error MSB3073: The command "echo "C:\dev\tfs\Main\Shared\AggregationComponents\GenerateSchema.cmd"
10>C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(4429,5): error MSB3073: call "C:\dev\tfs\Main\Shared\AggregationComponents\GenerateSchema.cmd"
10>C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(4429,5): error MSB3073: echo "Move the PhoenixData namespace schema suffixing it"
10>C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(4429,5): error MSB3073: Powershell -Command "C:\dev\tfs\Main\Shared\AggregationComponents\MoveAndRenameXsds.ps1 'C:\dev\tfs\Main\Shared\AggregationComponents\bin\Debug\' 'C:\dev\tfs\Main\Shared\AggregationComponents\..\PublishedAnalyticsXsds' '.Aggregation'"" exited with code 9009.
========== Rebuild All: 8 succeeded, 1 failed, 1 skipped ==========

The unmatched quotation marks are suspicious. Are you sure you copied it correctly? Please share the actual command line you are trying to execute. (Also verify that it is on your PATH.) — Raymond Chen
– Raymond Chen, Commented Apr 21, 2015 at 16:58
@RahulLodha This problem could be due to pathext variable problem. See superuser.com/questions/675006 — X10
– X10, Commented Sep 18, 2015 at 2:54
An old thread I know, but I had this issue recently using the JetBrains WebStorm CLI (similar to VS Code) and turns out that if I used Windows Command Prompt as Administrator it worked fine. — James
– James, Commented Dec 14, 2021 at 23:08

Jon Tirjan · Accepted Answer · 2015-04-21 16:59:26Z

115

Sounds like you're missing an environment variable.

Add this to your Path environment variable:

%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\

OR

Change your script to this:

%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\powershell.exe -Command "your command"

answered Apr 21, 2015 at 16:59

Jon Tirjan

3,7242 gold badges19 silver badges28 bronze badges

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

Rahul Lodha Over a year ago

It worked. i had to restart visual studio after path change. Thank You! :)

Jon Tirjan Over a year ago

Glad it worked. Strange that it was missing though. I've always seen it populated by default.

Zeyad Shaban Over a year ago

What worked for me was C:\WINDOWS\System32\WindowsPowerShell\v1.0\

qaziqarta Over a year ago

I had to move the path %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\ from the System environment list box to the User environment list box, as per this answer: superuser.com/a/1034020 . Otherwise the %SYSTEMROOT% part was not expanding to actual path.

Chethana Wickramaarachchi Over a year ago

This is working and , Have to restart visual studio after path change. Otherwise will show the same error- default path- C:\WINDOWS\System32\WindowsPowerShell\v1.0\

Uwe Keim · Accepted Answer · 2021-12-06 07:48:17Z

18

You only need to add it to your environment variables, just follow the following two simple steps:

1.write env in the search bar

or Right click start button -> System -> Advanced system settings -> Environment Variables... -> Select PATH

2. click on the new button and add the following path:

C:\WINDOWS\System32\WindowsPowerShell\v1.0\

or %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\

edited Dec 6, 2021 at 7:48

Uwe Keim

41k61 gold badges194 silver badges311 bronze badges

answered Jan 24, 2021 at 14:43

Mostafa Wael

4,0641 gold badge28 silver badges32 bronze badges

Comments

alloha · Accepted Answer · 2020-04-24 02:59:28Z

4

Remove BOM byte from the beginning of batch file or convert it's encoding to ANSI. BOM treats system to think you use unavailable command.

answered Apr 24, 2020 at 2:59

alloha

1321 silver badge13 bronze badges

molbalga Over a year ago

The approved solution did work for me, but this was really the root cause.

Alex · Accepted Answer · 2020-07-02 16:36:30Z

2

My mistake was just that I forgot to run Visual Studio / command prompt as an Administrator.

answered Jul 2, 2020 at 16:36

Alex

5,69610 gold badges59 silver badges75 bronze badges

Comments

Arif Test · Accepted Answer · 2021-04-22 18:28:10Z

0

try

'%SYSTEMROOT%\\System32\\WindowsPowerShell\\v1.0\\powershell.exe tracert google.com'

might require \\ instead of \.

answered Apr 22, 2021 at 18:28

Arif Test

33 bronze badges

Comments

Lance Tollenaar · Accepted Answer · 2026-03-03 04:23:36Z

0

Old question, but I had this issue today.

I wrote a batch script that subsequently executes a Powershell script, and accidentally used %path% as a local variable, to store the path of some unrelated file, in the batch script.

However, using %path% as a local variable will quietly override your (very important) environment %PATH% variable, which happens to include the path to powershell.exe.

Thankfully, this change is not permanent (unless you used setx in the batch file).

answered Mar 3 at 4:23

Lance Tollenaar

1

Collectives™ on Stack Overflow

Powershell' is not recognized as an internal or external command, operable program or batch file

6 Answers 6

You only need to add it to your environment variables, just follow the following two simple steps:

1.write env in the search bar

2. click on the new button and add the following path:

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

5 Comments

You only need to add it to your environment variables, just follow the following two simple steps:

1.write env in the search bar

2. click on the new button and add the following path:

Comments

1 Comment

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related