Skip to content
This repository was archived by the owner on Apr 22, 2023. It is now read-only.
This repository was archived by the owner on Apr 22, 2023. It is now read-only.

Windows Installer didn't add Node PATH #4356

Closed

Description

@benirose

I just installed Node using the .msi for Windows 7 64-bit. It seemed to add npm to my PATH but not node. I was able to add it easily, but didn't see this detail in the instructions. A new developer may not know this is something they have to do if the install fails to do it. Adding a note to the installation instructions may be helpful.

Activity

  1. isaacs commented on Dec 3, 2012

    @isaacs

    It should add them both. What was the PATH value after running the installer

    /cc @piscisaureus @sblom

  2. benirose commented on Dec 3, 2012

    @benirose
    Author

    I had just "C:\Users\brosenbach\AppData\Roaming\npm" as my PATH. I had to add ";C:\Program Files\nodejs" myself. Not sure why that was.

  3. paulxtiseo commented on Dec 6, 2012

    @paulxtiseo

    Same here. Just installed using MSI installer, 64bit version. Path was incorrectly set. Even now, when I fixed it manually by adding "C:\Program Files\nodejs" (to user environment and system environment) and removing the Appdata one that points to an empty folder, I can only run it from any command-line if cmd.exe is run as Administrator. As a user, I can only run it from inside that folder.

  4. MllePandaRoux commented on Jul 4, 2013

    @MllePandaRoux

    Same issue here! :)

  5. 7oque commented on Sep 2, 2013

    @7oque

    This just happened to me with the installer: v0.10.17

    (added roaming path and not path to application, in my case R:\Applications\nodejs)

  6. jgillich commented on Jan 3, 2014

    @jgillich

    Just had the same problem as @benirose on a fresh Windows 8.1 Pro installation.

  7. TahsinAbrar commented on Jan 10, 2014

    @TahsinAbrar

    I'm also facing the same problem. When I wrote echo $PATH in node.js terminal, It didn't show anything. I need to set the PATH to "C:\Program Files\nodejs". So, what should I do now?

  8. marceloco commented on Feb 25, 2014

    @marceloco

    I just had the same problem on a Surface Pro running Windows 8.1 Pro (64 bit).

  9. rbellio commented on Mar 9, 2014

    @rbellio

    I had the same issue, but I noticed if I opened up my environment variables, node was in my path already. Closing environment variables, re-opening my command windows and node is now on my path and available.

  10. rjt commented on Mar 9, 2014

    @rjt

    Yep, windows is like that, having to close out of the windows cmd line and
    reopen is one of the reasons we like bash.
    On Mar 9, 2014 7:30 AM, "rbellio" notifications@github.com wrote:

    I had the same issue, but I noticed if I opened up my environment
    variables, node was in my path already. Closing environment variables,
    re-opening my command windows and node is now on my path and available.

    Reply to this email directly or view it on GitHubhttps://github.com//issues/4356#issuecomment-37125852
    .

  11. rbellio commented on Mar 9, 2014

    @rbellio

    You may misunderstand me. It wasn't the opening and closing of windows cmd line that fixed the issue for me. It was opening Environment Variables and closing it that made it work. It's almost as if Environment Variables did not recognize the change.

  12. rjt commented on Mar 9, 2014

    @rjt

    System wide variable changes are usually not fully recognized on windows
    till after a reboot. ReOpening the cmd line has been required for years.
    Power shell or Win8 may be better.
    On Mar 9, 2014 9:02 AM, "rbellio" notifications@github.com wrote:

    You may misunderstand me. It wasn't the opening and closing of windows cmd
    line that fixed the issue for me. It was opening Environment Variables and
    closing it that made it work. It's almost as if Environment Variables did
    not recognize the change.

    Reply to this email directly or view it on GitHubhttps://github.com//issues/4356#issuecomment-37127559
    .

  13. dougwilson commented on Mar 9, 2014

    @dougwilson
    Member

    Yes, needing a reboot is something required, but other times simply opening a new Command Prompt windows is sufficient. Perhaps the installer should simply recommend a reboot after install to clear up the confusion when users try to instantly start using node.js from the command line?

  14. dougwilson commented on Mar 9, 2014

    @dougwilson
    Member

    Actually, I take that back. The installer should be able to get the new PATH picked up by broadcasting a WM_SETTINGCHANGE message to all the open windows. More information at https://stackoverflow.com/questions/3636055/how-to-modify-the-path-variable-definitely-through-the-command-line-in-windows

    It seems from these reports that this isn't being done, so if the installer did this, it should fix the issue.

  15. dougwilson commented on Mar 9, 2014

    @dougwilson
    Member

    For those so inclined to make a PR to this, it looks like someone has posted instructions for how to accomplish this in WiX: http://www.kajabity.com/2013/09/an-update-to-the-apache-maven-installers-broadcasting-wm_settingchange-to-update-environment-variables/

  16. 35 remaining items

  17. modified the milestones: 0.12.5, 0.12.4 on May 25, 2015
  18. modified the milestones: 0.12.5, 0.12.6 on Jun 22, 2015
  19. orangemocha commented on Jun 23, 2015

    @orangemocha
    Contributor

    Fixed with f50c37d and shipped in v0.12.5.

  20. modified the milestones: 0.12.5, 0.12.6 on Jun 24, 2015
  21. misterdjules commented on Jun 24, 2015

    @misterdjules

    This issue was moved to milestone 0.12.6 by mistake because it hadn't been closed after the fix landed and shipped with node v0.12.5. Moving it back to the 0.12.5 milestone to avoid confusion.

  22. ArtemKolodko commented on Jun 23, 2016

    @ArtemKolodko

    @uniring it works from console, thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions