About Nvm installer
Skip to content Navigation Menu GitHub Copilot Write better code with AI Security Find and fix vulnerabilities Actions Automate any workflow Codespaces Instant dev environments Issues Plan and track work Code Review Manage code changes Discussions Collaborate outside of code Code Search Find more, search less Explore Learning Pathways Events & Webinars Ebooks & Whitepapers Customer Stories Partners Executive Insights GitHub Sponsors Fund open source developers The ReadME Project GitHub community articles Enterprise platform AI-powered developer platform Pricing Provide feedback Saved searches Use saved searches to filter your results more quickly //voltron/issues_fragments/issue_layout;ref_cta:Sign up;ref_loc:header logged out"}"> Sign up Notifications You must be signed in to change notification settings Fork 3.5k Star 40k DescriptionThe installer currently tries to install nvm to the user account that was used to grant administrator access, instead of the user that invoked the installer. For example, if your user account is set to "standard user" (as it always should be, but never is on a standard single user windows install) and you have the built-in administrator account enabled for UAC purposes, then nvm will try to install to Users\Administrator\AppData\Roaming\nvm instead of the actual user's roaming profile location.
Key features of the Nvm installer that are enabled through these drivers include:
- NVM install hangs indefinitely Issue 2824 nvm-sh/nvm - GitHub
- NVM install node freezes Issue 1614 nvm-sh/nvm - GitHub
- nvm install - errors Issue 334 coreybutler/nvm
- Installing Node.js with NVM. Using NVM to juggle Node.js
- NVMS Lite 2.1 Download: How To Install NVMS on
- NVM: Getting Permission denied with nvm install command
- nvm install - errors Issue 334 coreybutler/nvm-windows
Solves thingssometimes.If the error persists, try to update your npm and Node.js versions or usenvm to manage your Node.js version.# Try to update your npm and Node.js versions or use nvmFirst, update your NPM version by running the following command.Copied!npm install -g npm@latest# 👇️ If you get a permissions error on macOS / Linuxsudo npm install -g npm@latestIf you get a permissions error on Windows, open CMD as an administrator andrerun the command.To open CMD as an administrator:Click on the Search bar and type CMD.Right-click on the Command Prompt application and click "Run asadministrator".Rerun the command.Copied!npm install -g npm@latestnpm install -g npm@latest --forceIf that didn't help, try to download and install the long-term supported versionof Node.js.To install Node:Open the nodejs.org page and download the Windowsinstaller for the LTS (long-term supported) version.Start the installer and click Next on the Welcome screen.Accept the end-user license agreement and click Next.Leave the default destination folder selected and click Next.On the "Custom Setup" screen, click Next.You can optionally install tools for native modules, otherwise, click Next.On the next screen, click on the Install button.Lastly, click on the Finish button.Make sure to close any existing command prompts and PowerShell instances forthe PATH variable to get updated.You can start a new CMD shell and use the npm --version command to makesure Node is installed.Copied!npm --versionnode --versionnpm install -g npm@latestIf the error is not resolved, try to restart your PC after installing the LTSversion of Node.# Use nvm if you need to manage multiple Node.js versionsIf you need to manage multiple Node.js versions, you can use the nvm package.There are 2 nvm packages:nvm for windowsnvm for macOS and LinuxI have written detailed, step-by-step guides on how to install NVM on Windowsand macOS or Linux:Install NVM on WindowsInstall NVM on macOS or LinuxMake sure to follow the step-by-step instructions. Once you switch to thelong-term supported Node.js version, the error will be resolved.
