Windows-build-tools: Could not install Visual Studio Build Tools

Created on 22 Oct 2018  ·  44Comments  ·  Source: felixrieseberg/windows-build-tools 
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

picture Villan-98
👍39

Most helpful comment

Just use it simply
It'll be work very smoothly

npm install --global --production [email protected]
picture hmmhmmhm on 3 Dec 2018
👍191 🚀28 ❤28 🎉28 👀16 👎15 😕11 😄10

All 44 comments

I'm getting this same issue.

pdavis68 picture pdavis68 on 22 Oct 2018

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

Exlord picture Exlord on 24 Oct 2018

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
ridakk picture ridakk on 24 Oct 2018

I also faced this problem.

use 4.0.0 for now. The latest seems to be bugged

takase1121 picture takase1121 on 25 Oct 2018
👍29 🎉13 ❤7 🚀1

+1

awedev picture awedev on 29 Oct 2018
👎19 👍1

Damn

Econymous picture Econymous on 16 Nov 2018
👎17 😄5 👍1

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

LuKaXiya picture LuKaXiya on 28 Nov 2018

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:

  1. Install the MS VS2017 Community Edition as described in https://github.com/nodejs/node/pull/24462#discussion_r234450133
    (The "Visual C++ build tools" workload + the "Python 2" and "Git for Windows" individual components)
  2. The new install_tools.bat from https://github.com/nodejs/node/pull/24677
    Which is just: Install chocolatey, and run choco upgrade python2 visualstudio2017-workload-vctools.
    Or in script form:
    cmd "%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
refack picture refack on 28 Nov 2018
👍1

Just use it simply
It'll be work very smoothly

npm install --global --production [email protected]
hmmhmmhm picture hmmhmmhm on 3 Dec 2018
👍191 🚀28 ❤28 🎉28 👀16 👎15 😕11 😄10

Thanks，it's done. just use
npm install --global --production [email protected]

At 2019-01-14 15:27:45, "bgSosh" notifications@github.com 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.

LuKaXiya picture LuKaXiya on 16 Jan 2019

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

srlowe picture srlowe on 16 Jan 2019

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" notifications@github.com 写道：

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

LuKaXiya picture LuKaXiya on 16 Jan 2019
👍1

me too, how to deal with it

chris-envas picture chris-envas on 17 Apr 2019

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

alexdevero picture alexdevero on 26 Apr 2019

Just use it simply
It'll be work very smoothly

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

the savior

mithundas79 picture mithundas79 on 29 Apr 2019
👍6 ❤2

Just use it simply
It'll be work very smoothly

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

Thanks bro.

giegiey picture giegiey on 2 May 2019
👍6 ❤3

Just use it simply
It'll be work very smoothly

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

thanks work very well

fer626 picture fer626 on 7 May 2019
👍6

👍 Also stuck on this.

samrueby picture samrueby on 16 May 2019

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

dcarter0317 picture dcarter0317 on 6 Jun 2019

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

[email protected] postinstall C:\Users\Grant\AppData\Roaming\npm\node_
moduleswindows-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!

ulsting picture ulsting on 12 Jun 2019
👍14 😄1

Just use it simply
It'll be work very smoothly

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

Thank you ... Works perfectly

hamadgondal picture hamadgondal on 19 Jun 2019

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

connor4312 picture connor4312 on 8 Jul 2019
👍1

same issue:

Windows 10
Node v10.16.0
npm 6.9.0  
[email protected]
oshihirii picture oshihirii on 14 Jul 2019
👍2

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

Rabindramanohar picture Rabindramanohar on 24 Jul 2019

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]

image

And from the build-logs, I found below exception

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

image

satishdabilpur picture satishdabilpur on 6 Aug 2019
👍5

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

sudha53633 picture sudha53633 on 30 Aug 2019
👍4

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]

image

And from the build-logs, I found below exception

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

image

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

satishdabilpur picture satishdabilpur on 30 Aug 2019

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

dinukasal picture dinukasal on 3 Sep 2019
👍2

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.

takase1121 picture takase1121 on 3 Sep 2019

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

[email protected] postinstall C:\Users\M_H_I\AppData\Roaming\npm\node_moduleswindows-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..."..???

MHICoder15 picture MHICoder15 on 11 Sep 2019
👍2

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

[email protected] postinstall C:\Users\M_H_I\AppData\Roaming\npm\node_moduleswindows-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?

jgod picture jgod on 17 Oct 2019
👍1

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

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

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

TheColorRed picture TheColorRed on 20 Dec 2019
👍14 🎉1
  1. Uninstall Python 3.x and use Python 2.7

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

ihormkl picture ihormkl on 17 Feb 2020

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:
RGKrish183 picture RGKrish183 on 16 Mar 2020

Uninstall Python 3.x and use Python 2.7

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

paulrberg picture paulrberg on 1 Aug 2020

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 :

  1. Uninstall python 2.*
  2. Install python 3.* and the Python launcher (py)
  3. Install python 2.* again
  4. Use py -3 to use python 3.* and py -2 for python 2.*.
takase1121 picture takase1121 on 1 Aug 2020
👍2

Same issue
image

Nimplex picture Nimplex on 29 Nov 2020

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

  1. Install latest LTS node for windows from https://nodejs.org/en/download/
  2. Go to Add or Remove programs and uninstall any existing visual studio build tools
  3. Open Powershell as Admin
  4. Verify node version is latest node --version
  5. Upgrade npm version npm install -g npm
  6. Remove existing installations of windows build tools and node-gyp npm uninstall -g windows-build-tools node-gyp yarn
  7. Go to C:\Usersusername and remove existing .windows-build-tools and .node-gyp folders
  8. Make sure electron builder is in your dev dependencies
  9. 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
justinjdickow picture justinjdickow on 22 Jan 2021

Same here

olavomello picture olavomello on 19 Feb 2021

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

CodingMikey picture CodingMikey on 16 Mar 2021

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

  1. Remove C:\Users\<user>\.windows-build-tools
  2. Uninstall Build Tools from Windows Installed Programs
  3. 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

TecnicsSelva picture TecnicsSelva on 22 Mar 2021

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 picture karlhorky on 22 Apr 2021
❤2 👍2

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!

c42-arun picture c42-arun on 3 May 2021
🎉2

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

aamirtestable picture aamirtestable on 12 May 2021
👍2 🚀1
Was this page helpful?
0 / 5 - 0 ratings

Related issues

d3x0r picture d3x0r  ·  6Comments
Infinitay picture Infinitay  ·  6Comments
Bailfire picture Bailfire  ·  10Comments
raymondhani picture raymondhani  ·  5Comments
kittaakos picture kittaakos  ·  8Comments