BoxStarter not installed. The package was not found with the source(s) listed.

[axcheron]

Hi,

I get an error when the provisioning process starts...

==> default: C:\Windows\system32>choco install BoxStarter
==> default: Chocolatey v0.10.3
==> default: Installing the following packages:
==> default:
==> default: BoxStarter
==> default: By installing you accept licenses for the packages.
==> default: BoxStarter not installed. The package was not found with the source(s) listed.
==> default:
==> default: If you specified a particular version and are receiving this message, it is possible that the package name exists but the version does not.
==> default: Version: ""
==> default: Source(s): "https://chocolatey.org/api/v2/"
==> default:
==> default: Chocolatey installed 0/1 packages. 1 packages failed.
==> default: See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
==> default:
==> default: Failures
==> default: - BoxStarter - BoxStarter not installed. The package was not found with the source(s) listed.
==> default: If you specified a particular version and are receiving this message, it is possible that the package name exists but the version does not.

I checked the connectivity on the VM, but everything is fine. Any ideas ?

System: OS X 10.11.6
VBox 5.1.8
Vagrant 1.8.6

Update 1

According to this issue: chocolatey/choco#1029, NAT seems to be the problem. I managed to manually install BoxStarter by changing my network adapter from NAT to Bridged, but of course it breaks Vagrant's port forward.

[jbarnett-r7]

Thank you for reporting this bug. We were actually seeing the same issue internally but hadn't been able to track down a root cause yet. I checked the issue thread you suggested and they suggested it might be a VirtualBox problem.

Sure enough I found this bug ticket on VirtualBox describing a similar issue. The thread there suggests trying a test build of VirtualBox, 5.1.9 r111846. I installed that one and the issue is no longer present.

[axcheron]

Thanks for your feedback. I downgraded VirtualBox from 5.1.8 to 5.1.6 and it works fine now.

[jbarnett-r7]

Glad to hear it. I updated the docs to reflect the new requirements. I'll keep this issue open as a reminder to remove those requirements once the new version of VirtualBox is released

[Chiggins]

Maybe just because I'm running Arch Linux and it's pretty cutting edge, but I was able to get Metasploitable built and running. VBoxManage -v says 5.1.8r111374

[semml0r]

Current build.sh script states the following:
sh build_win2008.sh A compatible version of VirtualBox was not found. Currently only 5.1.9 is supported. Please download and install it from https://www.virtualbox.org/wiki/Download_Old_Builds_5_1.
So this might be updated too, as 5.1.9 is not released as a public download. According to @axcheron it should point to version 5.1.6.

[jbarnett-r7]

@semml0r That was my bad. I have that build installed locally so I was using that version when testing the script and forgot to fix it before committing. I just changed it back to 5.1.6.

[jbarnett-r7]

The latest version of VirtualBox does not have this issue.

[axcheron]

I also checked, VirtualBox 5.1.12 (r112440) works fine.