After installing on 3 different corporate Windows 8/10 boxes, I found a fix for me. 'vagrant up' always fails, but 'vagrant up --provider virtualbox' works. I couldn't see anything meaningful in the debug output with/without the switch, but it solve my problem. YMMV.
Best, Kenneth On Friday, January 12, 2018 at 10:59:23 AM UTC-7, Chris Buck wrote: > > I am looking to have my team at work start using Vagrant to spin up lab > environments for testing certain tools. To that end a DevOps (Mac) > colleague of mine wrote a vagrant configuration for me. Vagrant spins up > the two machines on his Mac, Windows fails. > My tech: > Windows 10 Anniversary Update > PowerShell 5 > Vagrant 2.0.1 > Virtualbox 5.2.2 > Git 2.15.1.2 > The etools Vagrant etc. were all installed using "Run as Administrator". > > Whether I attempt to execute *vagrant up* as admin or using normal > permissions in CMD, vagrant reports: > > C:/HashiCorp/Vagrant/embedded/gems/gems/childprocess-0.6.3/lib/childprocess/windows/handle.rb:12:in > > `open': Access is denied. (5) (ChildProcess::Error) > from > C:/HashiCorp/Vagrant/embedded/gems/gems/childprocess-0.6.3/lib/childprocess/windows/process.rb:71:in > > `launch_process' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/childprocess-0.6.3/lib/childprocess/abstract_process.rb:82:in > > `start' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/subprocess.rb:141:in > > `block in execute' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/safe_chdir.rb:26:in > > `block (2 levels) in safe_chdir' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/safe_chdir.rb:25:in > > `chdir' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/safe_chdir.rb:25:in > > `block in safe_chdir' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/safe_chdir.rb:24:in > > `synchronize' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/safe_chdir.rb:24:in > > `safe_chdir' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/subprocess.rb:140:in > > `execute' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/subprocess.rb:22:in > > `execute' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/powershell.rb:81:in > > `version' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/powershell.rb:95:in > > `validate_install!' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/powershell.rb:50:in > > `execute_cmd' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/platform.rb:73:in > > `block in windows_admin?' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/platform.rb:75:in > > `windows_admin?' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/plugins/providers/hyperv/provider.rb:19:in > > `usable?' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:379:in > > `block in default_provider' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/registry.rb:49:in > > `block in each' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/registry.rb:48:in > > `each' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/registry.rb:48:in > > `each' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:365:in > > `default_provider' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:177:in > > `block in with_target_vms' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:204:in > > `block in with_target_vms' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:186:in > > `each' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:186:in > > `with_target_vms' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/plugins/commands/up/command.rb:87:in > > `execute' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/cli.rb:42:in > > `execute' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:308:in > > `cli' > from > C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/bin/vagrant:138:in > `<main>' > > Almost laughably, when executing *vagrant up* from within PowerShell > running as Admin, vagrant reports: > > The version of powershell currently installed on this host is less than > the required minimum version. Please upgrade the installed version of > powershell to the minimum required version and run the command again. > > Installed version: > Minimum required version: 3 > > Suggestions? > -- 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/681ba33d-2686-4502-964a-6d7e2984939a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
