Node: NodeJS Installation Error | Windows 10 64-bit

[froggyman]

• Platform: Windows 10 64-bit

When i try to install node-v7.8.0-x64 i get the following error:

There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor.

my installation log.txt

[refack]

Some previous suggested solutions:
https://github.com/nodejs/node/issues/3431#issuecomment-283794115
If that fails, look at the other solutions:
is:issue "DLL required for this install"

Also node is xcopyable, just unzip your preferred archive from https://nodejs.org/download/release/, and add to your path by opening a command prompt and running:
SETX [/M] Path "%Path%;[your chosen node directory]"

• [/M] for adding for all users (and the SYSTEM user)
• [your chosen node directory] from step 3

[froggyman]

@refack

I would like to tell you to RTFM

I already RTFM several times but it didn't help.

Node is xcopyable

oh. Could you please give a some information because iam a fool?

[refack]

oh. Could you please give a some information because iam a fool?

Hope you're not sarcastic, but even if you are, I'll answer for posterity:

1. To go https://nodejs.org/download/release/latest-v7.x/ (or navigate to your desired version).
2. Pick an archive (for the above case node-v7.8.0-win-x64.zip
3. Unzip to your favorite location (e.g. C:\Program Files\Node, or c:\bin\nodejs)
4. open a command prompt and run SETX [/M] Path "%Path%;[your chosen node directory]"
[/M] for adding for all users (and the SYSTEM user)
   [your chosen node directory] from step 3

That's it. Open a new console and type node -V or npm -V, should work

[froggyman]

I wasn't sarcastic indeed

SETX [/S] Path "%Path%;[my chosen node directory]" gave me an error, but i could do it through the UI.

Thanks!

[refack]

I was just reminded today that you can also set the place where npm bin shims go (those .cmd files that run global modules) to a different directory by npm config prefix [xxxxxx] -g and add xxxxxxx to your path so that the node install dir stays clean.

[Servant707]

@refack
Snarky answers don't help the community. If you are going to help out the community "for posterity", please make sure that you are giving the correct answer.
/S connects you to a remote system via a /U /P (that's a username and password)
The command that you want would be setx /M PATH "%PATH%;[your chosen node directory]"
Just make sure that you don't put a final backslash or that will escape the last quote and give other problems in your path.

Edit: But thank you for pointing me in the correct direction to get Node.JS installed on a Windows 10 Pro box.

[refack]

@Servant707 admittedly late, but I edited my above comments. Thank you.

[art890]

hi, have the same issue with w10 and LTS Version: 10.15.3 (includes npm 6.4.1)

MSI (s) (B8:7C) [14:59:56:454]: Dir (source): Key: NpmFolder    , Object: C:\temp\  , LongSubPath: nodejs\node_modules\npm\ , ShortSubPath: nodejs\1ef5zb6j\npm\
Action ended 14:59:57: ProcessComponents. Return value 1.
MSI (s) (B8:7C) [14:59:57:013]: Doing action: UnpublishFeatures
Action start 14:59:57: UnpublishFeatures.
Action ended 14:59:57: UnpublishFeatures. Return value 1.
MSI (s) (B8:7C) [14:59:57:014]: Doing action: RemoveRegistryValues
Action start 14:59:57: RemoveRegistryValues.
Action ended 14:59:57: RemoveRegistryValues. Return value 1.
MSI (s) (B8:7C) [14:59:57:015]: Doing action: ConfigureEventManifestUnregister
Action start 14:59:57: ConfigureEventManifestUnregister.
MSI (s) (B8:70) [14:59:57:017]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI705.tmp, Entrypoint: ConfigureEventManifestUnregister
MSI (s) (B8:5C) [14:59:57:017]: Generating random cookie.
MSI (s) (B8:5C) [14:59:57:018]: Created Custom Action Server with PID 6520 (0x1978).
MSI (s) (B8:18) [14:59:57:031]: Running as a service.
MSI (s) (B8:18) [14:59:57:035]: Hello, I'm your 32bit Impersonated custom action server.
CustomAction ConfigureEventManifestUnregister returned actual error code 1157 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (B8:7C) [14:59:57:041]: Note: 1: 1723 2: ConfigureEventManifestUnregister 3: ConfigureEventManifestUnregister 4: C:\WINDOWS\Installer\MSI705.tmp 
MSI (s) (B8:7C) [14:59:58:861]: Product: Node.js -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action ConfigureEventManifestUnregister, entry: ConfigureEventManifestUnregister, library: C:\WINDOWS\Installer\MSI705.tmp 

[refack]

@arturas-peceliunas you might try un-checking "Performance Counters" and "Evert Tracing (ETW)"

(apart from that there are many other tricks listed above, with my favorite being just-unzip-and-it'll-work)

[sunilsai]

when i am installing node.js i am getting this error
"""warning 1909.could not create shortcut Node.js command prompt.link.verify the destination folder exists and that you can access it""" can u please suggest solution

[art890]

@sunilsai i also tried to fight with this installer but without any result. Suggest just unzip, move/copy to program files folder and run bat files to setup path variable

[raquetty]

Open a CMD as Administrator, search the path of the msi that you downloaded and execute it via cmd.

example C:\Users\Laptop\Downloads>node-v12.3.1-x64.msi

[Toddwendy]

@arturas-peceliunas you might try un-checking "Performance Counters" and "Evert Tracing (ETW)"

(apart from that there are many other tricks listed above, with my favorite being just-unzip-and-it'll-work)

This is old I know, however if I had a problem today it's likely I'm not alone. To those that have a failed installation error, this fixed it for me.

• Un-checking "Performance Counters" and "Evert Tracing (ETW)" during installation of the msi as @arturas-peceliunas suggested worked perfectly for me. Thanks.-