NVM installation error on Windows. Cannot find the npm file

Question

I was using NVM to insall node js. But when i try to install this specific version nvm install 14.17.3 it is not able to detect the npm file. the .zip file for npm is not found in the specified directory.

C:\Users\Infra>nvm install 14.17.3
Downloading node.js version 14.17.3 (64-bit)...
Complete
Downloading npm...
Creating C:\Users\Infra\AppData\Local\Temp\nvm-install-3421872285\temp
Downloading npm version 6.14.13... Complete
Installing npm v6.14.13...
error installing 14.17.3: open C:\Users\Infra\AppData\Local\Temp\nvm-npm-2947621574\npm-v6.14.13.zip: The system cannot find the file specified.

Answer 1

I was having the same problem. I even tried to change the node and npm mirror, but same error. I just rolled back to nvm version 1.1.12 and it worked just fine.

• Tassisto: I wanted to install nvm install 14.21.3, couldn't find a solution with NVM
• Yasin Asadnezhad: It was better to explain more regarding rollback in the nvm version. How did you do? with which command?
• m.spyratos: Just uninstall from programs and download the previous version from Github to reinstall
• Yogurtu: So it means we need a NVM for NVM now... a "NVMVM"

Answer 2

https://github.com/coreybutler/nvm-windows/issues/1209

Bug in NVM-Windows - planned to be fixed in next version

Potentially useful workaround is to go back to a previous NVM version like v1.1.12

• Uday Teja: Worked! almost wasted by install/uninstall and changing the env path and system restart
• andreszs: In other words, we would need a Node Version Manager Version Manager to mange NVM versions and address this problem... Could this be any worse??
• Kavindu Vindika: This should be marked as the solution for this issue!!!

Answer 3

Solution for those who use NVM via Chocolatey:

• Open CMD or PowerShell as Administrator.
• Copy and execute this command:

  choco install --force --version 1.1.12 nvm.install
  

• Enter A when asked.
• If you get a dialogue box by NVM asking to take control of your already installed different versions of Node then just click on Yes button.
• Keep clicking on Yes button if the dialogue box keeps appearing again and again.

• pkalinow: First run choco uninstall nvm to get rid of the current, buggy version. Without it, the installation is going to fail.

Answer 4

I had a similar error when installing the old version of nodejs 0.12.2. I need this version to work with the old version of WebOS 3.4 installed on my TV.

Before that, I already had nodejs versions 23.10.0 and 16.20.2 installed

I downloaded the node-v0.12.2 Win-x64.msi installer from here https://nodejs.org/en/blog/release/v0.12.2 and installed it in the default folder (let's say it was the C:\nvm4w\nodejs_0.12.2 folder. It doesn't matter now).

After installation, the following files were in the folder: Installed Nodejs 0.12.2 files I checked, the nodejs version 0.12.2 was not listed anywhere. I searched and found that versions 23.10.0 and 16.20.2 are present in the folders of the same name C:\Users\KS\AppData\Local\nvm. By analogy, I created a folder v0.12.2 and dropped the contents obtained during the installation of node-v0.12.2 Win-x64.msi into it.

The result was as follows: Folder with all installed versions of Nodejs When unsuccessfully attempting to install Nodejs 0.12.2 with the command nvm install 0.12.2 the file npm-v2.7.4.zip was downloaded to the folder C:\Users\KS\AppData\Local\Temp\nvm-install-3885601035\temp But for some reason the installer was looking for this file in the folder C:\Users\KS\AppData\Local\Temp\nvm-npm-2168612958. There was such a folder, but it was empty Error "Cannot find the npm file" I took the file npm-v2.7.4.zip, unpacked it into a separate folder and ran the command nvm use 0.12.2 (this is mandatory!) In the folder C:\nvm4w\nodejs (the appearance of which changes depending on the version of nodejs used) I created the node_modules folder, in it I created the npm folder, and in it (that is, in the folder C:\nvm4w\nodejs\node_modules\npm) I put all the contents of the npm-v2.7.4.zip archive.

Now, when using Nodejs version 0.12.2, everything is the same as when using Nodejs version 16.20.2 and 23.10.0 Installed Nodejs versions Accordingly, the command is executed For Nodejs 0.12.2 npm 2.74 is used