node.js Setup Wizard ended prematurely

[samarthRT]

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

[TheHans255]

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.

[Fishrock123]

cc @nodejs/build?

[joaocgreis]

@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]

@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]

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]

@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]

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

[joaocgreis]

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]

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]

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]

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