Can't install vagrant

344 views
Skip to first unread message

msharp

unread,
Feb 4, 2016, 6:22:20 PM2/4/16
to Vagrant

I keep getting the following error when trying to install Vagrant - "Error writing to file: C:\HashiCorp\Vagrant\Embedded\bin\file.exe.  Verify that you have access to that directory"


I definitely have access to the directory, I'm not sure what's going on, but retry doesn't work so all I can do is 'Cancel' which reverts the installation.  There doesn't seem to be any documentation anywhere on what I should do to fix this.


I'm running Windows 7, 64-bit.  I've tried to install vagrant 1.7.4, 1.8.0, and 1.8.1 all with the same message.



Wil Taylor

unread,
Feb 4, 2016, 6:30:33 PM2/4/16
to Vagrant
Few things I would check are as follows:

* Do you have admin rights to the system?
* Can you try opening a powershell console as admin and use the following command to start the installer:
  msiexec.exe /i "c:\downloads\vagrant_1.8.1.msi"

Replace the path to where you have the msi file.



--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/9033a74d-1cc5-4dce-89e7-bd1334118e0c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

John Egan

unread,
Feb 5, 2016, 11:08:05 AM2/5/16
to Vagrant
I've been trying to fix the very same problem for months, with no luck. I tried the suggestion above using Powershell, but no luck. I'm trying to get this to work at my office, where we have mostly Windows 7 enterprise edition computers connected to a Windows domain. I'm one of the few Mac users, so no problems for me, but I'm trying to help my colleagues get Vagrant running, with little success. I've tried this now on 5 different computers, all with the same result.

msharp

unread,
Feb 5, 2016, 5:15:26 PM2/5/16
to Vagrant
admin rights - check, check, check, check, check
powershell, didn't work! X_X

John sounds like your colleagues are in the exact same boat as me.


On Thursday, February 4, 2016 at 4:30:33 PM UTC-7, Wil T wrote:

John Egan

unread,
Feb 5, 2016, 6:08:29 PM2/5/16
to Vagrant
Are you also on a network, connected to a Windows domain? Also, I'm curious about "file.exe". Is that a legit file for Vagrant? Seems like a generic name to me...

I ran into a similar problem installing Git for Windows. That installer also got stuck on a "file.exe" which was also in a /bin/ directory. As with Vagrant, I tried installing to different directories, running the installer as Admin, and checking deep into the directory permissions. Out of desperation, I chose the option to continue with the Git installation, skipping over that file. Either I got lucky, or that file was a phantom error, because I haven't yet run into a problem with Git or Git Bash. 

At this point, I suspect some sort of problem with a Windows domain security policy, and something to do with writing to a directory with "/bin" in the path name. I know that others have this same problem, there's an earlier thread. 

Hopefully, someone can help us sort this out...

msharp

unread,
Feb 22, 2016, 6:16:28 PM2/22/16
to Vagrant
I hadn't heard back on this.  But remembered this issue when installing Cygwin as I also got an error for the file.exe.  During the install there was an option to continue, and I haven't had issues.  I also installed Git and got the same error, but there again, I was able to hit continue and installed without an issue.

It feels like this is a complex issue with an easy solution.  Vagrant should just allow the user to continue the install.

John Egan

unread,
Feb 22, 2016, 6:32:14 PM2/22/16
to Vagrant
Agreed. I had the same problem installing Git, but was able to continue, with no sign of any problems so far... At this point, it's worth a try, even though our dev team is starting to migrate to Macs due to issues like this...

msharp

unread,
Feb 23, 2016, 12:29:08 PM2/23/16
to Vagrant
Unfortunately, there's no budget to do such a thing here.  Isn't the purpose of using Vagrant to be more cross platform friendly?  Doesn't make much sense to have to switch to a Mac just to download Vagrant.

Chad Thompson

unread,
Feb 23, 2016, 4:14:19 PM2/23/16
to Vagrant
I would certainly check with your Windows admin teams - the problems I've usually encountered with things like this is due to various Windows / domain, etc. permissions for installing software.

(Can you change the location of Vagrant, perhaps, to a 'local' directory - like a user directory, etc. rather than the C:\ drive directly?)

John Egan

unread,
Feb 23, 2016, 6:03:51 PM2/23/16
to vagra...@googlegroups.com
Hi - I actually tried a variety of install locations, same results unfortunately

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/WK1zGE9FoVI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/1e47b2f9-6b51-443e-be92-cad79f5e73a9%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages