What version did you install, and where did you download it from?
Have you checked Windows' event log to see if any error messages were reported?
Thank you for responding, I don't see any logs in Windows event, this is the latest version I am trying to install.
I am also having trouble installing the latest CLI version, appears to be a firewall issue. Is there any other workaround to complete the installation ?
This is the error I get while installing the CLI version -
npm ERR! shasum check failed for C:\Users........\Temp\npm-4972
npm ERR! Expected: df7c3ed5a277c3f9d4b5d819b05311d10a200ae6
npm ERR! Actual: d3899450b3278013205a57b0de898b93766dc81f
npm ERR! From: http://registry.npmjs.org/npm/-/npm-2.15.12.tgz
Thanks in advance!
Its possibly the corporate firewall, but that shouldn't be an uncommon situation.
I have tried the https:// url , that complains of ca certificate issues.
Please suggest any workarounds if you can think of.
If you're getting certificate issues with the official registry link, I suspect either a proxy, OR something is injecting its own certificate (essentially acting as a MITM). I think you're going to have problems as long as that's going on.
Do you have any alternate network connection you can try? Are you allowed to take your computer home and try from your own network? (Guessing not, but some places do...)
If you navigate to https://registry.npmjs.org in your browser, what certificates are present? Here's what Safari reports to me:
This is what I see -
registry.npmjs.org uses an invalid security certificate.
No wonder https does not work.
I tried adding security certificate to config but I get shasum exception while installing , pointing to https://registry.npmjs.org.
No much to go on with the logs, is there a way to enable more detailed login?
Thanks in advance!
If you're getting a hashing exception, my guess is that something is being injected into the downloaded files, causing the actual hash to not match the expected hash.
As for debugging that... you might try using "curl" or "wget" to see what is actually being returned or work with your network folks to see what's going on.