How to uninstall nvm-windows on Windows

nvm-windows manages Node.js versions under its own install folder and adds itself to your PATH; removing it does not remove the Node versions it installed on its own. This guide covers nvm-windows installed per-user from the CoreyButler.NVMforWindows winget package.

Quit anything using Node first

Close any terminal that has a Node process running through an nvm-managed version. Check Task Manager (Ctrl+Shift+Esc) for nvm.exe or node.exe before you uninstall.

Remove the app with its own uninstaller

Go to Settings › Apps › Installed apps, find NVM for Windows, and choose Uninstall, or run:

winget uninstall --id CoreyButler.NVMforWindows

Where the data lives

Location	What it holds	What to do
`%LOCALAPPDATA%\Author Software\nvm`	The nvm-windows program, its settings file and every Node version you installed with `nvm install`	Removed whole by the uninstaller; back up any global npm packages you installed under a specific Node version first
`%ProgramData%\Author Software\nvm\logs`	A small runtime log file	Not touched by the uninstaller; safe to remove

Check the result

Run these read-only commands after the uninstall finishes, ideally from a new terminal window:

nvm version
winget list --id CoreyButler.NVMforWindows
Test-Path "$env:LOCALAPPDATA\Author Software\nvm"
$env:Path -split ';' | Select-String 'nvm'

nvm version failing with "not recognized" means nvm-windows is gone from your PATH; printing a version means either the uninstall did not finish or another install is still on your machine.
A completed winget list query with no match means the package record is gone; a matching row means the uninstall did not finish.
Test-Path "$env:LOCALAPPDATA\Author Software\nvm" returning False means the install folder, Node versions included, is gone; True means it is still there.
The last command listing a line means your user PATH still has an nvm entry; Mole does not edit PATH entries, so remove one yourself in Settings › System › About › Advanced system settings › Environment Variables if you want it gone.

If you installed it with winget

winget uninstall runs the same Inno Setup uninstaller (unins000.exe /SILENT) Settings › Apps uses and removes the same install folder; it does not touch the log folder or your user PATH.

What Mole lists

For nvm-windows installed per-user from winget:

The install folder, the user Start Menu folder (which also held a Sync.lnk shortcut) and its Desktop shortcut are selected by default.
The nvm protocol registration under HKCU\SOFTWARE\Classes is selected by default and backed up to a .reg file first.
%ProgramData%\Author Software\nvm\logs is not part of this list. The user PATH entries nvm-windows adds are never edited by Mole.

What this test covered

Tested with nvm-windows 2.0.0 installed through the arm64 Inno Setup package, per-user scope. Because the test ran from an elevated session, the per-user uninstaller first failed with a ShellExecuteEx error and then asked for administrator access when retried; a normal per-user install and uninstall does not hit either one. No Node version was installed through nvm during the test.