Chocolatey Community Coffee Break

Join the Chocolatey Team on our regular monthly stream where we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Announcing Chocolatey Central Management 0.10.0

Livestream from
Thursday, 06 October 2022

We recently released our largest update to Chocolatey Central Management so far. Join Gary and Steph to find out more about Chocolatey Central Management and the new features and fixes we've added to this release.

Watch On-Demand
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand
Chocolatey Product Spotlight: Chocolatey 1.2.0 and Chocolatey Licensed Extension 5.0.0

Livestream from
Thursday, 03 November 2022

Join Paul and Gary for this months Chocolatey product livestream where we look at the latest release of Chocolatey 1.2.0, Chocolatey Licensed Extension 5.0.0 and shine a spotlight on the new hook scripts functionality. This opens up so many possibilities for Chocolatey CLI users!

Watch On-Demand
Chocolatey Coding Livestream

Livestream from
Tuesday, 29 November 2022

Join Josh as he adds the ability to manage Chocolatey GUI config and features with the Chocolatey Ansible Collection.

Watch On-Demand
Introduction into Chocolatey with Veeam

Webinar from
Tuesday, 13 December 2022

Join Gary, Paul, and Maurice as they introduce and demonstrate how to use Chocolatey! Questions will be answered live in an Ask Me Anything format.

Watch On-Demand



Downloads of v 1.1.12:


Last Update:

28 Nov 2023

Package Maintainer(s):

Software Author(s):

  • coreybutler


nvm node nodejs node.js version manager windows


  • 1
  • 2
  • 3

1.1.12 | Updated: 28 Nov 2023



Downloads of v 1.1.12:



Software Author(s):

  • coreybutler

NVM 1.1.12

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

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


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


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


Deployment Method:


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.install -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.install -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.install
    name: nvm.install
    version: '1.1.12'
    state: present

See docs at

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

See docs at

cChocoPackageInstaller nvm.install
    Name     = "nvm.install"
    Version  = "1.1.12"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'nvm.install':
  ensure   => '1.1.12',
  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.

Package Approved

This package was approved by moderator Windos on 28 Nov 2023.




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.

# Set error action preference to stop on errors
$ErrorActionPreference = 'Stop'

# Define package name and tool directory
$packageName = $env:chocolateyPackageName
$toolsDir = Split-Path -parent $MyInvocation.MyCommand.Definition
$nvmPath = Join-Path $env:ProgramData 'nvm'

# Package arguments for installation
$packageArgs = @{
    packageName   = $packageName
    fileType      = 'zip'
    version       = '1.1.12'
    url           = ""
    checksum      = '4E076C1B80DBC97A21DA75792CC35F292247C034DAA698044FED30A00020AD6F'
    checksumType  = 'sha256'
    unzipLocation = $toolsDir

# Install the package
Install-ChocolateyZipPackage @packageArgs

# Create ignore file for setup executable
New-Item -Path "$toolsDir\nvm-setup.exe.ignore" -ItemType File

# Start installation process
Start-Process "$toolsDir\nvm-setup.exe" -ArgumentList "/VERYSILENT /NOCIONS /DIR=$nvmPath"
# Set error action preference to stop on errors
$ErrorActionPreference = 'Stop'

# Define package configuration
$packageName = 'nvm.install'
$packageSearch = 'NVM for Windows*'
$fileType = 'exe'
$validExitCodes = @(0)

# Registry paths to search for installed packages
$registryPaths = @(

# Search and uninstall the package
$registryPaths | ForEach-Object {
    Get-ItemProperty -Path $_ -ErrorAction SilentlyContinue |
    Where-Object { $_.DisplayName -like $packageSearch } |
    ForEach-Object {
        Uninstall-ChocolateyPackage -PackageName $packageName `
            -FileType $fileType `
            -SilentArgs $silentArgs `
            -File ($_.UninstallString -replace '"', '') `
            -ValidExitCodes $validExitCodes

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 1.1.11 85805 Friday, April 14, 2023 Approved
NVM 1.1.10 12831 Monday, March 13, 2023 Approved
NVM 1.1.9 86048 Sunday, February 13, 2022 Approved

This package has no dependencies.

Discussion for the NVM Package

Ground Rules:

  • This discussion is only about NVM and the NVM 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, 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