node is not recognized as an internal or external command but is in PATH

Question

Although I've follow suggestions from:

I'm having an strange issue: Resume, although node path is list in Path, it doesn't find node.

Workflow:

Microsoft Windows [Version 6.3.9600]    //Running CMD on windows 8.1 
(c) 2013 Microsoft Corporation. All rights reserved.

I followed suggestions in SO, adding variable to Environment Variables, and it's display Ok in Path:

C:\Users\myUser>path
PATH=c:\Program Files (x86)\nodejs ; (...omitted...) //So folder is there

Next line will fail

C:\Users\myUser>call jasmine-node spec  
'node' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\myUser>cd "c:\Program Files (x86)\nodejs" //So I move to the folder list before...

But if I move to folder list in Path, then it works OK.

c:\Program Files (x86)\nodejs>call jasmine-node spec
>  (...omitted...) //Exec OK.

c:\Program Files (x86)\nodejs>node
>   //Exec OK. Waiting...

It seems contradictory.

Is there really a space before the semicolon in your `PATH` or did you add that while redacting? — hobbs, Oct 01 '14 at 15:30
O_O hobbs!! That was it! I edit manually adding a whitespace! Thanks a lot! I've spent hours trying to find the problem! If you add it as an answer I'll accept it. — Mario Levrero, Oct 01 '14 at 15:38
This happened to me **JUST AFTER** I installed a different, non related program. It might not be anything Node related that causes this problem to "suddenly" crop up. In my case, Dropbox altered my PATH. — Geek Stocks, Jul 18 '17 at 14:33

score 7 · Accepted Answer · answered Oct 01 '14 at 15:50

7

The nodejs directory in your PATH isn't recognized because there's a space before the semicolon, so Windows is looking for a directory with a space at the end of the name, which doesn't exist.

answered Oct 01 '14 at 15:50

hobbs

223,387
19
210
288

In my case the `%path%` was placed before the node path. – coletrain Aug 05 '16 at 20:00

score 5 · Answer 2 · answered Apr 23 '15 at 16:01

Error: 'node' is not recognized as an internal or external command

The problem is may be the node is not installed on the machine in which the application is running.

Then install it and set the environment variable for nodejs.

Or

One more reason can be the nodejs path not set in the environment variable.

Check with the following - open Control Panel -> System and Security -> System -> Advanced System Settings -> Environment Variables -> Path

the nodejs path should be available here. If not available then add the following:

C:\Program Files (x86)\nodejs OR C:\Program Files\nodejs

Now Re-Run the application and the Error got resolved.

score 3 · Answer 3 · answered Feb 12 '15 at 10:47

3

;C:\Program Files\nodejs\

Slash after \nodejs\ worked for me

answered Feb 12 '15 at 10:47

bernaulli

147
4

score 3 · Answer 4 · answered Jul 27 '15 at 15:06

3

Usually the environment variables are not effective till a system Restart.

I suggest a System Restart for all those who face the same issue when doing a clean install.

This worked for me.

answered Jul 27 '15 at 15:06

sudhansu63

6,025
4
39
52

2

On contrary, USUAL behavior is that system restart is NOT required But NEW command window has ALWAYS to be opened for the cmd to work. – nanosoft Sep 08 '16 at 06:50

score 2 · Answer 5 · answered Mar 03 '15 at 00:22

In Windows, you need to set node.js folder path into system variables or user variables.

1) open Control Panel -> System and Security -> System -> Advanced System Settings -> Environment Variables

2) in "User variables" or "System variables" find variable PATH and add node.js folder path as value. Usually it is C:\Program Files\nodejs;. If variable doesn't exists, create it.

3) Restart your IDE or computer.

It is useful add also "npm" and "Git" paths as variable, separated by semicolon.

score 1 · Answer 6 · answered Oct 01 '14 at 15:24

1

If you did npm install jasmine-node -g you should just need to do jasmine-node spec (no call prefix).

answered Oct 01 '14 at 15:24

mscdex

104,356
15
192
153

Thanks mscdex, I did a global install. Anyway, if I remove the 'call' prefix I still receive the same behavior. – Mario Levrero Oct 01 '14 at 15:26

Ahmad Baktash Hayeri · Answer 7 · 2016-01-06T05:41:19.660

If you've checked your PATH, and are sure that the path for node is added properly, then you're likely to face the problem while running node OR npm commands with CLI's other than the default command line interface of the operating system (e.g. Git bash in Windows).

The strange part is that you can check for node -v and npm -v in those CLIs, but for some reasons, they don't work well with those commands (especially when combined with install or update).

Possible Solution

Try running node with the default terminal for your OS.

score 0 · Answer 8 · answered Dec 06 '17 at 18:40

I faced this issue even after adding node.exe to PATH. I wasn't able to run node command at random locations without running command prompt as administrator.

Solution to this issue is, you have to give full access permissions to this node.exe file for different user types. open the properties of node.exe, go to security tabs, check all the security options to the user on your local machine.

after doing this you should be able to access the node.exe file from any location.

score 0 · Answer 9 · edited Apr 06 '20 at 08:26

things to check:

open CMD>Go to the directory where node.exe resides > type node -v > :

if it shows the version: Please add the same path (like> PATH=C:\Programfiles\nodejs\;) in the OS path in environment variable (any of the system or user variable, both work fine)
if it doesn't recognize, please add a variable PATHEXT=.exe; in the environment variable (The PathExt is an Environment Variable that stores a list of the file extensions for the operation system to execute) and save them.

Now open a new command prompt window and check.it must work.

score 0 · Answer 10 · answered Jul 31 '20 at 06:43

0

After installing nodejs you have to restart your terminal or IDE .

answered Jul 31 '20 at 06:43

somashekhar

3
2

score 0 · Answer 11 · answered Jul 26 '22 at 05:31

0

C:\Program Files\nodejs

adding the path without the semi-colon did it for me...

answered Jul 26 '22 at 05:31

ransi_07

11
5

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Jul 28 '22 at 14:38

score 0 · Answer 12 · answered Nov 23 '22 at 08:07

0

For the issue which is coming "node' is not recognized as an internal or external command, operable program or batch file.", I have tried updating the path, but the issue didn't resolve. So I uninstalled and installed node.js and it worked for me.

answered Nov 23 '22 at 08:07

Naurto san

277
1
2
14

score -1 · Answer 13 · edited Jul 27 '19 at 09:49

-1

The error:

node-is-not-recognized-as-an-internal-or-external-command

And the following solution:

Set Environment variable NODE_HOME as C:\Program Files\nodejs
Open cmd window and run:

cd "C:\Program Files\nodejs"
npm install connect
npm install -g appium

edited Jul 27 '19 at 09:49

steadweb

15,364
3
33
47

answered Jul 27 '19 at 08:55

Sanchi Tyagi

11
2

Hi, Sanchi, and welcome to SO. Installing new packages is not a solution. – Mario Levrero Jul 29 '19 at 07:20

score -3 · Answer 14 · edited Mar 24 '16 at 15:15

-3

It's as simple as adding the location of nodejs (C:\Program Files (x86)\nodejs) to your PATH variable and restarting your application with "Run as administrator".

edited Mar 24 '16 at 15:15

Hatchet

5,320
1
30
42

answered Mar 23 '16 at 18:50

Muzammil

1

Can you please brief it – Moumit Mar 23 '16 at 19:13

node is not recognized as an internal or external command but is in PATH

14 Answers14

Possible Solution

Linked