Vagrant on windows fails to load Chef-Zero due to Chef dependencies

[vinyar]

General info:
C:>vagrant -v
Vagrant 1.4.3

C:>vagrant plugin list
vagrant-berkshelf (1.3.7)
vagrant-chef-zero (0.6.0)
vagrant-omnibus (1.2.1)
vagrant-windows (1.5.1)

Error text:
INFO environment: Loading plugin from JSON: vagrant-chef-zero
ERROR root: Failed to load plugin: vagrant-chef-zero
ERROR root: -- Error: #<Gem::LoadError: Unable to activate chef-11.8.2-x86-mingw32, because ffi-1.9.3-x86-mingw32 conflicts with ffi (= 1.3.1)>
ERROR root: -- Backtrace:
ERROR root: C:/HashiCorp/Vagrant/embedded/lib/ruby/2.0.0/rubygems/specification.rb:2007:in `raise_if_conflicts'

[vinyar]

linked issue to Chef-Zero: chef/chef-zero#55

[andrewgross]

Vagrant Chef Zero on windows is going to be a bit tricky. I have no figured out how to do proper discovery for the chef-zero gem, or fork it as a different process.

[wokandroll]

I am just wondering is there any way around this that other people have thought of or alternatives, I have been racking my brains.

[ghost]

I would be interested in picking this up. Is the issue just around starting and stopping chef zero, having a quick look at the code , the use of lsof and kill, seem to need a windows implementation, is that "all" there is to it? or have I missed something?