Downloads of v 1.1.9:


Last Update:

16 Mar 2022

Package Maintainer(s):

Software Author(s):

  • coreybutler


nvm node nodejs node.js version management windows admin

NVM (Portable)

  • 1
  • 2
  • 3

1.1.9 | Updated: 16 Mar 2022



Downloads of v 1.1.9:


Software Author(s):

  • coreybutler

  • 1
  • 2
  • 3
NVM (Portable) 1.1.9

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install NVM (Portable), run the following command from the command line or from PowerShell:


To upgrade NVM (Portable), run the following command from the command line or from PowerShell:


To uninstall NVM (Portable), run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade nvm.portable -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade nvm.portable -y --source="'INTERNAL REPO URL'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install nvm.portable
    name: nvm.portable
    version: '1.1.9'
    state: present

See docs at

chocolatey_package 'nvm.portable' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.1.9'

See docs at

cChocoPackageInstaller nvm.portable
    Name     = "nvm.portable"
    Version  = "1.1.9"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'nvm.portable':
  ensure   => '1.1.9',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved by moderator flcdrg on 17 Mar 2022.




Manage multiple installations of node.js on a Windows computer.

This has always been a node version manager, not an io.js manager, so there is no back-support for io.js. Node 4+ is supported. Remember when running nvm install or nvm use, Windows usually requires administrative rights (to create symlinks).


There are situations where the ability to switch between different versions of Node.js can be very useful. For example, if you want to test a module you're developing with the latest bleeding edge version without uninstalling the stable version of node, this utility can help.


nvm-windows runs in an Admin shell. You'll need to start powershell or Command Prompt as Administrator to use nvm-windows

NVM for Windows is a command line tool. Simply type nvm in the console for help. The basic commands are:

  • nvm arch [32|64]: Show if node is running in 32 or 64 bit mode. Specify 32 or 64 to override the default architecture.
  • nvm current: Display active version.
  • nvm install ﹤version﹥ [arch]: The version can be a specific version, "latest" for the latest current version, or "lts" for the most recent LTS version. Optionally specify whether to install the 32 or 64 bit version (defaults to system arch). Set [arch] to "all" to install 32 AND 64 bit versions. Add --insecure to the end of this command to bypass SSL validation of the remote download server.
  • nvm list [available]: List the node.js installations. Type available at the end to show a list of versions available for download.
  • nvm on: Enable node.js version management.
  • nvm off: Disable node.js version management (does not uninstall anything).
  • nvm proxy [url]: Set a proxy to use for downloads. Leave [url] blank to see the current proxy. Set [url] to "none" to remove the proxy.
  • nvm uninstall ﹤version﹥: Uninstall a specific version.
  • nvm use ﹤version﹥ [arch]: Switch to use the specified version. Optionally use latest, lts, or newest. newest is the latest installed version. Optionally specify 32/64bit architecture. nvm use ﹤arch﹥ will continue using the selected version, but switch to 32/64 bit mode. For information about using use in a specific directory (or using .nvmrc), please refer to issue #16.
  • nvm root ﹤path﹥: Set the directory where nvm should store different versions of node.js. If ﹤path﹥ is not set, the current root will be displayed.
  • nvm version: Displays the current running version of NVM for Windows.
  • nvm node_mirror ﹤node_mirror_url﹥: Set the node mirror.
  • nvm npm_mirror ﹤npm_mirror_url﹥: Set the npm mirror.


$ErrorActionPreference = 'Stop';

$packageName = 'nvm'
$nvm = (& where.exe $packageName)

& $nvm off

$ErrorActionPreference = "Stop"

$packageName = 'nvm'

$nodePath = "$env:SystemDrive\Program Files\nodejs"
$nvmPath = Join-Path $env:ProgramData $packageName
$OsBits = Get-ProcessorBits
$NvmSettingsFile = Join-Path $nvmPath "settings.txt"

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $nvmPath
  url           = ''
  checksum      = '81e651ec6d848075d557cca929af682f63a77d4fab44c202f25a20c0aba33749'
  checksumType  = 'sha256'
Install-ChocolateyZipPackage @packageArgs

$NvmSettingsDict = [ordered]@{}
if (Test-Path $NvmSettingsFile) {
  $NvmSettings = Get-Content $NvmSettingsFile
  $NvmSettings | Foreach-Object { $NvmSettingsDict.add($_.split(':', 2)[0], $_.split(':', 2)[1]) }
  Write-Output "Detected existing settings file"
  $NvmSettingsDict.GetEnumerator() | ForEach-Object { "$($_.Name): $($_.Value)" } | Write-Verbose
if (!($NvmSettingsDict['root'])) { $NvmSettingsDict['root'] = $nvmPath }
if (!($NvmSettingsDict['path'])) { $NvmSettingsDict['path'] = $nodePath }
if (!($NvmSettingsDict['arch'])) { $NvmSettingsDict['arch'] = $OsBits }
if (!($NvmSettingsDict['proxy'])) { $NvmSettingsDict['proxy'] = "none" }

$NvmSettingsDict.GetEnumerator() | ForEach-Object { "$($_.Name): $($_.Value)" } | Write-Verbose
$NvmSettingsDict.GetEnumerator() | ForEach-Object { "$($_.Name): $($_.Value)" } | Out-File "$NvmSettingsFile" -Force -Encoding ascii

Install-ChocolateyEnvironmentVariable -VariableName "NVM_HOME" -VariableValue "$nvmPath" -VariableType Machine;
Install-ChocolateyEnvironmentVariable -VariableName "NVM_SYMLINK" -VariableValue "$nodePath" -VariableType Machine;

Install-ChocolateyPath -PathToInstall "%NVM_HOME%" -PathType Machine;

Install-ChocolateyPath -PathToInstall "%NVM_SYMLINK%" -PathType Machine;

$ErrorActionPreference = 'Stop'

$uninstalled = $false
$packageName = 'nvm'
$zipName = ""
$nvm = (& where.exe $packageName)
$EnvVariableType = 'Machine'

$nvmPath = Split-Path $nvm

Uninstall-ChocolateyZipPackage $packageName $zipName
if (Test-Path $nvmPath) { Remove-Item $nvmPath -Force -Recurse }

Install-ChocolateyEnvironmentVariable -VariableName "NVM_HOME" -VariableValue $null -VariableType $EnvVariableType
Install-ChocolateyEnvironmentVariable -VariableName "NVM_SYMLINK" -VariableValue $null -VariableType $EnvVariableType

[regex] $PathsToRemove = "^(%NVM_HOME%|%NVM_SYMLINK%)"
$environmentPath = Get-EnvironmentVariable -Name 'PATH' -Scope $EnvVariableType -PreserveVariables
[string[]]$newpath = ''
foreach ($path in $environmentPath.split(';')) {
    If (($path) -and ($path -notmatch $PathsToRemove)) {
        [string[]]$newpath += "$path"
        "$path added to `$newpath"
    else {
        "Path to remove found: $path"
$AssembledNewPath = ($newpath -join (';')).trimend(';')

Install-ChocolateyEnvironmentVariable -variableName 'PATH' -variableValue $AssembledNewPath -variableType $EnvVariableType
"Path with variables"
$newEnvironmentPath = Get-EnvironmentVariable -Name 'PATH' -Scope $EnvVariableType -PreserveVariables
"Path with values instead of variables"

$uninstalled = $true

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
NVM (Portable) 1.1.7 173908 Thursday, August 30, 2018 Approved
NVM (Portable) 1.1.5 43551 Monday, June 26, 2017 Approved
NVM (Portable) 1.1.1 3453 Saturday, November 12, 2016 Approved

This package has no dependencies.

Discussion for the NVM (Portable) Package

Ground Rules:

  • This discussion is only about NVM (Portable) and the NVM (Portable) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or NVM (Portable), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus