Important
NVM for Windows has been fully rewritten for modern workflows. Try the v2 release candidate and help us validate it before the final release. There are significant changes from v1, as listed below and in the docs.
The Microsoft/Google recommended Node.js version manager for millions of Windows developers.
NVM for Windows is not the same thing as nvm! (expand for details)
The original nvm is a completely separate project for Mac/Linux only. This project uses an entirely different philosophy and is not just a clone of nvm.
| Feature | Description |
|---|---|
| Compatibility |
• No mandatory administrator privileges. • Shim mode - no symlinks, fast (written in Zig). • Link mode - Zero-latency, junctions with symlink fallback. |
| Automation |
• Per-directory version switching (pinning). • Auto-install missing versions. • Auto-install default global modules. |
| Speed |
• Parallel (multiple) simultaneous installations. • Smaller downloads (7z). • Native extraction. • Caching. |
| Native Integrations |
• Windows Apps • Logging (Windows Event Viewer) • Windows Registry • Desktop Notification Center |
| Customization |
• User-defined aliases. • User-defined default global modules. • Configure local (air-gapped) downloads. |
Commercial Certified Builds are coming in September 2026 for controlled environments. Get notified
| Feature | Description |
|---|---|
| Code Signing |
• Installers • Executables |
| Installers |
• MSI/MST • Microsoft Intune |
| Advanced Logging ⭐ |
• Fully auditable • Structured • Dedicated Event Source • Native SIEM integration |
| Policy Enforcement ⭐ |
• Active Directory/Entra integration • Restrict Node.js versions/ranges (e.g. no EOL versions, LTS only, etc.) • Control nvm-windows, Node/npm/npx settings • Advanced proxy (IWA, WPAD/PAC) support • Private Node.js download mirror |
| Trust Artifacts ⭐ |
• SBOM • SLSA Provenance • VEX Reports |
⭐ = Add-on package
Thanks to everyone who has submitted issues on and off GitHub, made suggestions, and generally helped make this a better project. Special thanks to
- @vkbansal, who provided significant early feedback throughout the early releases.
- @rainabba and @sullivanpt for getting Node v4 support integrated.
- @s-h-a-d-o-w who resolved the longstanding space escaping issue in path names (#355).
- ajyong who sponsored the code signing certificate in late 2021.