Is this installed correctly?

[atif089]

• Platform : Windows 7 x64

My shell is stuck here for several minutes and I don't see any CPU / Hard Disk activity either.

[felixrieseberg]

It seems like the Python installer never came back to tell you what happened - would you mind taking a peek at %USERPROFILE%\.windows-build-tools\ to see if there are any log files?

[linonetwo]

python-log.txt is empty

[zaggino]

Same issue here, using latest Node 6.9.1 LTS 64-bit on Windows Server 2008 R2

[guaycuru]

This is also happening to me, but with build tools:

Waiting for installers... \Successfully installed Python 2.7
Waiting for installers... \

[wayrex]

+1

[jarod1sun]

same as above, my OS is Windows 10, shell stuck at :
Waiting for installers... \Successfully installed Python 2.7
Waiting for installers... \

[djbreen7]

+1

[alexpaluzzi]

Also having this problem. Don't see anything in logs.

[chypriote]

I was having this problem too, and understood once I manually ran the Visual Build Tools installer: the installer downloads a bunch of files before starting installation.
If you are stuck at

Waiting for installers... \Successfully installed Python 2.7
Waiting for installers... \

you just have to wait (took me ~15mn) for all files to be downloaded, and the installation will resume.

[gunjandatta]

I'm also seeing the same. Using the LTS 6.9.4. It's stuck at:

Waiting for installers... |Successfully installed Python 2.7
Waiting for installers... \

I've let this sit for about 1.5 hours. WIFI shows no activity, so it's not downloading files.

[wayrex]

Greetings, JIC someone is having the same issue, I've fixed removing the installed Python in my machine (yeah, I've had it installed), removing it from Windows PATH, running a cleaner like CCleaner and trying to run the installer again...

[miy4mori]

try this

npm --add-python-to-path='true' --debug install --global windows-build-tools

Edit:
The above is wrong.The real reason is that it will call Microsoft's installer in the background to download and install, please be patient.

[sparcut]

Fix for this anyone?

Edit:
Nevermind, @miy4mori ended up finishing 10 seconds after making this comment...

[nickspacek]

@miy4mori Fixed it for me as well on Windows 7.

[jossiwolf]

Thanks @miy4mori, it worked!

For others coming here from Google, make sure to uninstall Python and removing it from PATH before running this.

[neotan]

Thanks for @miy4mori 's inspiration!

My env.:

• Win10 64bit
• Node.js v6.10.3

I got success after ~2 hours try and error, by taking these working approaches:

1. Remove %USERPROFILE%\.windows-build-tools\
2. Run npm --add-python-to-path='true' --debug install --global windows-build-tools with Administrator access CMD

[jim1399]

Thanks @neotan ,, tried your method on (Win 10 64b + Nodejs 8) & it worked 💯

[craigbrett17]

I followed @miy4mori's tip but inspite of giving more more info, it didn't directly help.

What I had to do is like @jossiwolf said, uninstall Python (all versions of it), run the command, and now it has worked. But I seem to have no Python installed, in spite of the command supposing to add Python to the path (I work in one of those least-execution policy type environments, so it could've just added it to the admin user's path).

I can't see Python in my installed programs though. So I'm wondering if I now need to install Python proper again.

[jossiwolf]

@craigbrett17 There should be a Python 2.7 installation in %USERPROFILE%\.windows-build-tools\python27.

If you want to have Python 3 again, you'll have to reinstall it.

[craigbrett17]

@jossiwolf: Python 2.7 is all good for me. Problem is, it's installed it to my admin account's user profile, set the path variables for the admin user only and all the build tools are in that individual admin account's users dir. So I pretty much will have to run every npm install as admin. Which is just a bit of a pain. That and Python2 is now out of the way hidden from Windows proper, my normal shell sessions and is locked to the admin's user. I'm using Python normally as well as for these tools.

I did choco install python2 again to and redress the balance and re-get Python 2 properly on my machine. However, I still can't build properly now, probably because the build tools are on the admin user's profile. I might lift them from there and start borrowing path variables from the admin and put them on the system instead.

[craigbrett17]

Resolved this by moving the GYP_MSVS_VERSION variable up to a system environment variable and then copying the bit of the path that points at the nodejs gyp bin into the system path variable as well.

So in total, if installing under LUA:

1. Uninstall Python (if any versions are on your system)
2. Run npm --add-python-to-path='true' --debug install --global windows-build-tools with Administrator access CMD
3. Reinstall Python version(s)
4. Promote GYP_MSVS_VERSION from admin user's env variables to system env variables.
5. In the admin user's path, there should be a path similar to: "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin". Copy this to the system path.

Things at least seem to install correctly now. Will continue testing to see if this has solved it for me.

[siimkkoger]

It can take some time - it took me like 15 minutes to suddenly complete.

[pfuri]

When it says "please be patient" it means it, took me about 5 minutes of waiting on fios:

Launched installers, now waiting for them to finish.
This will likely take some time - please be patient!
Waiting for installers... |Successfully installed Python 2.7
Waiting for installers... -Successfully installed Visual Studio Build Tools.
+ windows-build-tools@1.3.2
added 126 packages in 296.338s

[briancodes]

@pfuri It was hanging on the second "Waiting for installers" for 10+ minutes for me. I risked closing PowerShell and re-running the command - worked in a few seconds after that

[JPtenBerge]

I'm running into something that hasn't been posted here yet. When I run npm install --global windows-build-tools --debug, this appears in my console:

Starting installation...
  windows-build-tools Installer: Launching installer in C:\Users\me\.windows-build-tools with file BuildTools_Full.exe +0ms
Launched installers, now waiting for them to finish.
This will likely take some time - please be patient!
  windows-build-tools Tail: Waiting for log file to appear in C:\Users\me\.windows-build-tools\build-tools-log.txt +0ms
  windows-build-tools Tail: Waiting for log file to appear in C:\Users\me\.windows-build-tools\python-log.txt +1ms
  windows-build-tools Tail: waitForFile: Found C:\Users\me\.windows-build-tools\build-tools-log.txt +0ms
  windows-build-tools Tail: Tailing C:\Users\me\.windows-build-tools\build-tools-log.txt +0ms
  windows-build-tools Tail: waitForFile: Found C:\Users\me\.windows-build-tools\python-log.txt +0ms
  windows-build-tools Tail: Tailing C:\Users\me\.windows-build-tools\python-log.txt +0ms
  windows-build-tools Installer: Stdout from launch-installer.ps1: T h i s   i n s t a l l a t i o n   p a c k a g e   c o u l d   n o t    b e   o p e n e d .     V e r i f y   t h a t   t h e   p a c k a g e   e x i s t s   a n d   t h a t   y o u   c a n   a c c e s s   i t ,   o r   c o n t a c t   t h e   a p p l i c a t i o n   v e n d o r   t o   v e r i f y   t h a t   t h i s   i s   a   v a l i d   W i n d o w s   I n s t a l l e r   p a c k a g e .
  +466mss-build-tools
Waiting for installers... /  windows-build-tools Tail: Stopping success +1m
  windows-build-tools build tools tailer exited +0ms
Successfully installed Visual Studio Build Tools.
  windows-build-tools Installer: Successfully installed Visual Studio Build Tools according to tailer +1ms
Waiting for installers... /

"This installation package could not be opened." I went to %userdir%\windows-build-tools and tried executing the python installer by hand - worked just fine. But this doesn't help move the installer forward, it's still stuck at waiting for installers.

Help would be greatly appreciated. I'm on Windows 10 with the latest Node.js, v9.5.0. I ran the command with Administrator privileges.

[MattOndo]

I am in the same spot as @JPtenBerge right now, just sitting there!

[bkrebs]

Like @MattOndo , I tried the previous recommendations and was still receiving the same error as @JPtenBerge. While the npm install was still 'Waiting for installers...', I opened another Administrative command window and ran the following:

cd %USERPROFILE%\.windows-build-tools

msiexec /n /lvx+! python-log.txt /i python-2.7.14.amd64.msi /quiet

The python-log.txt file began to grow and the npm install completed within a few minutes.

[MattOndo]

KUDOS to @bkrebs! That solution worked!

[JPtenBerge]

One of the overnight commits is awesome, because the installation runs smoothly for me as well now. Praise all around!

[sumit6b]

@craigbrett17 solution worked for me after i put VisualStudioVersion=15.4 system level environment variable.

[realworld666]

I get the following hang. Been like this for 20 minutes

Starting installation...
  windows-build-tools Installer: Launching installer in C:\Users\davec\.windows-build-tools with parameters -ExecutionPolicy,Bypass,-NoProfile,-NoLogo,& {& 'C:\Users\davec\AppData\Roaming\npm\node_modules\windows-build-tools\ps1\launch-installer.ps1' -BuildToolsInstallerPath 'C:\Users\davec\.windows-build-tools' -InstallBuildTools -ExtraBuildToolsParameters '' -PythonInstaller 'python-2.7.14.amd64.msi' -InstallPython -VisualStudioVersion '2015' }. +0ms
  windows-build-tools Installer: Stdout from launch-installer.ps1: Passed arguments:
  windows-build-tools  +272ms
Launched installers, now waiting for them to finish.
This will likely take some time - please be patient!

Status from the installers:
  windows-build-tools Tail: Waiting for log file to appear in C:\Users\davec\.windows-build-tools\build-tools-log.txt +0ms
  windows-build-tools Tail: Waiting for log file to appear in C:\Users\davec\.windows-build-tools\python-log.txt +1ms
  windows-build-tools Tail: waitForFile: still waiting +1ms
  windows-build-tools Tail: waitForFile: Found C:\Users\davec\.windows-build-tools\python-log.txt +0ms
  windows-build-tools Tail: Tailing C:\Users\davec\.windows-build-tools\python-log.txt +1ms
---------- Visual Studio Build Tools ----------
Still waiting for installer log file...
------------------- Python --------------------
---------- Visual Studio Build Tools ----------
[034C:0DC4][2018-06-07T21:36:00]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{a9528995-e130-4501-ae19-bbfaddb779cc}, resume: ARP, restart initiated: No, disable resume: No
[1B94:14EC][2018-06-07T21:36:00]i399: Apply complete, result: 0x0, restart: None, ba requested restart:  No
---------- Visual Studio Build Tools ----------
[034C:0DC4][2018-06-07T21:36:00]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{a9528995-e130-4501-ae19-bbfaddb779cc}, resume: ARP, restart initiated: No, disable resume: No
[1B94:14EC][2018-06-07T21:36:00]i399: Apply complete, result: 0x0, restart: None, ba requested restart:  No

------------------- Python --------------------
Successfully installed Python 2.7

[nigilan]

This is being discussed in #116

[mfalfafa]

thanks @neotan , it works for me

[raknarrok]

I had a similar issue, the problem was solved checking the Python version, in the system was added by default the Python37, after remove Python37 i reboot my pc and then installed the version Python27. I executed again the cmd and the error was solved.

[Ahmdrza]

just uninstall python, and re-run the command.