Installing VMWare provider makes vagrant commands mostly not work

[Amanda Kabak]

I'm running Windows 8.1 and installed Vagrant version 1.7.2. Before installing the vagrant vmware provider (3.2.9), all vagrant commands would work, returning help information or plugin lists. Once I install the provider (either 3.2.9 or 3.2.7, which is the earliest 3.2 version installed via the .msi), vagrant commands only intermittently work. For example, vagrant plugin list returns the plugin list, but almost all commands followed by -h don't return anything.

I've got colleagues running the same windows version, vagrant version 1.7.2 and the vmware provider 3.2.4 who don't have this problem. Once I uninstall the provider, all my vagrant commands are recognized. Any ideas?

[Alvaro Miranda Aguilera]

Hello Amanda,

As vmware is a paid plugin, can you send an email to sup...@hashicorp.com ?

include the following

vagrant version
vagrant plugin list

and for the commands with errors try this:

VAGRANT_LOG=debug vagrant <command> -h

Thanks!
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 vagrant-up+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/0c4270d7-398f-4823-beb8-6ad35763b466%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.