-
Notifications
You must be signed in to change notification settings - Fork 29.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node.js Setup Wizard ended prematurely #4329
Comments
Wherever your problem is, it's somewhere between lines 25928 and 25970 - before that, it was installing all the files, and after that, it was removing all of them and unregistering all of the components. Not sure quite where your error is - interesting that it's happening on all versions. |
cc @nodejs/build? |
@samarthRT Can you make sure there is no previous version installed in Control Panel, and uninstall it from there if there is? The root cause for this may be wixtoolset/issues#4462 . As a workaround, if uninstalling first does not work, can you try to install without the "Performance counters" feature (remove under "Node.js runtime" during installation)? |
@joaocgreis Thanks for reply. I didn't found any previous versions installed on the system. However, installing without the "Performance Counter" feature does the job. |
Performance counters allow for node to be monitored: https://technet.microsoft.com/en-us/library/cc749249 @samarthRT I'm glad it worked. We can reopen if this becomes an issue for you again. |
@samarthRT if you still have the machine where the error happened, can you run these two commands and paste the output here? Thank you! 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 |
Hey @Compynerd255, I couldn't locate these keys (GUIDs) on my system registry. Are we sure these are not system specific ? |
They are used by node, newer and older versions. If there was something there, it could be causing conflict, and with this we would know what. But as there's nothing there, it's not the cause. Thanks! |
Hi @joaocgreis, m facing another issue. Please suggest Now as I'm trying to access the npm command, it results in another error : C:\WINDOWS\system32>npm npm ERR! Cannot find module 'glob' npm ERR! Please include the following file with any support request: *npm-debug.log * : |
Hi @joaocgreis, Unselecting the "performance counter" during the installation did the job for me, but I have run the req queries which you provided and got a result for the second one: C:\Windows\system32>reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib_V2Providers{1e2e15d7-3760-470e-8699-b9db5248edd5}" /s HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib_V2Providers{1e2e15d7-3760-470e-8699-b9db5248edd5} HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib_V2Providers{1e2e15d7-3760-470e-8699-b9db5248edd5}{3a22a8ec-297c-48ac-ab15-33ec93033fd8} Deleting this entry fixed the issue for me which means that I did not have to unselect the "performance counter". |
@ilkercat thanks! @samarthRT sorry for the delay, I had missed this one. Your npm is installed under appdata, so can you try:
If that doesn't help, perhaps the best way forward would be to ask on IRC or create an issue in npm. |
@ilkercat thanks! This worked for me too. |
I had the same problem with node 5.5.0 and 6.2.2 in Windows 7 64-bit. |
Win7 64-bit as well Node 6.3 install. Won't work without not installing |
I removed this item, and the installation was okay |
I was facing same issue on win7 64 bit sp1 machine. |
For anyone finding this issue with the same problem: The solution for this seems to be running the next two commands in a Administrator Command Prompt:
The first command will just create a backup that can be restored with |
Hi folks, Just adding a +1 on this issue. I was attempting to do a per-user install of v4.6.0 on 64-bit (Windows) - "Microsoft Windows 7 Professional 6.1.7601 Service Pack 1 Build 7601" via msiexec /I node-v4.6.0-x64.msi ALLUSERS=2 MSIINSTALLPERUSER=1 I encountered the same issue. As commented above, unchecking performance counters resolves the problem. (Initially found the fix via #6647 and the comment by https://github.com/joaocgreis .) |
So for those of us installing node automatically, not manually/interactively - any suggestions on how to deal with this issue in a fully automated install? Is there a command-line argument along the lines of ALLUSERS=2 & co? |
I was facing same issue on windows7 64 bit machine.This is my installing log.I try to many ways and still didn't fix the issue.Please help me lookup and fix this issue. Thanks @Compynerd255 @gamtiq @andybakerbrfc @joaocgreis |
@shenmiweiyi I just get the same issue (windows7 64bit). |
@spike0xff You can try:
|
I ran into this too, with node-v6.10.0-x64.msi on Windows 7, and fixed it by disabling performance counter during install. |
I tried teh below and it has worked for me. I was having the same trouble with my Node.JS installer . It is not issue that the installer has just need to change some settings. I did the below steps. 1 - Clean TEMP Folder |
@joaocgreis Thanks you advice from comment #4329 (comment) helps me Nodejs 6.10.3 issue present. |
Nodejs 8.9.4 and nothing changed and nobody cares |
@NTMan i see, the problem was saved on my pc using Windows 7 64 bit. And i followed same steps as mentioned |
I had the same problem in Windows 10 Pro X64, I disabled my Avast for 10 minutes, and did full install, and worked! |
@macario1983 THANK YOU. This was driving me nuts. Such a simple fix too. |
@macario1983 thanks a lot. I have almost gone crazy with this bug |
Disabling Avast helped me too on Windows 10 x64 |
Worked when disabling Avast. Avast is driving me nuts with all sorts of problems. Deleting from all my machines for sure. |
Wow I was battling this for 3 hours, it all worked with disabling Avast... can't believe it was that simple. Thanks guys. |
Pfffffff Thank you guys !! I can't believe it too .. |
Thank You @macario1983 I was trying to install v8.11.2 with the Windows 64 bit MSI. |
Disabling avast worked for me! |
Disable avast worked for me !! |
After ensuring that the previous node was completely removed, I renamed the following key |
Disable avg worked for me on Windows 10 x64 !! |
I sent to Avast one e-mail to tell the false positive, or the problem, I hope that stop, and other users can do the same with their anti virus |
Disabling avast worked for me..!! :-) Thanks |
Disabling AVG worked for me, on |
Windows 7 x64, Node-v8.12.0-x64: Disabled antivirus, but that did not help. |
I had this issue with version 10.13.0. Installing without performance counters did not work for me but installing without Event tracing (ETW) did. |
For anybody that comes here using Chocolatey on Windows 7... The GUI installer clarifies:
Chocolatey eats this error, upgrade fails with error 1603, generic MSI error. Don't try to fix it scouring the web for hours, like I did. |
I get an error when I insall node.js on "Windows 10 pro" 64-bit.
I get "node.js Setup Wizard ended prematurely..."
I even tried to install different versions. These are :
node-v5.2.0-x64.msi
node-v4.2.3-x64.msi
node-v0.12.7-x64.msi
NTVS 1.1 VS 2015.msi
Attached is installation log file.
Nodejs.txt
The text was updated successfully, but these errors were encountered: