Skip to content
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

Closed
samarthRT opened this issue Dec 17, 2015 · 47 comments
Closed

node.js Setup Wizard ended prematurely #4329

samarthRT opened this issue Dec 17, 2015 · 47 comments
Labels
install Issues and PRs related to the installers. windows Issues and PRs related to the Windows platform.

Comments

@samarthRT
Copy link

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

@Fishrock123 Fishrock123 added the install Issues and PRs related to the installers. label Dec 17, 2015
@TheHans255
Copy link

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.

@ChALkeR ChALkeR added the windows Issues and PRs related to the Windows platform. label Jan 3, 2016
@Fishrock123
Copy link
Contributor

cc @nodejs/build?

@joaocgreis
Copy link
Member

@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)?

@samarthRT
Copy link
Author

@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.
It would be nice if someone can share the its use, as I'm in learning phase.
In the meantime I also found another issue #524 regarding the same.

@joaocgreis
Copy link
Member

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.

@joaocgreis
Copy link
Member

@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

@samarthRT
Copy link
Author

Hey @Compynerd255, I couldn't locate these keys (GUIDs) on my system registry. Are we sure these are not system specific ?

@joaocgreis
Copy link
Member

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!

@samarthRT
Copy link
Author

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! Windows_NT 10.0.10240
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\firstName lastName\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js"
npm ERR! node v5.9.0
npm ERR! npm v2.7.0
npm ERR! code MODULE_NOT_FOUND

npm ERR! Cannot find module 'glob'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! http://github.com/npm/npm/issues

npm ERR! Please include the following file with any support request:
npm ERR! C:\WINDOWS\system32\npm-debug.log

*npm-debug.log * :
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Users\firstName Lastname\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js' ]
2 info using npm@2.7.0
3 info using node@v5.9.0
4 verbose stack Error: Cannot find module 'glob'
4 verbose stack at Function.Module._resolveFilename (module.js:339:15)
4 verbose stack at Function.Module._load (module.js:290:25)
4 verbose stack at Module.require (module.js:367:17)
4 verbose stack at require (internal/module.js:16:19)
4 verbose stack at Object. (C:\Users\firstName lastName\AppData\Roaming\npm\node_modules\npm\lib\help.js:14:12)
4 verbose stack at Module._compile (module.js:413:34)
4 verbose stack at Object.Module._extensions..js (module.js:422:10)
4 verbose stack at Module.load (module.js:357:32)
4 verbose stack at Function.Module._load (module.js:314:12)
4 verbose stack at Module.require (module.js:367:17)
5 verbose cwd C:\WINDOWS\system32
6 error Windows_NT 10.0.10240
7 error argv "C:\Program Files\nodejs\node.exe" "C:\Users\firstName lastName\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js"
8 error node v5.9.0
9 error npm v2.7.0
10 error code MODULE_NOT_FOUND
11 error Cannot find module 'glob'
12 error If you need help, you may report this error at:
12 error http://github.com/npm/npm/issues
13 verbose exit [ 1, true ]

@ilkercat
Copy link

Hi @joaocgreis,
I think it is the cause since I had the same issue on Win7 x64 when using node-v4.3.2-x64.msi. There was an older version of nodejs on my machine installed before.

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}
ProviderType REG_DWORD 0x0
ApplicationIdentity REG_EXPAND_SZ C:\Program Files\nodejs\node.exe

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib_V2Providers{1e2e15d7-3760-470e-8699-b9db5248edd5}{3a22a8ec-297c-48ac-ab15-33ec93033fd8}
NameResource REG_DWORD 0x1
ExplainResource REG_DWORD 0x3
InstanceType REG_DWORD 0x6
First Counter REG_DWORD 0x2b88
NeutralName REG_SZ Node.js
Last Counter REG_DWORD 0x2b9c
CounterBlock REG_BINARY 010000000004411000000000000000006400000000000000050000000700000001000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF000000000200000000044110000000000000000064
00000000000000090000000B00000001000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF000000000300000000044110000000000000000064000000000000000D0000000F00000001000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FF00000000040000000004411000000000000000006400000000000000110000001300000001000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF000000000500000000000100000000000000000064000000000000001500000017
00000001000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF000000000600000000054110000000000000000064000000FDFFFFFF190000001B00000001000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF0000000007000000000541
10000000000000000064000000FDFFFFFF1D0000001F00000001000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF00000000080000000000010000000000000000006400000000000000210000002300000002000000FFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFF000000000900000000054110000000000000000064000000FDFFFFFF250000002700000001000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF000000000A000000000541100000000000000000640000
00FDFFFFFF290000002B00000001000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF00000000
CounterCount REG_DWORD 0xa

Deleting this entry fixed the issue for me which means that I did not have to unselect the "performance counter".

@joaocgreis
Copy link
Member

@ilkercat thanks!

@samarthRT sorry for the delay, I had missed this one. Your npm is installed under appdata, so can you try:

rmdir /s C:\Users\firstName Lastname\AppData\Roaming\npm
npm install npm

If that doesn't help, perhaps the best way forward would be to ask on IRC or create an issue in npm.

@yogibear54
Copy link

@ilkercat thanks! This worked for me too.

@gamtiq
Copy link

gamtiq commented Jul 3, 2016

I had the same problem with node 5.5.0 and 6.2.2 in Windows 7 64-bit.
I found that there was HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{1e2e15d7-3760-470e-8699-b9db5248edd5} in the register on my computer. After I had deleted this entry, node installation passed fine.
Thanks all!

@MarkPieszak
Copy link

Win7 64-bit as well Node 6.3 install. Won't work without not installing performance counters. Previously it worked when an older version was installed and 6.3 was installed with nvm (node version manager) strangely enough.

@pinin
Copy link

pinin commented Sep 21, 2016

I removed this item, and the installation was okay HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{1e2e15d7-3760-470e-8699-b9db5248edd5}

@DeepakTiwari13
Copy link

I was facing same issue on win7 64 bit sp1 machine.
In msi installer I unchecked performance counter installation , documentation installation.
Then it got installed.
v6.7.0

@joaocgreis
Copy link
Member

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:

LODCTR /S:lodctr_backup_20160901.ini
LODCTR /R

The first command will just create a backup that can be restored with LODCTR /R:lodctr_backup_20160901.ini if anything goes wrong. Please comment here if this doesn't work, and paste the backup file in the comment. Thanks!

@andybakerbrfc
Copy link

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 .)

@spike0xff
Copy link

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?

@shenmiweiyi
Copy link

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
installlog.txt

@mmouterde
Copy link

@shenmiweiyi I just get the same issue (windows7 64bit).
@gamtiq / @pinin solutions worked for me.

@joaocgreis
Copy link
Member

@spike0xff You can try:

msiexec /i node.msi /qn+ ADDLOCAL=ALL REMOVE=NodePerfCtrSupport,NodeEtwSupport

@emackey
Copy link

emackey commented Feb 22, 2017

Issue still persists on node-v6.9.4-x64.msi on Windows 7. Disabling Performance Counter does the trick.

I ran into this too, with node-v6.10.0-x64.msi on Windows 7, and fixed it by disabling performance counter during install.

@danicoolpak17
Copy link

danicoolpak17 commented Mar 27, 2017

I tried teh below and it has worked for me.
@Maktm @shenmiweiyi

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
2 - Disable your antivirus for 10 mins or so.
3 - Then do the below steps.
4 - Go to C:>users>"UserName">AppData>Local>Temp
5 - Right Click on Temp and go to Properties
6 - Select Security Tab
7 - Select the User and check the permission and controll give the user full control by Checking Full Control on permission
8 - Go Ahead and Install Node.js and Enjoy.

@NTMan
Copy link

NTMan commented May 5, 2017

@joaocgreis Thanks you advice from comment #4329 (comment) helps me

Nodejs 6.10.3 issue present.

@NTMan
Copy link

NTMan commented Feb 12, 2018

Nodejs 8.9.4 and nothing changed and nobody cares

@danicoolpak17
Copy link

@NTMan i see, the problem was saved on my pc using Windows 7 64 bit. And i followed same steps as mentioned

@macario1983
Copy link

I had the same problem in Windows 10 Pro X64, I disabled my Avast for 10 minutes, and did full install, and worked!

@davidstackio
Copy link

@macario1983 THANK YOU. This was driving me nuts. Such a simple fix too.

@ryzhovalexandr
Copy link

@macario1983 thanks a lot. I have almost gone crazy with this bug

@vstepanenko
Copy link

Disabling Avast helped me too on Windows 10 x64

@fossegutten
Copy link

Worked when disabling Avast. Avast is driving me nuts with all sorts of problems. Deleting from all my machines for sure.

@rodcunha
Copy link

rodcunha commented Jun 1, 2018

Wow I was battling this for 3 hours, it all worked with disabling Avast... can't believe it was that simple. Thanks guys.

@ingvald31
Copy link

Pfffffff Thank you guys !! I can't believe it too ..

@sebastienguillon
Copy link

Thank You @macario1983
I can confirm that it works (disabling Avast while installing Node.js).

I was trying to install v8.11.2 with the Windows 64 bit MSI.

@Danielsberg
Copy link

Disabling avast worked for me!

@pierrot974
Copy link

Disable avast worked for me !!

@T0T4R4
Copy link

T0T4R4 commented Jun 9, 2018

After ensuring that the previous node was completely removed, I renamed the following key
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib_V2Providers
to
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\old_V2Providers,
then rebooted,
disabled my AV for a while (Trend Micro)
and deleted the %appdata%/npm folder (which took a while)...

@stroop566
Copy link

Disable avg worked for me on Windows 10 x64 !!

@macario1983
Copy link

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

@ranjitsachin
Copy link

Disabling avast worked for me..!! :-) Thanks

@ferchinas
Copy link

Disabling AVG worked for me, on
Windows 10 "64 bits"

@ode2code95
Copy link

ode2code95 commented Sep 24, 2018

Windows 7 x64, Node-v8.12.0-x64: Disabled antivirus, but that did not help.
Disabled Performance counters, ETW, (see 4329 (comment)) and that fixed it! Thanks, but I wonder why this long-running issue continues to be present across 4 major releases?

@MTmace
Copy link

MTmace commented Oct 30, 2018

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.

@akaleeroy
Copy link

For anybody that comes here using Chocolatey on Windows 7... The GUI installer clarifies:

This application is only supported on Windows 8.1, Windows Server 2012 R2, or higher.

This application is only supported on Windows 8.1, Windows Server 2012 R2, or higher.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
install Issues and PRs related to the installers. windows Issues and PRs related to the Windows platform.
Projects
None yet
Development

No branches or pull requests