Is this installed correctly? #33
Comments
It seems like the Python installer never came back to tell you what happened - would you mind taking a peek at |
python-log.txt is empty |
Same issue here, using latest Node 6.9.1 LTS 64-bit on Windows Server 2008 R2 |
This is also happening to me, but with build tools:
|
+1 |
same as above, my OS is Windows 10, shell stuck at : |
+1 |
Also having this problem. Don't see anything in logs. |
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.
you just have to wait (took me ~15mn) for all files to be downloaded, and the installation will resume. |
I'm also seeing the same. Using the LTS 6.9.4. It's stuck at:
I've let this sit for about 1.5 hours. WIFI shows no activity, so it's not downloading files. |
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... |
try this
Edit: |
Fix for this anyone? Edit: |
@miy4mori Fixed it for me as well on Windows 7. |
Thanks @miy4mori, it worked! For others coming here from Google, make sure to uninstall Python and removing it from PATH before running this. |
Thanks for @miy4mori 's inspiration! My env.:
I got success after ~2 hours try and error, by taking these working approaches:
|
Thanks @neotan ,, tried your method on (Win 10 64b + Nodejs 8) & it worked 💯 |
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. |
@craigbrett17 There should be a Python 2.7 installation in If you want to have Python 3 again, you'll have to reinstall it. |
@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 |
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:
Things at least seem to install correctly now. Will continue testing to see if this has solved it for me. |
It can take some time - it took me like 15 minutes to suddenly complete. |
When it says "please be patient" it means it, took me about 5 minutes of waiting on fios:
|
@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 |
I'm running into something that hasn't been posted here yet. When I run
"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. |
I am in the same spot as @JPtenBerge right now, just sitting there! |
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:
The python-log.txt file began to grow and the npm install completed within a few minutes. |
KUDOS to @bkrebs! That solution worked! |
One of the overnight commits is awesome, because the installation runs smoothly for me as well now. Praise all around! |
@craigbrett17 solution worked for me after i put VisualStudioVersion=15.4 system level environment variable. |
I get the following hang. Been like this for 20 minutes
|
This is being discussed in #116 |
thanks @neotan , it works for me |
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. |
just uninstall python, and re-run the command. |
I solve this problem by installing .net 4.6 |
Every time (npm install -g windows-build-tools)the installation process goes up to successfully installed python 2.7 _ |
Here is how I solve my problem: You may also need to uninstall the |
My shell is stuck here for several minutes and I don't see any CPU / Hard Disk activity either.
The text was updated successfully, but these errors were encountered: