CODEWITHSUNDEEP
node.jswindows-installer
Dmytro Pastovenskyi
Dmytro Pastovenskyi

Reputation: 5429

node.js Setup Wizard ended prematurely

I can't install node.js (0.8.9). I'm doing it via Setup Wizard and each time at the end of installation I get message "Node.js Setup Wizard ended prematurely".

What could it be? Thanks.

Upvotes: 26

Views: 39472

Answers (16)

Omore
Omore

Reputation: 620

For version:12.16.1 using Windows 10 I tired many different ways but didn't work. so I do the following ways to make it work.

  1. Install the latest version
  2. Remain the setup file inside /downloads folder
  3. Open cmd (Run as Administrator)
  4. Run node.js msi file using this command -> msiexec /a "../download/node-v12.16.1-x64.msi"
  5. Install it without any problem

After installation open cmd

type > node -v

v12.16.1

Upvotes: 0

Thilina Sandunsiri
Thilina Sandunsiri

Reputation: 590

Most of the times this issue is coming because of the antivirus program which we've installed. First scan the setup file using the antivirus program to make sure it's a virus free file and then stop the antivirus program for few minutes and try to install nodeJS.

Upvotes: -1

Rawmouse
Rawmouse

Reputation: 77

I had a similar problem and it turned out that a file had gone corrupted in the Nodejs directory, by going to the folder "Program files" and giving the folder "nodejs" a new name, I was able to reinstall it properly.

I might add that I couldn´t delete the folder Nodejs because there was a corrupted file in the folder.

Upvotes: 1

hygull
hygull

Reputation: 8730

I also faced this issue multiple(2) times. Finally I disabled AVAST ANTIVIRUS program & tried to install Node.js again.

It worked.

Upvotes: 0

Ron Michael
Ron Michael

Reputation: 1473

Avast Antivirus is the culprit in my case. Disabling it allowed the installation to complete successfully.

Additional background on how Avast messes this up is available in this answer.

Upvotes: 16

MDIT
MDIT

Reputation: 1548

I had the same problem with node 7.1.0-x64 Windows 7 64-bit.

I found that there was

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{1e2e15d7-3760-470e-8699-b9db5248edd5}

in the register on my computer. After I had deleted this entry, node installation passed fine.

This video show all the steps to follow.

Upvotes: 6

Nikhil Ranjan
Nikhil Ranjan

Reputation: 138

I was try to install node-v8.1.4-x64.msi many times in window7 and finally successful. Please follow below step:--

step 1:- goto run and type "regedt32.exe".

step 2:- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib

step 3:- delete it (may be some file are not deleted but all folder s/b delete)

step 4:- Re-install it (Double click on .msi file)

step 5:- Hope this will intalled.

Upvotes: 4

Thomas D
Thomas D

Reputation: 422

Installing without the Performance counters feature made the installation work. All credits go to joaocgreis for the comment on the NodeJS GitHub issue tracker.

Upvotes: 15

devdigital
devdigital

Reputation: 34369

I was having the same issue, I ran the msi from an admin command prompt with the logging option:

node-v0.12.4-x64.msi /lxv C:\Nodejs.log

Inspecting the log showed the following error:

Product: Node.js -- Error 1714. The older version of Node.js cannot be removed. Contact your technical support group. System Error 1612.

Node.js was not listed under Program and Features though, so I ran the Program Install and Uninstall troubleshooter tool (select Run now) at the following site:

https://support.microsoft.com/en-us/mats/program_install_and_uninstall

Stepping through the wizard, selecting the 'trouble with uninstalling' option. The tool then listed 'Node.js' as an installed program. Selecting Node.js and finishing the wizard successfully removed Node.js.

I then ran the msi again from an admin command prompt and the node install succeeded.

Upvotes: 5

shaosh
shaosh

Reputation: 685

I saw the same error because I was trying to install a x86.msi to a 64-bit Win7. Then I changed to the correct x64.msi. It still does not work. I guess it might be permission issue, so I copy the .msi to the C:\Program Files, and install from there, and it succeed.

Upvotes: 0

Jim
Jim

Reputation: 2146

This may help someone in the future. I got a similar message from the installer and found that I could go to command prompt and run the MSI with a command line option to make it create a log file (like node-v0.10.24-x64.msi /lxv C:\Logs\Nodejs.log), where you can choose what the log is called and where it goes.

In my case, we are running in an Active Directory domain environment and some of our folders that are normally local are redirected to a network share so they are always there no matter what computer we log into. Mostly for the benefit of our "My Documents" folder.

When looking through the log I found the actual error that I was getting:

  • WixCreateInternetShortcuts: Error 0x80070005: failed to save shortcut '\ad.local\system\users\<myAcctName>\Start Menu\Programs\Node.js\Node.js website.url'
  • WixCreateInternetShortcuts: Error 0x80070005: failed to create Internet shortcut
  • CustomAction WixCreateInternetShortcuts returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox).

Resolution (for me)

Oddly enough, just running an admin escalated command prompt first, and then running the MSI lets it install correctly.

I think the difference is that when you double-click on an MSI and it escalates, it runs as TrustedInstaller and while that account has access to everything on my box, it does not have network access. When I run an escalated command prompt, it is running as me, but already escalated (the MSI never needs to ask for escalation), so it works.

Final Note:

As of 7/22/2015, the node.js team has finally tracked down the issue with the installer and from 0.12.8 and forward this should be no longer an issue for us. I tested an early version of the installer for them to make sure it worked for me and there were no hitches with the install.

https://github.com/joyent/node/issues/5849#issuecomment-123905214

As of this writing, 7/30/2015, the current version was still 0.12.7, so x.8 has not yet been rolled out to the masses I guess.

Upvotes: 19

Priyanka
Priyanka

Reputation: 105

Running command prompt with administrative rights and then running msi worked for me.

Upvotes: 0

Avisek Ghosh
Avisek Ghosh

Reputation: 19

I also faced it turns out its a problem of windows event log service. First check if Windows Event Log service is on or not. If not started then to fix it, rename or delete the C:\Windows\System32\LogFiles\WMI\RtBackup folder in safemode.

Hope it helps

Upvotes: 2

Zach Saucier
Zach Saucier

Reputation: 26034

I wasn't able to install it the regular way, but I ended up successfully installing it using Chocolatey (a Machine Package Manager built with Windows in mind) and then the nodejs package.

Upvotes: 1

paul
paul

Reputation: 5418

I had this error on Windows 7 x64 (node-v0.10.28-x64.msi) and was able to install by choosing not to install the "Online documentation shortcuts" during the Custom Setup part of the installation. Select "Entire feature will be unavailable".

enter image description here

None of the other solutions worked for me, but I did install as admin and log the output. The logs were not helpful (reported a FatalError, not much else).

Credit where credit's due - I found the answer here: https://github.com/joyent/node/issues/4516

Upvotes: 11

Dmytro Pastovenskyi
Dmytro Pastovenskyi

Reputation: 5429

I did not figure out what was the problem, I just copied installed version and update system variable PATH with path to my node.js and it worked well.

Upvotes: 2

Related Questions