Could not install Visual Studio Build Tools #152

Villan-98 · 2018-10-22T07:15:19Z

PS C:\Windows\system32> npm install -g windows-build-tools

> [email protected] postinstall C:\Users\sachi\AppData\Roaming\npm\node_modules\windows-build-tools
> node ./dist/index.js



Downloading vs_BuildTools.exe
[>                                            ] 0.0% (0 B/s)
Downloaded vs_BuildTools.exe. Saved to C:\Users\sachi\.windows-build-tools\vs_BuildTools.exe.

Starting installation...
Launched installers, now waiting for them to finish.
This will likely take some time - please be patient!

Status from the installers:
---------- Visual Studio Build Tools ----------
2018-10-20T08:56:31 : Verbose : [InstallerImpl]: Rpc connection was closed.
2018-10-20T08:56:31 : Verbose : [InstallerImpl]: Stream was closed
2018-10-20T08:56:31 : Verbose : [SetupUpdaterImpl]: Rpc connection was closed.
2018-10-20T08:56:31 : Verbose : [SetupUpdaterImpl]: Stream was closed
2018-10-20T08:56:32 : Verbose : Restarting the system after an installation operation.
------------------- Python --------------------
Python 2.7.15 is already installed, not installing again.


Could not install Visual Studio Build Tools.
Please find more details in the log files, which can be found at
C:\Users\sachi\.windows-build-tools

Skipping configuration: No configuration for Python or Visual Studio Build Tools required.
TypeError: Cannot read property 'then' of undefined
    at install_1.install (C:\Users\sachi\AppData\Roaming\npm\node_modules\windows-build-tools\dist\start.js:19:17)
    at launch_1.launchInstaller.then.then.then (C:\Users\sachi\AppData\Roaming\npm\node_modules\windows-build-tools\dist\install\index.js:34:9)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
+ [email protected]
added 143 packages in 39.518s

node version- 8.11
os: windows 10
npm version- 5.6

The text was updated successfully, but these errors were encountered:

pdavis68 · 2018-10-22T17:37:00Z

I'm getting this same issue.

Exlord · 2018-10-24T09:59:45Z

same here
node 8.12
os: windows 10
npm version- 6.4

ridakk · 2018-10-24T11:04:34Z

same here

Skipping configuration: No configuration for Python or Visual Studio Build Tools required.
TypeError: Cannot read property 'then' of undefined
    at install_1.install (D:\Users\kgoktas\AppData\Roaming\nvm\v8.12.0\node_modules\windows-build-tools\dist\start.js:19:17)
    at launch_1.launchInstaller.then.then.then (D:\Users\kgoktas\AppData\Roaming\nvm\v8.12.0\node_modules\windows-build-tools\dist\install\index.js:34:9)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:189:7)
+ [email protected]
added 143 packages from 96 contributors in 11.84s

λ node -v
v8.12.0
λ npm -v
6.4.1

takase1121 · 2018-10-25T07:34:00Z

I also faced this problem.

use 4.0.0 for now. The latest seems to be bugged

awedev · 2018-10-29T20:29:08Z

+1

RossPfeiffer · 2018-11-16T21:10:27Z

Damn

LuKaXiya · 2018-11-28T07:07:35Z

same here
npm -version
6.4.1
windows 10
node -v
v10.13.0

refack · 2018-11-28T15:29:39Z

To those who are looking for an alternative way to get your machine set up, the Node.js project is working with Microsoft on a recipe for installing the required build toolchain (admittedly it's hard to get this one right). ATM we have two fairly decent suggestions:

Install the MS VS2017 Community Edition as described in doc: updating vs cpp build tool installation steps in building nodejs/node#24462 (comment)
(The "Visual C++ build tools" workload + the "Python 2" and "Git for Windows" individual components)

The new install_tools.bat from win: do not use Boxstarter to install tools nodejs/node#24677
Which is just: Install chocolatey, and run choco upgrade python2 visualstudio2017-workload-vctools.
Or in script form:

"%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -InputFormat None -ExecutionPolicy Bypass -Command Start-Process '%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe' -ArgumentList '-NoProfile -InputFormat None -ExecutionPolicy Bypass -Command iex ((New-Object System.Net.WebClient).DownloadString(''https://chocolatey.org/install.ps1'')); choco upgrade -y python2 visualstudio2017-workload-vctools; Read-Host ''Type ENTER to exit'' ' -Verb RunAs

hmmhmmhm · 2018-12-03T17:01:44Z

Just use it simply
It'll be work very smoothly

npm install --global --production [email protected]

LuKaXiya · 2019-01-16T02:35:54Z

Thanks，it's done. just use npm install --global --production [email protected] At 2019-01-14 15:27:45, "bgSosh" <[email protected]> wrote: 3 months - what's going on guys? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

srlowe · 2019-01-16T09:58:14Z

@LuKaXiya Apologies - that was a bit terse, I was having a bad day bad 😩

LuKaXiya · 2019-01-16T10:08:22Z

Someone gave me this solution, you can give it a try. To those who are looking for an alternative way to get your machine set up, the Node.js project is working with Microsoft on a recipe for installing the required build toolchain (admittedly it's hard to get this one right). ATM we have two fairly decent suggestions: Install the MS VS2017 Community Edition as described in nodejs/node#24462 (comment) (The "Visual C++ build tools" workload + the "Python 2" and "Git for Windows" individual components) The new install_tools.bat from nodejs/node#24677 Which is just: Install chocolatey, and run choco upgrade python2 visualstudio2017-workload-vctools. Or in script form: "%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -InputFormat None -ExecutionPolicy Bypass -Command Start-Process '%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe' -ArgumentList '-NoProfile -InputFormat None -ExecutionPolicy Bypass -Command iex ((New-Object System.Net.WebClient).DownloadString(''https://chocolatey.org/install.ps1'')); choco upgrade -y python2 visualstudio2017-workload-vctools; Read-Host ''Type ENTER to exit'' ' -Verb RunAs 在 2019-01-16 17:58:17，"bgSosh" <[email protected]> 写道： @LuKaXiya Apologies - that was a bit terse, I was having a bad day bad 😩 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

chris-envas · 2019-04-17T03:20:13Z

me too, how to deal with it

alexdevero · 2019-04-26T10:52:14Z

I am also experiencing this issue with v5.1.0. Installation hangs and never finishes. Installing v4.0.0 worked.

mithundas79 · 2019-04-29T20:27:17Z

Just use it simply
It'll be work very smoothly
npm install --global --production [email protected]

the savior

giegiey · 2019-05-02T09:02:01Z

Just use it simply
It'll be work very smoothly
npm install --global --production [email protected]

Thanks bro.

fer626 · 2019-05-07T14:39:04Z

Just use it simply
It'll be work very smoothly
npm install --global --production [email protected]

thanks work very well

samrueby · 2019-05-16T17:06:37Z

👍 Also stuck on this.

dcarter0317 · 2019-06-06T16:12:14Z

Thank you so much, npm install --global --production [email protected]
did the trick.

ulsting · 2019-06-11T23:15:03Z

I tried npm install --global --production [email protected] and got:

[email protected] postinstall C:\Users\Grant\AppData\Roaming\npm\node_
modules\windows-build-tools
node ./dist/index.js
build-tools-log.txt

Downloading python-2.7.14.amd64.msi
[> ] 0.0% (0 B/s)
Downloaded python-2.7.14.amd64.msi. Saved to C:\Users\Grant.windows-build-tools
\python-2.7.14.amd64.msi.
Downloading BuildTools_Full.exe
[> ] 0.0% (0 B/s)
Downloaded BuildTools_Full.exe. Saved to C:\Users\Grant.windows-build-tools\Bui
ldTools_Full.exe.

Starting installation...
Launched installers, now waiting for them to finish.
This will likely take some time - please be patient!

Status from the installers:
---------- Visual Studio Build Tools ----------
Successfully installed Visual Studio Build Tools.
---------- Visual Studio Build Tools ----------
Successfully installed Visual Studio Build Tools.
------------------- Python --------------------
Successfully installed Python 2.7

Could not install Visual Studio Build Tools.
Please find more details in the log files, which can be found at
C:\Users\Grant.windows-build-tools

Now configuring the Visual Studio Build Tools and Python...

All done!

[email protected]
removed 1 package and updated 5 packages in 45.157s

hamadgondal · 2019-06-19T13:59:56Z

Just use it simply
It'll be work very smoothly
npm install --global --production [email protected]

Thank you ... Works perfectly

connor4312 · 2019-07-08T21:13:40Z

This should be fixed with #183, however that's not been published to npm yet.

oshihirii · 2019-07-14T08:06:02Z

same issue:

Windows 10
Node v10.16.0
npm 6.9.0  
[email protected]

Rabindramanohar · 2019-07-24T13:18:35Z

Thank you, npm install --global --production [email protected] is worked for me.

satishdabilpur · 2019-08-06T12:28:53Z

I am using below NPM versions

Npm - 6.9.0
Node - 10.16.0

While installing below command, still seeing Could not install Visual Studio Build Tools. issue. How to resolve this?

npm install -g --production [email protected]

And from the build-logs, I found below exception

MUX: Exception: Info: Could not download update data.

sudha53633 · 2019-08-30T11:11:25Z

Facing same error with node 10.16.3LTS, windows 7.

Have tried with npm install --global --production [email protected], but not worked.

Kindly do the needful

satishdabilpur · 2019-08-30T11:30:56Z

I am using below NPM versions

Npm - 6.9.0
Node - 10.16.0

While installing below command, still seeing Could not install Visual Studio Build Tools. issue. How to resolve this?

npm install -g --production [email protected]

And from the build-logs, I found below exception

MUX: Exception: Info: Could not download update data.

I had VS2015 and VS2017 installed. So once VS2015 is uninstalled, it worked perfectly.

dinukasal · 2019-09-03T04:31:21Z

All of these solutions didn't work for me, installation gets stuck.
I installed windows build tools manually after downloading & installing the windows 10 sdk iso from here,
https://developer.microsoft.com/en-US/windows/downloads/windows-10-sdk

takase1121 · 2019-09-03T05:37:45Z

Not to badmouth this package or anything, but maybe try using WSL. Node.js natives on windows is already hard despite this package made it much easier.

MHICoder15 · 2019-09-11T13:03:20Z

PS C:\Windows\system32> npm install -g windows-build-tools
[email protected]

[email protected] postinstall C:\Users\M_H_I\AppData\Roaming\npm\node_modules\windows-build-tools
node ./dist/index.js

Downloading python-2.7.15.amd64.msi
[> ] 0.0% (0 B/s)
Downloaded python-2.7.15.amd64.msi. Saved to C:\Users\M_H_I.windows-build-tools\python-2.7.15.amd64.msi.
Downloading vs_BuildTools.exe
[> ] 0.0% (0 B/s)
Downloaded vs_BuildTools.exe. Saved to C:\Users\M_H_I.windows-build-tools\vs_BuildTools.exe.

Starting installation...
Launched installers, now waiting for them to finish.
This will likely take some time - please be patient!

Status from the installers:
---------- Visual Studio Build Tools ----------
Still waiting for installer log file...
------------------- Python --------------------
Successfully installed Python 2.7

Anyone can tell me What's solution is this problem "Still waiting for installer log file..."..???

jgod · 2019-10-17T11:07:01Z

PS C:\Windows\system32> npm install -g windows-build-tools
[email protected]

[email protected] postinstall C:\Users\M_H_I\AppData\Roaming\npm\node_modules\windows-build-tools
node ./dist/index.js

Downloading python-2.7.15.amd64.msi
[> ] 0.0% (0 B/s)
Downloaded python-2.7.15.amd64.msi. Saved to C:\Users\M_H_I.windows-build-tools\python-2.7.15.amd64.msi.
Downloading vs_BuildTools.exe
[> ] 0.0% (0 B/s)
Downloaded vs_BuildTools.exe. Saved to C:\Users\M_H_I.windows-build-tools\vs_BuildTools.exe.

Starting installation...
Launched installers, now waiting for them to finish.
This will likely take some time - please be patient!

Status from the installers:
---------- Visual Studio Build Tools ----------
Still waiting for installer log file...
------------------- Python --------------------
Successfully installed Python 2.7

Anyone can tell me What's solution is this problem "Still waiting for installer log file..."..???

Any progress?

TheColorRed · 2019-12-20T20:47:28Z

I was able to fix my install by doing these three things (Not sure which action(s) fixed the issue):

Remove C:\Users\<user>\.windows-build-tools
Uninstall Build Tools from Windows Installed Programs
Uninstall Python 3.x and use Python 2.7

Then all I needed to do was: npm i -g windows-build-tools

ihormkl · 2020-02-17T10:27:22Z

Uninstall Python 3.x and use Python 2.7

This one was the case (Python 3.7 installed from the Microsoft Store).
Thank you.

RGKrish183 · 2020-03-16T09:26:08Z

npm -v = 6.14
node -v = 10.15.3
os = windows 7 sp1

npm i -g --production windows-build-tools

npm install --global --production [email protected]

still gettting error, could

D:\gulaqWorkspace\api\node_modules\iconv>if not defined npm_config_node_gyp (nod
e "C:\Users\Admin\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycl
e\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (no
de "C:\Users\Admin\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bi
n\node-gyp.js" rebuild )
gyp ERR! find VS
gyp ERR! find VS msvs_version was set from command line or npm config
gyp ERR! find VS - looking for Visual Studio version 2015
gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt
gyp ERR! find VS could not use PowerShell to find Visual Studio 2017 or newer
gyp ERR! find VS looking for Visual Studio 2015
gyp ERR! find VS - not found
gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8
gyp ERR! find VS
gyp ERR! find VS valid versions for msvs_version:

PaulRBerg · 2020-08-01T08:36:37Z

Uninstall Python 3.x and use Python 2.7

So what if we need both Python 3.x and Python 2.x?

takase1121 · 2020-08-01T08:48:24Z

Uninstall Python 3.x and use Python 2.7

So what if we need both Python 3.x and Python 2.x?

I think what you can do is actually :

Uninstall python 2.*
Install python 3.* and the Python launcher (py)
Install python 2.* again
Use py -3 to use python 3.* and py -2 for python 2.*.

Nimplex · 2020-11-29T11:16:03Z

Same issue

justinjdickow · 2021-01-22T14:25:38Z

New to windows so this took a while... Here's what I did to get this working. Including node-gyp and electron rebuild in here as well just in case people are landing here to build native libraries for Electron in windows

Install latest LTS node for windows from https://nodejs.org/en/download/
Go to Add or Remove programs and uninstall any existing visual studio build tools
Open Powershell as Admin
Verify node version is latest node --version
Upgrade npm version npm install -g npm
Remove existing installations of windows build tools and node-gyp npm uninstall -g windows-build-tools node-gyp yarn
Go to C:\Users\username and remove existing .windows-build-tools and .node-gyp folders
Make sure electron builder is in your dev dependencies
Add "postinstall": "electron-builder install-app-deps" to your package.json scripts object

Install things

npm install --global --production windows-build-tools
npm install --global node-gyp
setx PYTHON $env:USERPROFILE\.windows-build-tools\python27\python.exe
npm config set python $env:USERPROFILE\.windows-build-tools\python27\python.exe
npm install --global yarn
yarn // native deps will be built properly after this step

olavomello · 2021-02-19T13:37:35Z

Same here

CodingMikey · 2021-03-16T20:24:02Z

I tried npm install --global --production [email protected] but it wasn't working for me I would get error msg "Could not install Visual Studio Build Tools"

I deleted my python using Add or Remove programs on windows. I then deleted .windows-build-tools folder. After running npm install --global --production [email protected] and restarting my computer I got it to work.

thanks @hmmhmmhm

TecnicsSelva · 2021-03-22T10:09:39Z

I was able to fix my install by doing these three things (Not sure which action(s) fixed the issue):

Remove C:\Users\<user>\.windows-build-tools

Uninstall Build Tools from Windows Installed Programs

Uninstall Python 3.x and use Python 2.7

Then all I needed to do was: npm i -g windows-build-tools

Really it is working

karlhorky · 2021-04-22T14:57:41Z

Another option is to try installing the build tools via Chocolatey instead (use an Administrator command line):

choco install python visualcpp-build-tools -y
npm config set msvs_version 2017

Maybe this should be documented in the readme as an alternative...

c42-arun · 2021-05-03T17:29:50Z

Another option is to try installing the build tools via Chocolatey instead (use an Administrator command line):
choco install python visualcpp-build-tools -y
npm config set msvs_version 2017
Maybe this should be documented in the readme as an alternative...

^^ @karlhorky - that worked for me, you're a star!

aamirtestable · 2021-05-12T08:37:05Z

Another option is to try installing the build tools via Chocolatey instead (use an Administrator command line):
choco install python visualcpp-build-tools -y
npm config set msvs_version 2017
Maybe this should be documented in the readme as an alternative...
^^ @karlhorky - that worked for me, you're a star!

My CI/CD have npm install --global --production [email protected] and your solution just worked with that

Thank you

amzbiz · 2021-08-13T23:45:33Z

None of these solutions work for me, Windows 10, Node 12. I'm off to Linux as I can't wait for this to be resolved.

tommasosansone91 mentioned this issue Jan 31, 2019

Can't install term3 in Atom Floobits/atom-term3#103

Open

aifodu mentioned this issue Feb 13, 2019

Installation Hangs after "Successfully installed Python 2.7" and no log file for visual studio build tools #172

Open

sunnymui mentioned this issue Feb 26, 2019

[Windows] Can't install and run the app without errors on Windows codeforsanjose/disaster-response-sj#43

Closed

dr3x mentioned this issue Apr 17, 2019

win10 ver17763.316 Could not install Visual Studio Build Tools. #175

Closed

wrahool mentioned this issue Jun 20, 2019

Unable to pull NPM dependencies while installing empirica on Windows empiricaly/empiricaly.github.io#8

Closed

oshihirii mentioned this issue Jul 14, 2019

MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe". nodejs/node-gyp#307

Closed

timkonieczny mentioned this issue Aug 5, 2019

Windows 10: Error: A dynamic link library (DLL) initialization routine failed. exokitxr/exokit#1356

Closed

jacobq mentioned this issue Aug 25, 2020

Register new version #223

Open

axc450 mentioned this issue May 6, 2021

Windows Build Tools failing to install #253

Open

theenoahmason mentioned this issue Jun 9, 2021

Windows Build Tools install fails dreamsicle-io/wp-theme-assets#19

Closed

Could not install Visual Studio Build Tools #152

Could not install Visual Studio Build Tools #152

Comments

Villan-98 commented Oct 22, 2018

pdavis68 commented Oct 22, 2018

Exlord commented Oct 24, 2018 • edited Loading

ridakk commented Oct 24, 2018

takase1121 commented Oct 25, 2018

awedev commented Oct 29, 2018

RossPfeiffer commented Nov 16, 2018

LuKaXiya commented Nov 28, 2018

refack commented Nov 28, 2018

hmmhmmhm commented Dec 3, 2018 • edited Loading

LuKaXiya commented Jan 16, 2019 via email

srlowe commented Jan 16, 2019

LuKaXiya commented Jan 16, 2019 via email

chris-envas commented Apr 17, 2019

alexdevero commented Apr 26, 2019

mithundas79 commented Apr 29, 2019

giegiey commented May 2, 2019

fer626 commented May 7, 2019

samrueby commented May 16, 2019

dcarter0317 commented Jun 6, 2019

ulsting commented Jun 11, 2019

hamadgondal commented Jun 19, 2019

connor4312 commented Jul 8, 2019

oshihirii commented Jul 14, 2019

Rabindramanohar commented Jul 24, 2019

satishdabilpur commented Aug 6, 2019 • edited Loading

sudha53633 commented Aug 30, 2019

satishdabilpur commented Aug 30, 2019 • edited Loading

dinukasal commented Sep 3, 2019

takase1121 commented Sep 3, 2019

MHICoder15 commented Sep 11, 2019

jgod commented Oct 17, 2019

TheColorRed commented Dec 20, 2019 • edited Loading

ihormkl commented Feb 17, 2020

RGKrish183 commented Mar 16, 2020

PaulRBerg commented Aug 1, 2020

takase1121 commented Aug 1, 2020

Nimplex commented Nov 29, 2020

justinjdickow commented Jan 22, 2021

olavomello commented Feb 19, 2021

CodingMikey commented Mar 16, 2021

TecnicsSelva commented Mar 22, 2021

karlhorky commented Apr 22, 2021

c42-arun commented May 3, 2021

aamirtestable commented May 12, 2021

amzbiz commented Aug 13, 2021

Exlord commented Oct 24, 2018 •

edited

Loading

hmmhmmhm commented Dec 3, 2018 •

edited

Loading

satishdabilpur commented Aug 6, 2019 •

edited

Loading

satishdabilpur commented Aug 30, 2019 •

edited

Loading

TheColorRed commented Dec 20, 2019 •

edited

Loading