I have been using my Windows 7 enterprise based Vagrant setup for two weeks now. It uses Vagrant 1.18, Git for Windows, and VirtualBox. I left it running and was happily using the service it provides. Then I tried to use "vagrant ssh" to connect and I got an error. I soon found that no vagrant commands work from Git Bash or CMD. Focusing on CMD I am baffled that I now get a stacktrace whenever I try to run a vagrant command.
I posted the issue to StackOverflow. The callstack is listed there. http://stackoverflow.com/questions/36221690/vagrant-stopped-working-access-denied Can anyone read the Ruby(?) callstack and give me something to go on? My best theory is that my employer changed the configuration of the machine as part of a security update. If the error could just tell me which directory or which file it was trying to access then I'd at least have a lead. Thanks, Scott -- 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/a5326305-2377-487e-8f97-d9870a5777a8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
