That does not make any difference. The problem is somewhere in the core packages. I can't say for certain but I think this all worked under 1.8 .
DEBUG host: Trying: bsd DEBUG host: Trying: linux DEBUG host: Trying: null DEBUG host: Trying: windows INFO host: Detected: windows! INFO runner: Preparing hooks for middleware sequence... INFO runner: 1 hooks defined. INFO runner: Running action: environment_unload #<Vagrant::Action::Builder:0x00000000069449d0> ERROR vagrant: Vagrant experienced an error! Details: ERROR vagrant: #<Vagrant::Errors::PowerShellNotFound: Failed to locate the powershell executable on the available PATH. Please ensure powershell is installed and available on the local PATH, then run the command again.> ERROR vagrant: Failed to locate the powershell executable on the available PATH. Please ensure powershell is installed and available on the local PATH, then run the command again. ERROR vagrant: C:/opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/ util/powershell.rb:94:in `validate_install!' C:/opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/powershell.rb:50:in `execute_cmd' C:/opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/platform.rb:73:in `block in windows_admin?' C:/opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/util/platform.rb :75:in `windows_admin?' C:/opt/vagrant/embedded/gems/gems/vagrant-2.0.1/plugins/providers/hyperv/provider.rb:19:in `usable?' C:/opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:379:in `block in default_provider' C:/opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/registry.rb:49: in `block in each' C:/opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/registry.rb:48:in `each' C:/opt/vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/registry.rb:48:in `each' On Saturday, February 3, 2018 at 12:04:35 AM UTC+10, Alvaro Miranda Aguilera wrote: > > so, remove the hostname, and disable the default shared folder > > config.vm.synced_folder ".", "/vagrant", disabled: true > > > see if that at least start the VM > > from there maybe, you can play with the communicator set it to ssh and see > if that works. > > > > On Fri, Feb 2, 2018 at 2:58 PM, Niels Bertram <[email protected] > <javascript:>> wrote: > >> As simple as below. There are quite a few issues in github re vagrant >> hanging on Windows 7 due to an older version of powershell... but we have >> NO powershell. >> >> # -*- mode: ruby -*- >> # vi: set ft=ruby : >> >> >> Vagrant.configure("2") do |config| >> config.vm.box = "maier/alpine-3.6-x86_64" >> config.vm.hostname = "alpine" >> end >> >> >> On Friday, February 2, 2018 at 11:37:56 PM UTC+10, Alvaro Miranda >> Aguilera wrote: >>> >>> whats your vagrantfile ? >>> >>> >>> On Fri, Feb 2, 2018 at 1:18 PM, Niels Bertram <[email protected]> wrote: >>> >>>> Hi there, is there a way to run vagrant up without needing powershell >>>> on a Windows PC? >>>> >>>> Powers above have decided to disabled powershell and now Vagrant is >>>> failing to even boot the most simple machines. >>>> >>>> c:\test\vagrant-box> vagrant up >>>> Failed to locate the powershell executable on the available PATH. >>>> Please >>>> ensure powershell is installed and available on the local PATH, then >>>> run the command again. >>>> >>>> Any thoughts or tips on this would be much appreciated. >>>> >>>> Cheers Niels >>>> >>>> -- >>>> 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/656bd3b8-7113-42da-8045-9cbade1aa45c%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/vagrant-up/656bd3b8-7113-42da-8045-9cbade1aa45c%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> Alvaro >>> >>> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/16af71e6-c1de-47ba-9836-b813ef7614fa%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/16af71e6-c1de-47ba-9836-b813ef7614fa%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Alvaro > > -- 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/e75f049d-5bad-436e-b74e-0010e16df217%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
