Node.js v5.4.0 is only available in 32-bit.

[vincentlws]

when i try nvm install 5.4.0
i get this : Node.js v5.4.0 is only available in 32-bit.

[coreybutler]

Cannot recreate on Windows 10:

[coreybutler]

@vincentlws - Which version of Windows are you running?

[mm-gmbd]

@coreybutler, getting the same issue.

Running Windows 7 x64.

[mm-gmbd]

Also, I managed to get myself into some sort of pickle trying to force this to work. First, I thought 32-bit executable were fine to run on 64-bit machines (not the other way around, though).

So, after getting the error:

nvm install 5.4
> Node.js v5.4 is only available in 32-bit.

I decided to run the following:

nvm install 5.4 32
> Downloading node.js version 5.4.0 (32-bit)... Download failed. Rolling back.
> Rollback failed. remove C:\Users\[userName]\AppData\Roaming\nvm\v5.4.0\node32.exe: The process cannot access the file because it is being used by another process.
>
> Could not download node.js v.5.4.0 32-bit executable.

So, I thought it was just simply not installed, but I figured I'd check to make sure:

nvm install 5.4 32
> Version 5.4.0 is already installed.

Hmm, so although it said it couldn't be installed, it then said it was installed, so I tried to force nvm to use it:

nvm use 5.4 32
> Now using node v.5.4.0 (32-bit)

Ok, great, now I'm using the latest version of Node. Not great.

npm install [package]
> 'npm' is not recognized as an internal or external command...

Okay, so it doesn't work, I'll just switch back to the 64-bit version that I had installed previously, so I tried to run nvm list. First, I got the following error popup:

But then, the following did output to the console:

nvm list
>
> 5.4.0
> 0.12.0
> 0.10.38

But, nvm use apparently doesn't know about the versions that are included in the list but are 64-bit:

nvm use 0.12.0
> node v.0.12.0 (64-bit) is not installed.

I'll go ahead and move the installed node 5.4.0 folder (C:\Users\[userName]\AppData\Roaming\nvm\v5.4.0\) as mentioned in the first output when I actually forced nvm to install the 32-bit version and report back...

[mm-gmbd]

So, I moved the folder (C:\Users\[userName]\AppData\Roaming\nvm\v5.4.0\) into a backup folder elsewhere and ran the following:

nvm list
>
> 0.12.0
> 0.10.38

No error popup. So, I ran the following:

nvm use 0.12.0
> node v.0.12.0 (64-bit) is not installed.

Not sure what the problem is here, so I just decided to install that version again:

nvm install 0.12.0
> Downloading node.js version 0.12.0 (64-bit)... Complete.

Now, nvm use 0.12.0 works. So, I'm back up and running again, but that was a bit of a headache -- hopefully helpful in the long run, though!

[mm-gmbd]

Also, I'll try updating nvm itself, but at the time I was using the following version:

nvm version
> 1.0.6

[mm-gmbd]

Okay, so I've updated to nvm 1.1.0, but and after re-configuring the proxy (that's one thing that doesn't seem to be copied during the update process, BTW), I now get the following error:

nvm install 5.4
> Version 5.4 is not available. If you are attempting to download a "just released version", ...

Is it saying that it's not available because it's not available in 64-bit? Confused now.

[mm-gmbd]

I'm getting the Version x.x not available... error for every version. Not sure what the deal is... I'm going to try a complete uninstall and reinstall of the latest nvm and see if that gets things back up and working normally.

[javlc]

I had similar problem, could not install node v4.4.3 or others above the 0.x version.
I was using nvm-windows -v 1.0.6.
Updating to nvm-windows to -v 1.1.0 helped overcome the issue.

[ravijangra]

SOLVED:

upgrading to nvm-windows to v 1.1.0 solved this issue

[daoanhnhat1995]

You just need to do
nvm install 5.4 32
It will download node 32 bit version instead of default 64

[coreybutler]

I believe this has been resolved in the latest versions (1.1.0+). Feel free to reopen if anyone still experiences this.

[taylorgoolsby]

Although I don't get the error when I do nvm install 12.16.2, I do get the error when I do nvm install lts/erbium.

nvm install lts/erbium
lts/erbium.0.0
Node.js vlts/erbium.0.0 is only available in 32-bit.

I like using the code names because it will always download the newest minor and patch versions.
For now, specifying the exact version is good enough to work.

---

Windows 10 x64
nvm -v 1.1.7

[hassankhan87]

I am also getting an error, I have recently installed Microsoft updates maybe that break something.

nvm install --lts
--lts.0.0
Node.js v--lts.0.0 is only available in 32-bit.

Windows 10 x64 Version 2004 (OS Build 19041.264)
nvm -v 1.1.7

[gerardcsaperas]

Getting the same error using Windows 10 and nvm 1.1.7:

$ nvm arch
System Default: 32-bit.
Currently Configured: 32-bit.

$ nvm install lts/dubinum
lts/dubinum.0.0
Node.js vlts/dubinum.0.0 is only available in 32-bit.

[coreybutler]

@gerardcsaperas

First, that prompt looks like Linux, not Windows. If you're using macOS/Linux or WSL, then you want https://github.com/nvm-sh/nvm, which is for mac/Linux (and is not related to this project).

If you are actually running Windows, the problem is with nvm install lts/dubnium. NVM4W doesn't yet support named version downloads. You have to specify an actual version of Node, such as 14.13.0. If you need to find a version, you can use nvm list available for a list.

By default, it will download 32-bit versions unless you also explicitly specify the version (i.e. nvm install 14.13.0 64).

[yuusakuri]

I'm not using Unix such as wsl, but I'm having the same problem.

• Windows10 v20H2 64bit
• WindowsPowerShell 5.x
• nvm: 1.1.7

Script1

scoop update nvm

Output1

nvm: 1.1.7 (latest version)
Latest versions for all apps are installed! For more information try 'scoop status'

Script2

nvm install --lts 64

Output2

--lts.0.0
Node.js v--lts.0.0 is only available in 32-bit.

Script3

nvm install --lts 32

Output3

--lts.0.0
Version --lts.0.0 is not available. If you are attempting to download a "just released" version,
it may not be recognized by the nvm service yet (updated hourly). If you feel this is in error and
you know the version exists, please visit http://github.com/coreybutler/nodedistro and submit a PR.

Script4

nvm arch

Output4

System Default: 64-bit.
Currently Configured: -bit.

[coreybutler]

@yuusakuri - --lts is not a supported flag.

[qristiam]

only use your brain...

nvm install 5.4 64

just that. install nvm 5.4 64 bits... so simple

[stemtra]

Hey all, I just managed to solve this by running nvm install 14 instead of nvm install v14. Second one threw the "only available in 32-bit." error, first one made the job smoothly.

Hope this helps

[naveenraina]

Hi, I installed v12.21 and it worked fine. However when I tried installing another version of node with "nvm install node 14.16.0", I received the error -
"node.0.0
Node.js vnode.0.0 is only available in 32-bit."

I changed the command to "nvm install node~14.16.0" and that worked. I have no idea why but it worked.

[Samuel-Berger]

Although I don't get the error when I do nvm install 12.16.2, I do get the error when I do nvm install lts/erbium.

nvm install lts/erbium
lts/erbium.0.0
Node.js vlts/erbium.0.0 is only available in 32-bit.

I like using the code names because it will always download the newest minor and patch versions. For now, specifying the exact version is good enough to work.

Windows 10 x64 nvm -v 1.1.7

I have the same problem, I use Windows 10 and Powershell 7.

PS > nvm install lts/erbium
lts/erbium.0.0
Node.js vlts/erbium.0.0 is only available in 32-bit.

PS > nvm install lts/erbium 64
lts/erbium.0.0
Node.js vlts/erbium.0.0 is only available in 32-bit.

[coreybutler]

For anyone finding this through Google, I'm just going to be blunt... read the docs. The docs and nvm --help clearly explain the syntax to use. Most of these issues in the comments are caused by invalid syntax. The correct syntax is nvm install x.x.x and nvm use x.x.x. There is no preceding v in front of versions. You do not have to specify node, i.e. not nvm install _node_ x.x.x. Named releases are not supported, except current and latest.

Yes, I am aware other version managers support some of these things. I have taken this feedback into consideration. Most of these will be available in NVM4W's successor project, rt (see #565). However; very few new additions (preferably none) will be added to NVM4W. This project is effectively in maintenance mode while I build rt.