

Even if you're using npm in a command prompt, close it.Node.js is a cross-platform runtime environment for server-side JavaScript applications. command prompts and PowerShell windows, etc.

Now perhaps it tries to upgrade but you get another error, "node.exe is being used by another process." wget -OutFile 'C:\Program Files\nodejs\node.exe' if Node.js is NOT living in "Program Files (x86)" perhaps with where.exe, it is living in 'C:\Program Files\nodejs\node.exe'. It cannot find path of the path solution "where.exe node" (courtesy of Lonnie Best Answer)Į.g. You might need to set your proxy npm config set proxy "" (yes, use quotes) It's at least punching through the firewall /proxy (if you have one or have already ran the code get through. If you get `wget : Could not find a part of the path. Run this to update Node.js: wget -OutFile 'C:\Program Files (x86)\nodejs\node.exe' (courtesy of BrunoLM answer) I am not thinking this code actually upgrades your npm version below Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force

Run PowerShell as administrator npm i -g npm // This works uninstall/ reinstall, or manually delete files and folders. I have zero desire to run an EXE file or MSI file. Like some people, I needed to combine multiple answers, and I also needed to set a proxy. Note: some users still report issues updating npm with npm, but I haven't had that experience with v16+.
