No upgrade when running against node install via nvm-windows

[TonyApuzzo]

I also tried using the default path (which is created by nvm). This is on Windows Server 2012 running under PowerShell

PS> [System.Environment]::OSVersion.Version
Major  Minor  Build  Revision
-----  -----  -----  --------
10     0      14393  0

cinst nvm
nvm install 8.16.1
nvm use 8.16.1
npm install --global --production npm-windows-upgrade

PS > npm-windows-upgrade.cmd --npm-version latest --npm-path C:\ProgramData\nvm\v8.16.1
npm-windows-upgrade v6.0.1
Given path C:\ProgramData\nvm\v8.16.1 is a valid directory.
Upgrading npm... -

Upgrading npm (fallback method)... -

You wanted to install npm 6.11.0, but the installed version is 6.4.1.

A common reason is an attempted "npm install npm" or "npm upgrade npm". As of today, the only solution is to completely
uninstall and then reinstall Node.js. For a small tutorial, please see https://github.com/felixrieseberg/npm-windows-upg
rade#usage.

Please consider reporting your trouble to https://aka.ms/npm-issues.

Debug Information:

http_parser: 2.8.0 | node: 8.16.1 | v8: 6.2.414.77 | uv: 1.23.2 | zlib: 1.2.11 | ares: 1.10.1-DEV | modules: 57 | nghttp 2: 1.39.2 | napi: 4 | openssl: 1.0.2r | icu: 60.1 | unicode: 10.0 | cldr: 32.0 | tz: 2017c | os: win32 x64 | OS Name: Microsoft Windows Server 2016 Standard OS Version: 10.0.14393 N/A Build 14393

[ruffin--]

Bump? Any word on this? Having the same issue, and not sure if it's smarter to ditch nvm and deal with node versions manually or figure out how to update npm on Windows when using nvm.

---

EDIT: Some potential solutions from SO.

[keylowgee]

Bump again... even tried installing giving it an explicit path to where nvm.
npm-windows-upgrade --npm-version latest --npm-path C:\Users***\AppData\Roaming\nvm\v12.6.0