VirtualBox 4.3.28 version not recognized by

[shahzadamjadk]

Hi,
I am using windows 8.1 (fully updated). I am trying to create a sparkVM for a machine learning course using vagrant 1.7.2 and vitualbox 4.3.28 (latest version). However when I run "vagrant up --provider=virtualbox" in the command prompt I keep getting the following error:

C:\Users\Dr Shehzad\myvagrant>vagrant up --provider=virtualbox
C:/HashiCorp/Vagrant/embedded/gems/gems/i18n-0.6.11/lib/i18n/config.rb:83:in `bl
ock in missing_interpolation_argument_handler': missing interpolation argument :
vboxmanage in "Vagrant detected that VirtualBox appears installed on your system
,\nbut calls to detect the version are returning empty. This is often\nindicativ
e of installation issues with VirtualBox. Please verify\nthat VirtualBox is prop
erly installed. As a final verification,\nplease run the following command manua
lly and verify a version is\noutputted:\n\n%{vboxmanage} --version" ({:_key=>:vi
rtualbox_version_empty, :_namespace=>"vagrant.errors"} given) (I18n::MissingInte
rpolationArgument)

I have repeatedly deleted and re-installed both vagrant and virtualbox (also an administrator) but the error keeps showing, so likely not an issue with download errors. noted that Comodo internet security is incompatible with virtualbox 4.3.28 so I disabled it and tried again multiple times but the same message keeps coming back. Running the "\n\n%<vboxmanage> --version" command returns "the system cannot find the file specified"? Where and how do I add the version file to my installed virtual box? How do I make vagrant talk to virtual box. I have also sought help on the courses discussion forum but they don't seem to have a clue. Any ideas?

[scottgus1]

Sorry, Vagrant uses Virtualbox in a way that isn't supported here. You'll have to ask the Vagrant folks about your problem.

[shahzadamjadk]

I understand vagrant issues may not be supported here but why does running the "\n\n%<vboxmanage> --version" command return "the system cannot find the file specified"? This should have to do with virtual box itself. Is there a file missing? Any known incompatibility with new windows updates etc?

[Perryg]

For the same reason we don't support vagrant. Type VBoxManage --version in a user space terminal and see if it returns anything.