Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Windows node installer >= v0.8.0 fails in Windows 7 #3620

Open
briantrice opened this Issue · 18 comments

10 participants

Brian T. Rice Ben Noordhuis Bert Belder normantan Jim Schubert Scott Blomquist Jack pramodx aedile paulodiff
Brian T. Rice

0.7.9 installs correctly, but the 32 and 64 bit versions of 0.8.0 and 0.8.1 fail to install, beginning to rollback near the end of the progress bar. I don't know what install log to consult. The separate node.exe release executables run as expected.

Bert Belder
Owner

@briantrice

I have no clue why that works, I have never seen this happen anywhere. Maybe looking at the windows event log can help out here.

If you just want a quick workaround you could try to remove old version of node before installing the new version? Use the "add/remove programs" dialog for that.

Brian T. Rice

Yes, it is strange. I did uninstall a previous version of Node, but that didn't change the result. Also, I rebooted (the joys of Windows). I'll see about the Event log and follow up with what details I can.

normantan

Also had this problem as well. No problems with 0.7.12.

Event log as follows:

Product: Node.js -- Error 1303. The installer has insufficient privileges to access this directory: C:\Users\norman\AppData\Roaming\Microsoft\Installer. The installation cannot continue. Log on as administrator or contact your system administrator.
(NULL)
(NULL)
(NULL)
(NULL)
(NULL)

7B44433442463637312D394633322D343538412D393930372D4138343539424633303737377D

Edit: Should add that this was running as an administrator so shouldn't be an issue there.

Bert Belder

Is this still happening for people? The 0.8.0 installer had some glitches due to a problem with the installer build process, but this shouldn't be an issue with versions >= 0.8.1.

In case there are still problems with the installer, try this:

  • Uninstall all previous node versions.
  • Open %APPDATA%\Microsoft\Installer, and delete all subdirectories that have node related content in them.
  • Try installing again.

Please report if that works.

normantan
Brian T. Rice

I have the same result as @normantan reports. I also see this warning ahead of that:

An error occured while refreshing environment variables updated during the installation of ''. Some users logged on to the machine may not see these changes until they log off and then log back on.

Jim Schubert

I helped a user on Stackoverflow with an issue related to installing v0.8.12 in Windows 7 x64: http://stackoverflow.com/q/13076825/151445

His install failed on creating shortcuts. I wasn't able to reproduce his issue, but modifying the installer allowed him to proceed with installation.

Brian T. Rice

May I suggest that shortcut/menu creation be optional?

Bert Belder

Sure, I'd be happy to take a patch for that :-)

Brian T. Rice

Okay, I'll try to set that up.

Scott Blomquist
Owner

@jimschubert, that SO issue is quite probably related to #4021. @briantrice, I'm willing to help if you need it.

Jack

Looks like you know what's up but just to add some info, http://imgur.com/dkXXF

That's a directory it correctly doesn't have write permissions for but node should not fail to install because is can't write a desktop icon.

Brian T. Rice

I am way too busy with the day-job for this one, alas.

pramodx

Node.js setup 0.8.18 has issues setting up on Windows 7 32bit OS. Says rolling back action towards end of setup. Works fine on 64bit OS

aedile

This is still an issue on Windows 7 32bit. Titanium Studio tried installing 0.8.17 as part of the development environment and that failed. I then tried installing the latest release, 0.8.20, manually and it failed in the same manner.

Brian T. Rice

As of 0.8.21, both 32-bit and 64-bit installers fail on Windows 7 64-bit. The installer modification worked, but is inconvenient.

paulodiff

Installation rollback on windows 8 x64
Tnx piscisaureus i removed %APPDATA%\Microsoft\Installer and worked!!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.