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

[jashang87]

I run the "npm install --global --production windows-build-tool" and installation got stuck after "Successfully installed Python 2.7" (almost 2 hours) And no log file for studio build tools in ".windows-build-tools" folder It installed some programs related to Visual Studio (control panel screenshot below) Any idea how to fix this? Thanks

[terebentina]

I am experiencing the same thing. Windows 10 nodejs 10.11.0

[jashang87]

Hi @terebentina , I figured that everything is installed as required (Python and VS 2017) but the CMD script/installer got stuck and can't get the feedback from VS installer. So after installer installed the VS 2017 components (as shown in screenshot in my initial post, will take some time to install everything), I opened the task manager and killed "node.exe" processes (two of those processes were running) and then I closed the CMD window, opened a new CMD window and went to next step (in my case, installed node-gyp) and everything worked fine on second attempt (it didn't work first time, I uninstalled everything and followed the process again as I mentioned above).

[aifodu]

You may want to take a look at this post: https://github.com/felixrieseberg/windows-build-tools/issues/152#issuecomment-432945646

[gian1200]

I faced a similar issue. As a workaround I installed the 4.0.0 version npm install --global --production [email protected] and then run the original one npm install -g --production windows-build-tools, and it completed

[deepakjha14]

I am stuck with the same issue, cant get over "Python 2.7.10 already installed, not installing again" and stays there for the next ice age like a zen monk :( any help will be appreciated, dont know what to do. Tried what @gain1200 had suggested but no luck.

[harmandeep-singh]

I faced a similar issue. As a workaround I installed the 4.0.0 version npm install --global --production [email protected] and then run the original one npm install -g --production windows-build-tools, and it completed

Thank you :) @gian1200

npm install --global --production windows-build-tools

You may see this error below : (Just reboot the system , and run the above in window power shell as admin) 2019-10-02T04:22:16 : Error : It looks like you're installing or modifying another product right now. Please wait until all other operations are finished and try again.

it i

[peraltafederico]

Hi everyone! I found the solution to this problem with this steps:

1. Uninstall Python 2.7
2. Install this version of Python
3. Run npm install --global windows-build-tools

Let me know if it works!

[jonab12]

@peraltafederico Thank you this worked for me!

[bkelley13]

I thought it was stuck too, but it just took about 4 minutes to get past that.

[ryanbottema]

Hi everyone! I found the solution to this problem with this steps:

Uninstall Python 2.7 Install this version of Python Run npm install --global windows-build-tools

This works, but a note to Python3 users; make sure your 'python' path to python2 takes precedence over python3.

[cSarcasme]

ty @peraltafederico for your solution stuck now for one hour and you find the solution thank s a lot

[nowayhaze]

I'm not sure if I have a legit solution. After waiting for 30 minutes and nothing happening, I just killed the application. And ran the install script from the beginning again. This time it said python was already installed and then blew through the rest of installation.

[mcaljamj]

The 5.2.2 package is adding an entry to the users PATH environment variable every time it runs. As was in a CI scenario it was added 10's of time. Once i removed all unnecessary duplicates the package would again install.

[Delay-n-days]

我面临着一个类似的问题。作为一个解决方法，我安装了4.0.0版本，然后运行原来的一个，它完成了npm install --global --production [email protected]``npm install -g --production windows-build-tools

Thanks

[karlhorky]

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

choco install python visualstudio2017-workload-vctools -y
npm config set msvs_version 2017

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

[Crumor]

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

awesome @karlhorky works like charm thankyou very much

[FernandoMontesinos]

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

It worked for me, thank you very much

[Harsh-Khurana]

Should I delete .windows-built-tools folder and uninstall python 2.7 before re-running the commands that are specified as solutions?

[j1mmy-Z]

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

It really works, cost me several hours , thanks so much.

[bodrovdev]

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

THANK YOU!

[fabiovaz]

npm config set msvs_version 2017 saved me

[bhargu-27]

Hi everyone! I found the solution to this problem with this steps:

1. Uninstall Python 2.7
2. Install this version of Python
3. Run npm install --global windows-build-tools

Let me know if it works!

Hello after installing 2.7.17 when I follow step 3 it again installs 2.7.15

[jokereey]

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

choco install python visualstudio2017-workload-vctools -y
npm config set msvs_version 2017

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

It works! thank you man

[amzbiz]

Still hangs, doesn't work for me. Off to Linux.

[karlhorky]

@amzbiz my solution above is an alternative, not a way to make windows-build-tools work.

Once you run those two commands, it has installed the dependencies that windows-build-tools is supposed to install.

[amzbiz]

Yup I tried with both build tools 2017 and 2019 @karlhorky, one installed directly, and one using your Chocolatey recommendation. Unfortunately neither of those fixed my node 12 build issue. Fortunately I was able to replicate and fix my issue on node 10 but still looks likely I'll need to move to WSL as I don't want to keep pushing things uphill, spent a whole day trying different fixes and none of them got node 12 working 😢.

[karlhorky]

Interesting, wonder if the tools are installed properly but Node cannot find them for some reason (a path issue or something). Anyway, good luck!