Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows installer does not include MSVCP100.dll so curl does not work and so breaks vagrant #6764

ChristopherHackett opened this issue Dec 29, 2015 · 24 comments


Copy link

@ChristopherHackett ChristopherHackett commented Dec 29, 2015


vagrant version : 1.8.1
windows version : 10 Home 64 bit

Just done a clean OS install on my Windows laptop. I installed Windows 10 along with a bunch of other stuff including vagrant. When I came to use vagrant If found box add command failed with this

C:\Users\chris>vagrant box add laravel/homestead
The box 'laravel/homestead' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:

URL: [""]


on investigation I found curl located in C:\HashiCorp\Vagrant\embedded\bin complained of

The program can't start because MSVCP100.dll is missing from your computer. 

The dll is provided by MS Visual C++ 2010 x86 Redistributables - something I had on my old install for another program. Installing it makes vagrant work.

If I was less knowledgeable on this matter I probably would have given up looking for a fix.

If you are installing the Redistributable Package then maybe something is going wrong, If you are not including it for any reason then you should or provide some helpful message to the user they need it.

Copy link

@afiaka87 afiaka87 commented Dec 30, 2015

Thank you so much it took me forever to find this fix. Apparently most of the top google results for that error are just people who typed their vagrant commands incorrectly. This is a pretty annoying bug considering the debugging necessary to solve it. Hopefully a future version could work with a version of curl that doesn't have that dependency, or at least direct you to a download link.

Copy link

@niktsanov niktsanov commented Feb 20, 2016

Thank you very much! I've almost given up trying to fix this, as I've tried a lot of things.

Copy link

@vincekovacs vincekovacs commented Mar 3, 2016

I found this issue on windows 10.

I found out that the MSVCP100.dll exists in C:\Windows\sytem32 directory, but curl did not find it.

Copy link

@jideokus jideokus commented Mar 26, 2016

Thanks. Works like a charm. This was driving me a bit crazy.

Copy link

@StefanScherer StefanScherer commented Mar 26, 2016

I've sent a PR to include the DLL in the Vagrant installer hashicorp/vagrant-installers#78

Copy link

@TuyenGa TuyenGa commented Apr 10, 2016

thanks verymuch

Copy link

@jideokus jideokus commented Apr 10, 2016

Yeah good call.

On Sat, Apr 9, 2016 at 10:21 PM, Vuong Quang Tuyên <


thanks verymuch

You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#6764 (comment)

Babajide J. Okusanya

Copy link

@alnutile alnutile commented Apr 15, 2016

gildegoma added a commit that referenced this issue May 29, 2016

- Add "config" unit tests for `ansible_local` (guest)
- Share some "config" examples between both ansible provisioners
- Move `config_host.rb` specific examples to `config/host.rb`
- Add a requirement to "../helpers" in `config/guest.rb` in order to be
  able to run the related unit tests


- This is the first part of GH-6633 resolution
- This change is a handy prerequisite for GH-6570

Not addressed yet:

- FIXME (guest.rb): Some test-double stubs are currently not working as
  expected, and the related checks are commented out for the moment
  (no idea why, but this is not urgent to be fixed because of GH-7335
  rejection. See also GH-6984)
- FIXME (shared.rb): The guest-based config should actually NOT return
  an error when the extra_vars file cannot be found, but only display a
  a warning (similarly to the changes done for GH-6764, see 4e451c6)
Copy link

@arubacao arubacao commented Jun 8, 2016

There is a even simpler solution for this problem:

  1. Install a working curl.exe executable Download
  2. Make curl available for the whole system (PATH system-variable) short tutorial
  3. Delete or rename the unfunctional curl.exe in C:\HashiCorp\Vagrant\embedded\bin

Therefore you don't have unnecessary stuff installed, but a working curl executable with in my opinion is mandatory anyway :)

Copy link

@StefanScherer StefanScherer commented Jun 11, 2016

There is a PR hashicorp/vagrant-installers#78 to add the DLL to the Vagrant installer. Seems nobody has noticed that.
@sethvargo PTAL ?

Copy link

@amontalban amontalban commented Jun 14, 2016

I can confirm that @StefanScherer PR fixes the issue in 1.8.4 on Windows.

Looking forward to get this pushed to new version, thanks!

Copy link

@StefanScherer StefanScherer commented Jun 15, 2016

hashicorp/vagrant-installers#78 got merged. So next version of Vagrant should have a solution out-of-the-box for that.

@sethvargo sethvargo closed this Jun 15, 2016
Copy link

@hauthorn hauthorn commented Jul 29, 2016

In what version is this included? Running Vagrant 1.8.5 on a fresh Windows 10 Pro install, and I had to manually install the redistributable.

Copy link

@azeredogab azeredogab commented Jul 31, 2016

The solution that our friend @arubacao said it worked for me :)

Copy link

@hauthorn hauthorn commented Jul 31, 2016

@StefanScherer What version is that?

Copy link

@StefanScherer StefanScherer commented Jul 31, 2016

@hauthorn I thought after the PR has been merged the fix would be part of the installer of the next version. I just have checked Vagrant 1.8.5 and the DLL is still missing. So maybe this will be fixed for the next Vagrant installer?

Copy link

@zhudepei zhudepei commented Aug 1, 2016


Copy link

@Its-rahulG Its-rahulG commented Aug 4, 2016

The most easy and simple ans is, just install github client.. and install vagrant 1.7+ and virtual box 5.1+ .... and run command vagrant box add laravel/homestead . That's it. it will work like charm

Copy link

@manuepeva manuepeva commented Sep 26, 2016

Thank You so much!!! this run perfect for me ! I have been working on this bug for a while and I was just about to lose my mind.

Copy link

@wojcikm wojcikm commented Dec 18, 2016

Unfortunately this solution does not work for me. Error stays where it was. Actually Im running out of ideas what do to next. Reinstalled many times everysthing, tried different versions, different shells. What is interesting, Curl itself works (when i type in cmd: curl "" it gives a respond), but still throwing that error of login. Win 10 x64

Copy link

@huguenin huguenin commented Mar 3, 2017

I love you @ChristopherHackett - uninstalling my existing 2010 Redistributable (apparently "a newer version") and installing the one you suggested solved all of my Vagrant problems! Thank you so much :)

Copy link

@samdizon samdizon commented May 28, 2017

Got the same error. still unable to be fixed. Tried all those stuff.

Copy link

@lubosdz lubosdz commented Mar 28, 2019

On windows 10 it might be a permission access issue (C:\Users\x\AppData\Local\Temp) - this helped me:

Running redistributable VC++ DLL shoved up error message "You must fix issue - a newer version of DLL was detected on your system". So the solution was finally directory access permission.

Copy link

@ghost ghost commented Mar 29, 2020

I'm going to lock this issue because it has been closed for 30 days . This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@hashicorp hashicorp locked and limited conversation to collaborators Mar 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet