Reputation: 1360
I am trying to install node-v0.10.35-x86.msi on my windows 32 bit system, it will automatically rolling back at the end...
I had tried some solutions given in the following link...
node.js Setup Wizard ended prematurely
none of them worked for me....
Here is my installer log file of this node.js
Please provide quick solutions....
Upvotes: 3
Views: 6814
Reputation: 759
I tried most of them but finally I am able to fix by expanding the Node.js runtime node in order to see the Performance counters feature and disabling it.
Following video helped me: https://youtu.be/dLsiNamyad4?t=2m30s
Upvotes: 1
Reputation: 117
Try in cmd :
reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{793c9b44-3d6b-4f57-b5d7-4ff80adcf9a2}" /s
reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{1e2e15d7-3760-470e-8699-b9db5248edd5}" /s
If one of those exist delete it. It solve my problem.
Upvotes: 5
Reputation: 41
I had the same problem, solution is "Windows Eventlog". Run eventvwr.msc
on the "Run" box, check "Installation" and "Application" pages of the Windows protocol section.
Upvotes: 1
Reputation: 106
It seems that the following command
"wevtutil.exe" im "C:\Program Files\nodejs\node_etw_provider.man"
is failing on your setup with the following error:
ERROR - Error 0x800706b5: CAQuietExec Failed
A helpful suggestion on how to fix this issue can be found at http://blogs.technet.com/b/odsupport/archive/2010/12/30/troubleshooting-office-installation-failures.aspx:
This issue can occur if the Windows Event Log service is not running. Click on start, search and type in services.msc and hit enter. Scroll down to the Windows Event Log service, and ensure it is set to automatic. If it is not running right click on it and choose start. If you get an error like the following:
Error 4201: The instance name passed was not recognized as valid by a WMI data > provider.
Then please check the permissions on "c:\windows\system32\logfiles\wmi\RTbackup"
If the system account doesn’t have full control, grant the system account full > control and reboot. After reboot check and see if the Windows Event Log service is started in services.msc.
Upvotes: 1