Node.js installation error - node.js

I tried to install node.js on a Windows 8 machine, but I got the following error:
The cabinet file 'media1.cab' required for this installation
is corrupt and cannot be used. This could indicate a network error, an
error reading from the the CD-ROM, or a problem with this package.
I downloaded the installation file from the node.js website at http://nodejs.org/download/.
How I can solve this problem.
My system specifications are OS : Windows8 32bit, RAM : 4GB, CPU :
Intel Pentium P6200, 2.13Gz, Dual Core

I was experiencing the same error message trying to install on Windows 7.
I was able to fix this issue and successfully install by:
changing the directory for installation.
Instead of installing within my "Program Files (X86)" folder, I installed into my "Program Files" folder
My suggestion is to try installing to a different directory as this solved the problem for me.

For anyone stumbling here, my problem (on win 7) was I accidentally downloaded the 32-bit version by mistake. Getting the 64-bit version was the solution.

Actually above none of answers ara not worked for me. I'm using windows 8.1 x64 . So i'm trying install nodejs.msi. Actually i can not install it. So i have used Chocolatey package manager. This is the command that i used for install nodejs. choco install nodejs.install Thats all it worked :)

Related

NVM for Windows successfully installed but CMD prompt informs my version of Node.exe not compatible with my Windows version

I'm on a Microsoft Surface Pro X (it features Windows 10 Home on ARM 64-bit processor) trying to install Node.js. I've decided to use NVM for Windows. I can successfully install and get NVM for Windows running correctly. To my understanding, I'm able to install different versions of Node (i.e. 16.16.0 and 16.13.1, for example, both LTS) as shown in below graphic. But when I try to run Node, I get the error "This version of C:\Program Files\Nodejs\node.exe is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher."
I am not clear on the why this is happening. Am I not downloading a version of Node that is compatible on my ARM 64-bit processor? I've read through several closed issues on the GitHub page but I haven't encountered someone bringing up this same error. I'm pretty confident it does NOT have to do with the integrity of my symlinks too, or my system environment variables. See below:
Your help and insight is appreciated. Thanks.

Node JS 8.12.0 unable to install on windows 64 bit.

node-v8.12.0-x64.msi Using this file downloaded from the website, I am installing Node js on my windows 64 bit. Home Personal computer.
I do have Java installed.
UNable to install node js as there is some missing DLL which I am not understanding.
Kindly please help.
node js win64 installation error missing dll
According to similar problems encountered on the web, this error may come from different reasons:
Windows is not updated.
Not full access to the folder: C:\Users\\AppData\Local\Microsoft\Windows\ or C:\Users\\AppData\Local\Temp.
Please ensure those two points are ok...

Update nodejs in cygwin

Sometime back I've installed nodejs via cygwin which shows me the version 0.4.12 when I do node -v in bash.
Recently I've installed nodejs with the window installer which shows me the version 0.10.20 in window command prompt.
My Problem is I'm using Claymate for GumbyFramework in cygwin and it requires nodejs version above 0.8.0. How can I update the Nodejs in cygwin to the latest version?
Btw I'm using Windows Vista OS.
Pls. help!! Thanks in Advance..
Please know that Cygwin is not a supported platform. There would be a node version which would break things for you. The latest version that compiles natively on Cygwin is 0.4.12. Though the wiki page mentions some people had success building Node.js 0.10 on MinGW+MSYS. Try the following instructions : http://opensourcepack.blogspot.co.uk/2013/06/nodejs-with-posix-path-support.html
Don't mess with compile on Windows. You may want to just replace the old version Node.exe file with the newer Node.exe file on disk. You should be able to find the Cygwin folders within Windows explorer. You can search the entire disk, in windows not cygwin, for the file name node.exe. You should see the node.exe windows is finding, and the one cygwin is finding, under the cygwin folders.
Rename the cygwin node.exe and copy in the newer node.exe. Now, you nay get an issue with npm, in which case you may want to try the same thing with the npm folder.
I know cygwin isnt officially supported, but when you get it installed correctly it works.

"The installer has encountered an unexpected error installing this package...". Is it possible to install Node.js (v0.10.15) on Windows XP?

I want to use Node.js under Windows XP. I've downloaded the node-v0.10.15-x86.msi installer but when I try to install Node.js I always get this error at the middle of the process:
The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2908.
Here is a screenshot:
Is it possible to install Node.js on Windows? I cannot find any installation instructions on their site. I have AMD Athlon XP 1833 MHz processor. It is quite old processor. May this be the reason?
So, I figured out how to install it :)
I did a double click on node-v0.10.15-x86.msi file in order to install Node. And that caused an error.
.msi files shouldn't be installed that way. I found a solution on this page http://thebackroomtech.com/2007/08/23/howto-extract-files-from-a-msi-file-using-the-windows-command-line/
So my steps in Windows command line. I pointed a directory where to unpack node-v0.10.15-x86.msi to:
C:\>msiexec /a "C:\Downloads\Programs\Node.js\node-v0.10.15-x86.msi" /qb TARGETDIR="C:\Program Files\nodejs"
And now it works. It unpacked Node.js and all its dependencies to C:\Program Files\nodejs. I just added the directory to PATH.
I'm glad I can use Node on Windows. Working under Ubuntu is a pain.
I had the same problem. For resolve this problem you need to remove this key from registry
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\
Installer\UserData\S-1-5-21-1123561945-1935655697-1060284298-1003\
Components\AD95649F068525549B26938D7D18FEA7
Founded here
For me the S-1-5-21 was different, I renamed it to _del
HKEY_LOCAL_MACHINE
\SOFTWARE
\Microsoft
\Windows
\CurrentVersion
\Installer
\UserData
\S-1-5-21-1292428093-1606980848-1188629396-500_del

IBM installation manager cannot be launched in fedora 17(64bit)

Here's the error msg goes when i try to run the IBM installation manager:
java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
/opt/IBM/InstallationManager/eclipse/configuration/org.eclipse.osgi/bundles/447/1/.cp/libswt-pi-gtk-3659.so (libXtst.so.6: cannot open shared object file: No such file or directory)
swt-pi-gtk (Not found in java.library.path)
/tmp/swtlib-32/libswt-pi-gtk-3659.so (libXtst.so.6: cannot open shared object file: No such file or directory)
/tmp/swtlib-32/libswt-pi-gtk.so (/tmp/swtlib-32/lib/libswt-pi-gtk.so.so: cannot open shared object file: No such file or directory)
However, those files does exist. I also already have SWT lib installed. Any one have experience on this issue before?
IBM Installation Manager can only run if 32bit GTK components installed.
Here are the packages I install on Redhat 64bit in order to run IBM Installation Manager:
Install required packages for IBM Installation Manager UI on Redhat x64
Should be similar packages in Fedora.
I don't remember about Installation Manager but for WAS installation launching setup.jar itself did help:
java -jar setup.jar
I had this issue when tried to install CM on Linux Fedora 17 x86_64 bits and this command solved my issue
yum install gtk2.i686 gtk2-engines.i686 PackageKit-gtk-module.i686 PackageKit-gtk-module.x86_64 libcanberra-gtk2.x86_64 libcanberra-gtk2.i686
After execute it i can run interactive installation.
This was helpful for steering me in the right direction for solving the problem on rhel 6.5 on IBM power. i installed the equivalent packages using the .ppc instead of .ppc64 files (since the installer is PPC) and then i had to add these 2 lines at the bottom of the install.ini according to ibm support article swg21688528 as follows:
-Dorg.eclipse.swt.internal.gtk.useCairo=false
-Dorg.eclipse.swt.internal.gtk.cairoGraphics=false
Parke

Resources