Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 39579 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 15393 [details]
Could not configure host-only network
I got the attached errors upon installing the emulators from XAP
- Could not configure host-only network
Created attachment 15394 [details]
No suitable-host only network found
I had the same error a while back in the summer of 2015 when I first upgraded my system from Windows 8 to 10. And now after the Windows 10 update of march, which I received over the weekend, it's back.
When I attempt to create the host-adapter from the command line I get the following stack trace:
[Drive]:\Program Files\Oracle\VirtualBox>vboxmanage hostonlyif create
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Could not find Host Interface Networking driver! Please reinstall
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 71 of file VBoxManageHostonly.cpp
Where you able to fix this issue? How?
I was able to resolve the "Failed to create the host-only adapter" error by not repairing but uninstalling and re-installing VirtualBox. Because only on the intial installtion it creates the virtual network adapters which it need to be able to create virtual host-only adapters.
BUT after the installation I was unable to get any of the Xamarin Android Players passed the boot process. They all hung without any form of error message. I've now installed an Android Virtual Device with Intel HAXM, but the boot process and debugging is noticably slower than a Xamarin Android Player.
So at least the situation I'm now in is something, but far from ideal.