npm install error - MSB3428: Could not load the Visual C++ component "VCBuild.exe"

Asked 9/2, 2014 at 12:6 Answered 15/7, 2022 at 15:18

283

I'm trying to use the

npm install steam

but I am getting an error saying

I'm not sure how to fix this and I have gotten this on two different npm module installs. I can install other modules however.

What I have tried: Install whatever dependencies it needs. (ursa, node-gyp etc) Install Visual C++ 2005. Install Visual C++ 2010. Change the enviroment variable path to /VC/ (found on another StackOverflow thread/question. Googled, googled & googled.

I also get an error trying do:

npm install ursa

The error is:

Chaotic answered 9/2, 2014 at 12:6 Comment(5)

Did you install it with the x64 compiler as well? The error message is hinting about ursaNative.vcxproj wanting to build for x64 but that it is an invalid platform. – Felisha 9/2, 2014 at 12:33

@Karl-JohanSjögren, When I tried install an x64 bit version of Visual C++ 2010 I get: Please resolve the following: A newer version of Microsoft Visual C++ 2010 Redistributable has been detected on the machine. – Chaotic 9/2, 2014 at 13:5

Don't know anything about that error I'm afraid. But the initial problem I would think is because you don't have the x64 compiler installed. – Felisha 9/2, 2014 at 13:9

I solved this problem !!! please use the stable version of Node – Meaning 30/8, 2017 at 7:13

Why should I not upload images of code/data/errors? – Wrack 18/4, 2023 at 0:55

679

Try this from cmd line as Administrator

optional part, if you need to use a proxy:

set HTTP_PROXY=http://login:password@your-proxy-host:your-proxy-port
set HTTPS_PROXY=http://login:password@your-proxy-host:your-proxy-port

run this:

npm install -g --production windows-build-tools

No need for Visual Studio. This has what you need.

References:

https://www.npmjs.com/package/windows-build-tools
https://github.com/felixrieseberg/windows-build-tools

Touchwood answered 30/8, 2016 at 19:48 Comment(28)

Worked for me when installing sleep – Patriliny 20/9, 2016 at 16:12

Worked for me in Windows 8.1 64bit. Thanks. – Mirk 20/11, 2016 at 18:57

Worked for me on Windows 10 64bit. Thank you!! :) – Alcine 8/12, 2016 at 8:6

worked for me as well on Windows 10 64bit, the other above did not, thanks ! – Hematite 15/12, 2016 at 16:5

Only this solution seems to work on Windows 10 64 bit. Thanks! – Demo 13/6, 2017 at 10:54

This indeed worked in a W10 x64 environment. Thanks a lot :) – Nerval 26/6, 2017 at 12:2

I'm trying this as I too am running into this issue on Win 10 64 bit. But it hangs for me when it says "Waiting for Installers..." or at least it never seems to complete. I'll keep waiting. – Spleen 5/7, 2017 at 10:18

I was so sick of getting tons of errors every time I'm trying to build something under windows. This command solved all my problems! Thank you Matt very much – Wristband 14/7, 2017 at 17:46

@Wristband I was sick of it too. – Touchwood 17/7, 2017 at 15:51

Yarn user shoud try: yarn global add windows-build-tools with Administrator rights! – Dolorous 24/8, 2017 at 19:14

This doesn't install anything. This opens Visual Studio pop up window with options Modify, Unistall and Repair. So what? Where is the medicine to the issue? – Bounce 22/10, 2017 at 2:57

Microsoft Visual C++ 2015 Redistributable (x86) - 14.0.24210 : Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.

– Bounce 22/10, 2017 at 3:0

This attempts to install Python 2.7.13 although I had 2.7.14 already installed. – Shirley 15/11, 2017 at 13:6

Works on windows 10 build 15063. Thank you ! – Hypothecate 4/12, 2017 at 10:45

This command took more than 30 minute to complete on my i7 laptop. – Watkin 7/2, 2018 at 9:45

worth a note that you needed to restart powershell after this install – Lesalesak 6/3, 2018 at 19:29

You should run this command on Power shell as Administrator... ;) – Pulley 16/3, 2018 at 20:28

On Windows 7 it lasts half an hour and adds a 3GB+ dependency. I almost ran out of space. This was for font-manager mind you which cheerfully claims 1 dependency, nan. Maybe solution <1GB? – Italianize 14/4, 2018 at 18:41

Worked for me for node gyp error while installing StrongLoop on Windows 10 x64 – Refrigerator 6/5, 2018 at 9:21

Thanks a lot! This saved me A LOT of time! Works on Windows 7 x64 – Clubhouse 8/5, 2018 at 11:31

I found that this doesn't work because node-gyp forces version v140 and the installer above puts down the latest version (currently VS2017 which is v150). I had to add --vs2015 to the install line to get it to put down the right version. I figured this out from a variety of sources, but in particular npk48's comments really helped. This is the command that worked for me: npm install --global --production windows-build-tools --vs2015 After this I was successful at installing better-sqlite3 where I wasn't before. – Finnougric 27/9, 2018 at 3:37

got Error : It looks like you're installing or modifying anoth er product right now. and hags until stop manually. Successfully installed Python 2.7. i'm on win7 ultimate – Tellurian 6/10, 2018 at 11:27

Thanks for this answer. Worked on W7 64 bits – Thrash 6/12, 2018 at 22:51

@Finnougric adding the --vs2015 at the end did the trick for me. The only solution that worked after trying nearly everything else on this page. – Augusto 24/7, 2019 at 13:28

I had to manually run C:\Users\%username%\.windows-build-tools\vs_BuildTools.exe and update Visual Studio Build Tools 2017. – Pricillaprick 18/12, 2019 at 11:55

If command above stuck with message: "Successfully installed Python 2.7" pls run these commands: npm install --global --production [email protected] then npm install --global --production windows-build-tools – Isogamete 25/3, 2020 at 11:22

Worked for me too. Windows 10 x64.... It would take a while to install though.. – Mn 19/5, 2020 at 1:2

WARNING: the download could be pretty large in size (gave up after 250MB was sucked from my quota); if you just need to get the npm module installed, it may be more beneficial to just find and install a precompiled copy of the the required binary (usually the installer script would already try this, as in case of node-sass etc., before falling back to native compilation and giving this error). – Stipe 22/1, 2021 at 2:16

I know it's a very old question, but is the first in my google search and after some time I got how to solve this.

find node on your windows with:
as @janaka-bandara suggested you can use the native
where node
if you don't have it for some reason you can install which with node
$ npm install -g which
$ which node
after cd into the directory, inside the directory cd into node_modules\npm folder and finally:
$ npm install node-gyp@latest
here worked, the answer is from this site

Inequality answered 2/3, 2015 at 20:55 Comment(10)

how about npm install -g node-gyp@latest – Watchword 22/5, 2015 at 8:33

windows stuff, if you are running unix-based so is okay, but since npm is installed on "Program Files" folder on windows thing become a bit harder, I think. (old answer, can't reproduce this now to be sure) – Inequality 22/5, 2015 at 19:47

didn't help me :-( – Michelle 9/4, 2016 at 8:38

Hi Edu, i followed the same steps and it still shows the error while running npm install, I am using windows 8.1 – Cymar 25/4, 2016 at 12:55

@ShubhamTiwari every command you do succeeded or you received some errors? – Inequality 25/4, 2016 at 19:11

when i fired npm install node-gyp@latest it worked . But after that when i fired - npm install heapdump it gives same error – Lopez 22/11, 2016 at 7:37

You don't need which when you already have where (at least in W10+) – Stipe 22/1, 2021 at 2:19

@JanakaBandara where command is native on windows 10+? – Inequality 23/1, 2021 at 2:49

@EduRuiz seems so; Windows Server 2003 and later (i.e. anything after Windows XP 32 bit) provide the where.exe program. – Stipe 26/1, 2021 at 9:28

the last step did it for me, installing node-gyp – Kastroprauxel 3/1, 2022 at 15:3

It's mentioned in the Documentation clearly as below: https://github.com/nodejs/node-gyp#installation

Option 1: Install all the required tools and configurations using Microsoft's windows-build-tools using npm install --global --production windows-build-tools from an elevated PowerShell or CMD.exe (run as Administrator).

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

Pickpocket answered 10/4, 2017 at 12:22 Comment(2)

As mentioned in some other comments this installation takes quite long but it works – Cullie 27/3, 2019 at 6:31

as someone mentioned in another comment, adding --vs2015 on the end of this command is worth trying if it doesn't work by itself. It was the only solution on this thread that worked for me: npm install --global --production windows-build-tools --vs2015 – Augusto 24/7, 2019 at 13:53

Look at the installation instructions for node-gyp - you can't just npm install node-gyp. I see you've installed Visual C++, but there's more to it.

What version of windows do you have? If I knew that I might be able to tell you which part of the node-gyp instructions you didn't do, but check them out and you should be able to figure it out. I've gone through a bit of pain for this stuff too.

Marcellus answered 31/5, 2014 at 23:2 Comment(2)

Hello, I checked there and I installed the required things but it's still not working. (sorry for a super-late reply!) – Chaotic 27/9, 2014 at 18:2

If I were you, I'd re-do the installation steps as written. There may be some intricacy that makes simply having the components installed insufficient. But I don't know anything about ursa if its an ursa specific issue. – Marcellus 29/9, 2014 at 4:24

I tried the above suggested npm install --global --production windows-build-tools but found that the installation was always hanging forever.

I managed to fix the problem by installing Node.js 8 instead of Node.js 10.

Habitant answered 6/6, 2018 at 7:29 Comment(1)

INstallation has taken 90minutes for me so perhaps it was still doing something on your pc – Halves 20/12, 2018 at 9:14

Just to add to the above answer, anyone finding an issue of the installers taking forever, I found my issue was python, I uninstalled both my versions 3 and versions 2.

The re-ran the command in PowerShell terminal as the admin and it installed almost straight away.

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

Purplish answered 4/2, 2018 at 15:49 Comment(1)

I second this. Uninstalling Python 2.7 fixes this issue with the windows-build-tools. – Kaylor 24/5, 2018 at 19:39

PLEASE FOLLOW THE FLOW CORRECTLY WINDOWS 10x64

Powershell run as administrator
npm install -g node-gyp
npm install --global --production windows-build-tools

Caiaphas answered 28/4, 2019 at 3:57 Comment(0)

For me worked install the component "VCBuild.exe", just dowload the wizard, install and them open the cmd again as administrator and try run again. Updated link to dowload the wizard here

Dundee answered 5/7, 2019 at 18:37 Comment(2)

Didn't try this actually, but seems like the most straightforward and to-the-point solution! – Stipe 22/1, 2021 at 3:15

Worked for me. Just install Microsoft Build Tools 2015 from the link. – Misguidance 23/8, 2021 at 19:15

Faced this issue while trying to install a VueJs project. The solution that worked for me was to replace the deprecated package "node-sass" with "sass".

Replaced

"node-sass": "^4.5.3",

with

 "sass": "",

Lockage answered 15/7, 2022 at 15:18 Comment(0)

Tried npm install mongoose --msvs_version=2012, if you have multiple Visual installed, it worked for me

Selenodont answered 31/3, 2015 at 16:32 Comment(1)

bear in mind that this will help you only if you have Visual studio 2012 installed – Disapprobation 26/5, 2015 at 12:1

The problems here are to do with the npm node-gyp module

I found the solutions offered on the build page for that project effective.

node-gyp page on github

There's a fully automatic way and a manual way.

Fowlkes answered 23/2, 2017 at 0:54 Comment(2)

Thanks! This worked for me. On Windows 10, after the automatic installation, I had to manually run npm config set msvs_version 2015 and then npm config set python %USERPROFILE%\.windows-build-tools\python27\python.exe. After that I was able to build sleep – Torrez 7/6, 2017 at 12:33

Microsoft Visual C++ 2015 Redistributable (x86) - 14.0.24210 : Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.

– Bounce 22/10, 2017 at 3:1

As Matt said (https://mcmap.net/q/107704/-npm-install-error-msb3428-could-not-load-the-visual-c-component-quot-vcbuild-exe-quot) you should install the build-tools for windows. However, I did it via cmd and got an error, although I am the administrator -

Please restart this script from an administrative PowerShell!
The build tools cannot be installed without administrative rights.
To fix, right-click on PowerShell and run "as Administrator".

I got the same error via a PowerShell.

For windows 7, the administrative PowerShell can be found under:

Control Panel -> System and Security -> Administrative Tools -> Windows PowerShell Modules

Soutor answered 1/10, 2017 at 21:17 Comment(0)

I tried running the following commands but the PowerShell instance ends up hanging/freezing:

npm install -g node-gyp
npm install --global --production windows-build-tools

Therefore, instead of running the app on Windows I transferred over the application to a Ubuntu VM instance and was able to run npm install with no issues.

So if none of the above solutions work and if you don't mind working in a Linux environment, then try creating a Linux VM and porting over your codebase onto it. Then run npm install and see if it works.

Aurea answered 25/4, 2022 at 1:42 Comment(0)

I managed to get it working by following Option 2 on the Windows installation instructions on the following page: https://github.com/nodejs/node-gyp.

I had to close the current command line interface and reopen it after doing the installation on another one logged in as Administrator.

Chromoprotein answered 15/12, 2018 at 9:37 Comment(0)

For those the above answer does not work, here is another possible solution to look at.

Issue: On installing npm os-service package i was getting below error error MSB4019: The imported project "d:\M icrosoft.Cpp.Default.props" was not found. Confirm that the path in the declaration is correct

Even the installation of build tools or VS 2015 did not work for me. So I tried installing below directly via PowerShell (as admin)

https://chocolatey.org/packages/visualcpp-build-tools/14.0.25420.1 Command: choco install visualcpp-build-tools --version 14.0.25420.1

Once this was installed, set an environment variable VCTargetsPath=C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\v140

Then installation of the package worked perfectly fine after these.

Role answered 30/5, 2019 at 1:55 Comment(0)

i know this is old, i actually just had the same issue. i was able to solve it by running npm install -g node-gyp and fixed! npm

Brilliant answered 27/9, 2019 at 11:42 Comment(0)

-1

npm install --global windows-build-tools

just run this command via powershell (right click and run as administrator!)

worked for me..

Despite answered 4/2, 2019 at 14:46 Comment(0)

-5

1)install "lite server" and then try below command :
npm run lite

Oak answered 6/11, 2016 at 15:19 Comment(0)

Hot tags

Godot Unity Godot Help Programming Godot 4.X GUI GDScript 3D 2D Physics CSharp Godot 3.X VR XR Projects C++

Recommended topics

Hot tags