Hi, I'm not sure if there is a vagrant64 in the list of packages.
I'm not able to get this to install using the Vagrant website installer or Chocolatey, and was hoping to find a common thread causing both installation processes to fail. On Friday, September 18, 2015 at 11:19:38 AM UTC-6, dragon788 wrote: > > It seems like chocolatey isn't pulling the right arch then. Is there a > vagrant64 in the list of packages? > > On Fri, Sep 18, 2015, 9:45 AM John Egan <[email protected] <javascript:>> > wrote: > >> Hi - I tried a reboot, but no success. Also, I'm running 64-bit Windows 7 >> Enterprise. >> >> >> On Friday, September 18, 2015 at 6:44:05 AM UTC-6, dragon788 wrote: >> >>> It appears it was installing 32 bit, are you on a 64 bit workstation? It >>> also appears the "failure" was that it couldn't run with the reboot >>> suppression of the MSI framework. If you reboot is vagrant installed? >>> >>> On Thu, Sep 17, 2015, 5:31 PM John Egan <[email protected]> wrote: >>> >> I decided to try a different approach and use Chocolatey >>>> <https://chocolatey.org/> to try an install. it errored out, and I've >>>> included the command prompt output (chocolatey-screen-error.txt) and the >>>> log file in the hope this will provide more detail about the cause of the >>>> issue. >>>> >>>> I'm attempting to install Vagrant (1.7.4) on Windows 7 Enterprise, SP1 >>>> (workstation on a corporate Windows domain). >>>> >>>> I hope this extra information proves helpful. thanks! >>>> >>>> >>>> On Thursday, September 17, 2015 at 2:09:43 PM UTC-6, John Egan wrote: >>>>> >>>>> Hi Alvaro - I'm not that familiar with the command prompt in Windows; >>>>> how can I check the HOME of the user? Also, how can I check to see what >>>>> Virtualbox expects? >>>>> >>>>> On Monday, September 7, 2015 at 2:29:15 AM UTC-6, Alvaro Miranda >>>>> Aguilera wrote: >>>>>> >>>>>> Check the HOME and of the user. >>>>>> >>>>>> time by time, Virtualbox, and the command line get different HOMES, >>>>>> so >>>>>> that cause problems. >>>>>> >>>>>> Alvaro >>>>>> >>>>>> On Sat, Sep 5, 2015 at 3:27 AM, John Egan <[email protected]> wrote: >>>>>> > I'm also having these exact same symptoms. I'm also on a domain, >>>>>> with a >>>>>> > local admin account and am not using roaming profiles. A coworker >>>>>> of mine is >>>>>> > also experiencing the same problems. >>>>>> > >>>>>> > On Wednesday, August 5, 2015 at 2:54:59 AM UTC-6, Leynos wrote: >>>>>> >> >>>>>> >> Hi, >>>>>> >> >>>>>> >> 1. Yes, this is joined to a domain >>>>>> >> 2. This is with a local admin account >>>>>> >> 3. Roaming profiles aren't being used. >>>>>> >> >>>>>> >> Thanks, >>>>>> >> >>>>>> >> Leynos >>>>>> >> >>>>>> >> On Tuesday, 4 August 2015 17:27:12 UTC+1, dragon788 wrote: >>>>>> >>> >>>>>> >>> Everyone who is having issues, these questions might help narrow >>>>>> things >>>>>> >>> down: >>>>>> >>> 1. Are you joined to a domain? >>>>>> >>> 2. Do you log in as a domain user or local Administrator? >>>>>> >>> 3. Do you happen to know if IT is using Roaming profiles for your >>>>>> domain >>>>>> >>> if you have one? >>>>>> >>> >>>>>> >>> On Sunday, August 2, 2015 at 4:04:42 PM UTC-5, Leynos wrote: >>>>>> >>>> >>>>>> >>>> Hi, >>>>>> >>>> >>>>>> >>>> I am seeing this error too when trying to install. I have tried >>>>>> several >>>>>> >>>> different locations. >>>>>> >>>> >>>>>> >>>> The error is as in the following screenshot: >>>>>> >>>> >>>>>> >>>> https://imgur.com/wsH2Ie5 >>>>>> >>>> >>>>>> >>>> Note that when I try creating a file at the same location after >>>>>> >>>> restarting, whilst using a the administrator account, I receive >>>>>> the >>>>>> >>>> following error (in Powershell): >>>>>> >>>> >>>>>> >>>> Access to the path 'C:\Vagrant\embedded\bin\file.exe' is >>>>>> denied. >>>>>> >>>> >>>>>> >>>> Regards, >>>>>> >>>> >>>>>> >>>> Leynos >>>>>> >>>> >>>>>> >>>> On Monday, 27 July 2015 08:07:15 UTC+1, Tuan Minh Nguyen Hoang >>>>>> wrote: >>>>>> >>>>> >>>>>> >>>>> I also have the same issue. Have you been able to overcome it? >>>>>> :( >>>>>> >>>>> >>>>>> >>>>> On Thursday, June 25, 2015 at 4:22:01 PM UTC+8, Jos Rozen >>>>>> wrote: >>>>>> >>>>>> >>>>>> >>>>>> Alas, I'm still having the same issue. When trying to install >>>>>> from >>>>>> >>>>>> vagrant_1.7.2.msi (downloaded, several times, from >>>>>> vagrantup.com), the >>>>>> >>>>>> installer stops and displays "Error writing to file: >>>>>> >>>>>> C:\HashiCorp\Vagrant\embedded\bin\file.exe. Verify that you >>>>>> have access to >>>>>> >>>>>> that directory." --I do have access to that directory as there >>>>>> are already >>>>>> >>>>>> files in there (from that same install). >>>>>> >>>>>> This is a Windows 7 Enterprise, SP1, 64 bits machine, >>>>>> localized to >>>>>> >>>>>> French / France. >>>>>> >>>>>> thks >>>>>> >>>>>> Jos >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Le jeudi 25 juin 2015 01:04:47 UTC+2, [email protected] a >>>>>> écrit : >>>>>> >>>>>>> >>>>>> >>>>>>> Hi Jos, >>>>>> >>>>>>> >>>>>> >>>>>>> Managed to install? If not can you describe more about the >>>>>> problem? >>>>>> >>>>>>> Any error displayed on the screen or the installer just >>>>>> disappears? >>>>>> >>>>>>> An you try repair(right click on msi and repair) and check? >>>>>> >>>>>>> I am using it on a Windows 7 , 64bit laptop installation had >>>>>> no >>>>>> >>>>>>> issues. >>>>>> >>>>>>> Locale of the system? >>>>>> >>>>>>> >>>>>> >>>>>>> -Suneel >>>>>> >>>>>>> >>>>>> >>>>>>> On Wednesday, June 10, 2015 at 5:03:29 PM UTC+5:30, Jos Rozen >>>>>> wrote: >>>>>> >>>>>>>> >>>>>> >>>>>>>> Hey, >>>>>> >>>>>>>> When installing Vagrant (1.7.2) on my Windows 7 64 bits >>>>>> laptop, it >>>>>> >>>>>>>> errors trying to write file >>>>>> "C:\Vagrant\embedded\bin\file.exe". >>>>>> >>>>>>>> I do have administrator rights on my machine. I tried : >>>>>> >>>>>>>> - simply double-clicking on the msi or launching it from the >>>>>> command >>>>>> >>>>>>>> prompt running as an administrator, >>>>>> >>>>>>>> - rebooting my laptop first, >>>>>> >>>>>>>> - a few locations for Vagrant. >>>>>> >>>>>>>> The installer can write files into that directory (as there >>>>>> are many >>>>>> >>>>>>>> already) but not this file.exe. >>>>>> >>>>>>>> Any ideas ? >>>>>> >>>>>>>> thks >>>>>> >>>>>>>> Jos >>>>>> >>>>>>>> >>>>>> > >>>>>> > -- >>>>>> > 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 [email protected]. >>>>>> > To view this discussion on the web visit >>>>>> > >>>>>> https://groups.google.com/d/msgid/vagrant-up/c9f58c2e-02c8-4113-9657-d16e0f7090b3%40googlegroups.com. >>>>>> >>>>>> >>>>>> > For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> -- >>>> 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/4zGGCMQ7Wxk/unsubscribe. >>>> >>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>> >>> >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/vagrant-up/b5aaa209-4839-4a92-8ab4-c7b57fa64968%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/vagrant-up/b5aaa209-4839-4a92-8ab4-c7b57fa64968%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >> 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/4zGGCMQ7Wxk/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/3dee7f9e-f41c-4bbc-bc35-eeab0a8d19df%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/3dee7f9e-f41c-4bbc-bc35-eeab0a8d19df%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/0c09a558-20a3-43e0-b310-44e8a8e48f86%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
