NVM for Windows maintains a single symlink that is put in the system
PATHduring installation only. Switching to different versions of node is a matter of switching the symlink target. As a result, this utility does not require you to runnvm use x.x.xevery time you open a console window. When you do runnvm use x.x.x, the active version of node is automatically updated across all open console windows. It also persists between system reboots, so you only need to use nvm when you want to make a change.
source
Symlink is located under %NVM_SYMLINK% wich defaults to C:\Program Files\nodejs and versions are downloaded under %NVM_HOME% which defaults to C:\Users\<user>\AppData\Roaming\nvm
Videos
Hello gang, I am having issues using Node version manager on windows. I have checked my environmental variables, manually added paths via my bash file, and i used the powershell, command prompt, and git bash. NVM commands work fine but node -v and npm -v will not work at all. Incredibly frustrating as i was in the middle of working on AWS services so this is incredibly counter productive. Any advice?
I should add that i was using the latest version of node up until today without any issues. An application or project i was working on necessitated an older version of Node.js. The Windows support article https://learn.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-windows explains in few details additional processes i could take to resolve the issue so i have been relying on information found on the web. I can send photos of my environmental variables although i am very cautious uploading any information regarding my local machine via a subreddit about programmers learning. Unfortunately not all humans live for the betterment of the human race. If anyone has dealt with this problem. let me know a resource i can delve into or how you resolved the issue.