Vagrant: Vagrant commands not working for Hyper-V provisioner

[oldluke92]

Vagrant version

2.1.0

Host operating system

Windows 10 v1803 (April Update)

Guest operating system

Ubuntu 16.04

Vagrantfile

Vagrant.configure("2") do |config|
  config.vm.box = "generic/ubuntu1604"
end

Debug output

vagrant destroy log

Expected behavior

Vagrant command should be executed

Actual behavior

Error occures:

C:/HashiCorp/Vagrant/embedded/gems/2.1.0/gems/vagrant-2.1.0/lib/vagrant/machine.rb:164:in `action': undefined method `fire_triggers' for nil:NilClass (NoMethodError)
[...]

Steps to reproduce

1. Get a pc with Windows 10 pro x64 and HyperV
2. Install Vagrant 2.1.0
3. Place the contents of the mentioned Vagrantfile above in a Vagrantfile in some directory
4. Repair the 'vagrant up' Command (see #9774 )
5. Start powershell as administrator (Click on the windows logo on your windows taskbar, type "powershell", right-click the "Windows Powershell" entry and click the "Run as Administrator" option.
6. Navigate to the directory with the above mentioned Vagrantfile in the powershell window
7. type 'vagrant up', hit enter and wait for the VM to be created and booted
8. try using 'vagrant halt', 'vagrant destroy', 'vagrant ssh' or 'vagrant provision' (I'm pretty sure any other command will fail too, but these are the ones I tested)

[josenk]

Also a problem with vagrant-vmware-esxi.
https://github.com/josenk/vagrant-vmware-esxi/issues/39

I can confirm the problem is resolved in Vagrant 2.1.1.dev.

[hashibot[bot]]

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.