CODEWITHSUNDEEP
node.js
ViVi
ViVi

Reputation: 4474

node.js Setup Wizard ended prematurely in windows 10 64bit

For the last 3 days I have been trying to figure out how to install node.js. I tried every solution that I found on the internet, like disabling certain components during installation, installing both x86 and x64 etc, none of them worked.

My OS is Windows 10 x64. I tried different versions of node.js and they all return the same error shown in the screenshot below.

I tried installing through the command line and got the log. But I could not find anything useful from the log either. Please help. The log can be found here: this path : https://drive.google.com/open?id=1OkkK36hlQeBX0xTNuOuilGaNr1u3S55e

ScreenShot

Upvotes: 5

Views: 4589

Answers (6)

Baliram Babar
Baliram Babar

Reputation: 1

I spent one day for that ....Best solutions is download zip example node-v12.16.2-win-x86.zip.

Upvotes: 0

sguidos
sguidos

Reputation: 31

I had the same issue on a Windows 2012R2 server installing node-v8.11.2-x64, and disabled the McAfee anti-virus to no avail. When I went to clean out the TEMP folder as suggested in this thread, I noticed that several files and folders were locked and could not be deleted, so I rebooted the machine (with the anti-virus disabled). After the reboot, I noticed that the locked temp files had been deleted, and I was able to install node.js, including the Performance Counters and Event Tracking options.

Upvotes: 0

Giuseppe Bertone
Giuseppe Bertone

Reputation: 2244

I had today the same problem with Windows 10 64 bit and Node.js 8.11.2: disabling completly Avast just for the time of the installation solved the issue.

I was trying to install Node.js through node-v8.11.2-x64.exe, but it was rolling back every time at the end. The error in the event log was about wevtutil.exe, version 10.0.17134.1

Upvotes: 0

Ud son
Ud son

Reputation: 21

I disabled the AVG antivirus(version 18.4.3056) but not windows firewall and then i was able to install nodejs.

Upvotes: 2

Hans Passant
Hans Passant

Reputation: 942538

MSI (s) (74:88) [20:49:45:955]: Executing op: ActionStart(Name=RegisterEventManifest,,)
MSI (s) (74:88) [20:49:45:961]: Executing op: CustomActionSchedule(Action=RegisterEventManifest,ActionType=3073,Source=BinaryData,Target=CAQuietExec,CustomActionData="wevtutil.exe" im "C:\Program Files\nodejs\node_etw_provider.man")
MSI (s) (74:A0) [20:49:45:969]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI33C1.tmp, Entrypoint: CAQuietExec
CAQuietExec:  Error 0xc0000409: Command line returned an error.

This is the relevant part of the log and where the install keels over, noise removed. 0xc0000409 is very, very nasty. STATUS_STACK_BUFFER_OVERRUN is a stack corruption error, triggered by code that protects against viral attacks.

Searching for "nodejs install 0xc0000409" takes you to this bug report, notable from December 2015. This issue has been dogging users for a long time, but they are having trouble finding the root cause. The generic workaround is to disable this install step by disabling the installation of the ETW performance counters.

Which works, but is but a band-aid. I think macario1983's comment points at the real troublemaker. It got a lot of helpful votes in just two days. And points at the kind of viral rootkit that programmer's voluntarily install, the kind that can so easily cause a STATUS_STACK_BUFFER_OVERRUN error with no decent way to identify the code that causes it. Anti-malware has become a cure that is worse than the disease, Avast in particular is a truly awful product and does not belong on a programmer's machine.

So decent advice is to 1: disable the anti-malware product before installing Node. 2: get rid of completely if it is Avast. 3: disable the performance counter registration. 4: try the updated installer, patched 4 days ago.

Upvotes: 4

J-Alex
J-Alex

Reputation: 7127

Possible options to solve this:

1. Removing previous installations traces

If you have previous installations, make sure that they were uninstaled completely. If HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{1e2e15d7-3760-470e-8699-b9db5248edd5} record exist in your register, remove it.

2. Disabling Performance Counters

If you don't need Performance counters feature, try to install without it (or maybe even without Event Tracing).

enter image description here

3. Disabling security and giving the full permissions

  1. Clean Temp Folder
  2. Disable your antivirus/firewall for the period of installation.
  3. C:/users/$user/AppData/Local/Temp- Right Click on Temp and go to Properties > select Security Tab > give the user permissions by checking Full Control on permission
  4. Install Node.js

Upvotes: 1

Related Questions