Node.js upgrade still shows older version in windows

Question

I have downloaded and installed the new version of nodejs (4.1.2) using the .msi installer. After that I ran node -v, but it still shows the older version (0.12.2). I tried restarting Windows and even uninstalled nodejs and reinstalled it, but still it shows the same. Why is that happening and how can I resolve it?

Adjoin

You might want to check your path variable and make sure it is not pointing to an older version of node.js – Lohman

Path variables are ok. I installed on the same directory. – Adjoin

Answer 1

Run a search for multiple copies of node.exe in the usual install paths:

• Program Files

    Get-ChildItem -File -path $env:PROGRAMFILES -include node.exe -recurse -force
  

• Program Files(x86)

    Get-ChildItem -File -path $env:PROGRAMFILESX86 -include node.exe -recurse -force
  

• Common Files

    Get-ChildItem -File -path $env:COMMONPROGRAMFILES -include node.exe -recurse -force
  

• Roaming

    Get-ChildItem -File -path $env:APPDATA -include node.exe -recurse -force
  

Upgrading npm has its own issues:

Chances are that you attempted to upgrade npm before, it somehow failed, and you then went looking for this tool. If the tool fails to upgrade, it may be troubled by partial changes done during npm install npm or npm upgrade npm. In that case, you will have to completely uninstall Node:

Uninstall Node.js (select Uninstall, not the Repair option).

Go into %programfiles%\nodejs and delete the entire folder.

Delete %appdata%\npm and %appdata%\npm-cache.

Edit your PATH and remove everything that references npm (to do so, hit "Start" and search for "Environment Variables").

Reinstall Node, then install this tool - and only use this tool to upgrade npm, do not attempt to run npm install npm.

References

• npmjs docs: Prefix Configuration

• Get-ChildItem for FileSystem

• Finding files in the PATH with PowerShell

• Microsoft NodeJS Guidelines

• Environment.SpecialFolder Enumeration (System)

• Common folder variables - Windows Defender Security Intelligence

• KNOWNFOLDERID (Windows)

Uproot

Well, I solved this problem long ago. The reason of this problem was indeed multiple existence of node.js installation. – Adjoin

I had a similar issue, had two instances of node installed, so I removed one through Control Panel, other one, older version, I just deleted the folder. After this clean installation of new version works with no issues. Thx Paul. – Mane

Answer 2

I had the same issue and resolved it by deleting the node.js folder in program files (x64) and it w

Forequarter

Answer 3

I had remove Nsolid path from Environment. it should be relate to node.exe in different path, make sure Nsolid, %appdata%/npm dont have node.exe file.

Crelin