# nvm-windows for Windows PC - **Name:** nvm-windows for Windows PC - **Version:** 2.0.1 - **Developer:** Corey Butler - **License:** Open Source - **Platform:** Windows - **Requires:** Windows 10 / 11 - **File type:** EXE Installer - **Size:** 10.6 MB - **Category:** Developer Tools - **Updated:** 2026-10-21 - **SHA-256:** 2ba6ab6290fdc7d1e608e76c97577ca6e1df772b2d59ab8ebc01e10788de8e57 - **Canonical page:** https://filecobra.com/app/nvm-windows-node-manager-pc/ - **Download page:** https://filecobra.com/download/nvm-windows-node-manager-pc/ - **Direct download:** https://github.com/coreybutler/nvm-windows/releases/download/v2.0.1/nvm-2.0.1-x64-setup.exe > nvm-windows installs multiple Node.js versions side by side and switches between them with one command — essential for developers whose projects each pin a different Node release… nvm-windows (Node Version Manager for Windows) installs and switches between multiple Node.js versions on one machine from the command line. Run 'nvm install lts', 'nvm use 22', and every project gets the exact Node runtime it expects — no reinstalling, no PATH surgery. Version 2.0 is a ground-up rewrite with faster switching, per-shell sessions, and cleaner integration with npm, pnpm and yarn shims, built for developers who juggle projects pinned to different Node releases. ## Installation 1. **Download the installer** — Download nvm-windows from the official vendor link on this page. 2. **Run the setup** — Open the downloaded installer file and follow the on-screen installation steps. 3. **Launch the app** — Start nvm-windows from the Start menu or desktop shortcut. ## Editorial verdict If you develop with Node.js on Windows, version conflicts are a tax you pay weekly: one project needs Node 18 for its build chain, another demands 22, and a client site only runs on 20. nvm-windows removes the tax. Install as many versions as you need, type 'nvm use 20.11.0', and the terminal — and everything launched from it — sees exactly that runtime. The 2.0 rewrite keeps the familiar commands but rebuilds the engine: switching is faster, elevation prompts are rarer, and the symlink-based switching that confused antivirus tools in the 1.x era is handled far more cleanly. It remains a developer's command-line tool, with the assumptions that brings: you should uninstall existing standalone Node installations first so PATH entries do not fight, and global npm packages are per-version by design, which surprises newcomers when a global CLI 'disappears' after switching. There is still no per-directory automatic switching like Unix nvm's .nvmrc hooks without a small wrapper script. None of that changes the verdict for its audience: this is standard equipment on a Windows dev machine, installed before the first project clone. Teams can pin the same Node version in an onboarding script and stop debugging environment drift by hand. ### Strengths - Installs and switches unlimited Node.js versions with single commands, ending the uninstall-reinstall cycle when projects pin different runtimes. - The 2.0 rewrite switches versions faster and with fewer UAC prompts than the 1.x line, and handles permissions and paths more predictably. - Works with the standard Node workflow — npm, npx, corepack, pnpm and yarn all resolve through the active version automatically. - Supports version aliases like lts and latest, architecture selection, and a configurable mirror for restricted networks. - Free and open source, tiny footprint, and scriptable, which makes standardizing a whole team's Node version a one-line onboarding step. ### Trade-offs - Existing standalone Node installations should be removed first; leftover PATH entries are the number-one cause of 'nvm says one version, node runs another'. - Global npm packages do not follow you across versions, so global CLIs must be reinstalled per Node version or managed with a dedicated tool. - It is command-line only, and automatic per-project switching from .nvmrc files needs a small PowerShell wrapper rather than being built in. ## FAQ **Is nvm-windows free?** Yes. nvm-windows is free and open source under the MIT license. Download it only from the official GitHub repository (coreybutler/nvm-windows) — several lookalike sites bundle it with unwanted extras. **Is nvm-windows the same as nvm for Mac and Linux?** They solve the same problem with similar commands, but they are separate projects with different code. nvm-windows is a native Windows implementation by Corey Butler, not a port of the Unix shell script. **Do I need to uninstall Node.js before installing nvm-windows?** It is strongly recommended. Remove any existing standalone Node installation and make sure its folders are gone from your PATH, then install nvm-windows and use it to install your Node versions — this prevents version conflicts. **How do I switch Node versions?** Install versions with 'nvm install 22' (or 'nvm install lts'), list them with 'nvm list', and activate one with 'nvm use 22'. Open a fresh terminal afterwards if an existing window still reports the old version. **Does nvm-windows work in PowerShell and Windows Terminal?** Yes. It works from Command Prompt, PowerShell, and Windows Terminal. After switching versions, terminals pick up the change; an administrator terminal may be required for the 'nvm use' command depending on your setup. --- Source: https://filecobra.com/app/nvm-windows-node-manager-pc/ · Mirrored from the publisher's own release channel by FileCobra. FileCobra runs no antivirus lab of its own.