Node: NodeJS install problem - Error 1603

Created on 3 May 2016  路  4Comments  路  Source: nodejs/node

version: any
platform: Windows 7 64 bit
subsystem: none

Hey Guys,

So yesterday I wanted to update my Node version, unfortunately, even though the update was a success, when checking my Node version it was still displaying an old version. Whatever I tried, there was no way to get Node updated properly. So I decided (I'm on Windows btw) to remove all my Node folders and NPM folders.

Then I downloaded the .msi file from the Node site. However, at the end of installation a rollback was done and the installation ended prematurely.

So I tried a few things, like starting the installation from command line. Starting command line as an administrator and trying the install. Trying older version, .exe files. Also installed Chocolatey and tried to install Node through there. However, it all failed. So even though I googled for hours, tried it all, I have no more clue what to do. Maybe there is something in Registrar from old Node files that is blocking the install? It's a wild guess. I also removed all temp files and tried the install. No result.

I also logged the installation progress;

CAQuietExec: Error 0x8007000d: Command line returned an error.
CAQuietExec: Error 0x8007000d: QuietExec Failed
CustomAction RegisterPerfmonManifest returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Any suggestions are super welcome!

install windows

Most helpful comment

In case someone else lands here with the same problem, the solution in #4329 worked out fine for me.

All 4 comments

Hi @Xamsix ! If I understood correctly, there are two issues here:

  1. Node does not update, the old version is always used. That's strange. If you download a .exe such as from http://nodejs.org/dist/latest/win-x64/ and run it by double clicking, process.version has to be correct. If you run it from the command line, make sure that where node.exe prints the correct path.
  2. Installation fails with Performance Counters. That's a duplicate of https://github.com/nodejs/node/issues/4329 . If you don't need Performance Counters, just disable them during the installation. If you need then, please run the commands from https://github.com/nodejs/node/issues/4329#issuecomment-200795764 and paste the output.

Thanks @joaocgreis for your comment!

  1. Since I removed all Node files it's currently not a real problem anymore. I'll keep this in mind for when installation is a success, thanks.
  2. Oh my god, thank you so much. I tried hours and hours, but didn't ran into this topic on via Google or checking here. Such an easy fix eventually haha.

Thanks! This topic can be closed, my problem was fixed :D

In case someone else lands here with the same problem, the solution in #4329 worked out fine for me.

I did two things:

  1. un-checking "Event tracing(ETW)"
  2. And services.msc enabled Volume Shadow Copy Service I set automatic

I tried all but it麓s fix to me. I hope that help you.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

TazmanianDI picture TazmanianDI  路  127Comments

egoroof picture egoroof  路  90Comments

nicolo-ribaudo picture nicolo-ribaudo  路  147Comments

jonathanong picture jonathanong  路  91Comments

mikeal picture mikeal  路  197Comments