running npm install -g meteor gives this error
Error: Response status was 403
at ClientRequest. (C:\Users\username\AppData\Roaming\npm\node_modules\meteor\node_modules\node-downloader-helper\dist\index.js:1:7153)
at Object.onceWrapper (events.js:422:26)
at ClientRequest.emit (events.js:315:20)
at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:641:27)
at HTTPParser.parserOnHeadersComplete (_http_common.js:126:17)
at TLSSocket.socketOnData (_http_client.js:509:22)
at TLSSocket.emit (events.js:315:20)
at addChunk (_stream_readable.js:309:12)
at readableAddChunk (_stream_readable.js:284:9)
at TLSSocket.Readable.push (_stream_readable.js:223:10)
Emitted ‘error’ event on b instance at:
at ClientRequest. (C:\Users\Jefferson\AppData\Roaming\npm\node_modules\meteor\node_modules\node-downloader-helper\dist\index.js:1:7284)
at Object.onceWrapper (events.js:422:26)
[… lines matching original stack trace …]
at TLSSocket.Readable.push (_stream_readable.js:223:10) {
status: 403,
bo
I also get an identical issue, again for npm install -g meteor.
Trying to run this on Windows 10. Have tried in powershell/cmd prompt and as administrator.
Have also tried https://install.meteor.com/windows using the installer (Some other forum posts suggested as a fix, however no success).
Would appreciate any assistance 
@filipenevola is probably the best to answer this.
Actually I think it was @zodern that made the new Windows installer.
@storyteller I just figured Filipe might know if there were any issues with download servers.
In either case the fastest way is to reach out to these people on community Slack.
We’ve done some tests and it’s working.
Maybe you are behind a proxy or firewall?