locked
Xamarin Android Player "Could not configure host-only network. Please reboot the system..." Error RRS feed

  • Question

  • User138378 posted

    I upgraded Windows 8.1 to Windows 10 and i cant run Xamarin Android Player. What can i do?

    Screenshots:

    Thursday, July 30, 2015 2:09 PM

Answers

  • User103830 posted

    Here is what you should do. Based on this answer: https://forums.xamarin.com/discussion/comment/119949#Comment_119949

    I opened VirtualBox, then from File -> Preferences -> Networks -> Host-only Networks I deleted all 20 adapters from previous failed attempts, leaving just one. Then I manually modified it's IP address to be 10.71.34.1 and network mask 255.255.255.0, clicked OK on all dialog boxes, closed VirtualBox and tried again to install the emulator. And it worked this time.

    Hope this helps

    • Marked as answer by Anonymous Thursday, June 3, 2021 12:00 AM
    Friday, July 31, 2015 1:11 AM

All replies

  • User103830 posted

    Here is what you should do. Based on this answer: https://forums.xamarin.com/discussion/comment/119949#Comment_119949

    I opened VirtualBox, then from File -> Preferences -> Networks -> Host-only Networks I deleted all 20 adapters from previous failed attempts, leaving just one. Then I manually modified it's IP address to be 10.71.34.1 and network mask 255.255.255.0, clicked OK on all dialog boxes, closed VirtualBox and tried again to install the emulator. And it worked this time.

    Hope this helps

    • Marked as answer by Anonymous Thursday, June 3, 2021 12:00 AM
    Friday, July 31, 2015 1:11 AM
  • User104444 posted

    @ApostolApostolov thanks! saved me a lot of grief.

    Saturday, August 1, 2015 10:51 AM
  • User147169 posted

    @ApostolApostolov thank you!

    Tuesday, August 4, 2015 5:01 AM
  • User24352 posted

    Thank you sir!

    Tuesday, August 4, 2015 11:59 PM
  • User97392 posted

    @ApostolApostolov thanks!

    Wednesday, August 5, 2015 9:59 AM
  • User148468 posted

    @ApostolApostolov appreciated!

    Monday, August 10, 2015 5:30 PM
  • User148314 posted

    @ApostolApostolov Thanks =)

    Wednesday, August 12, 2015 6:51 PM
  • User150652 posted

    I am using VS2015 Community and installed Xamarin Android Player at home. My internet access set up is as follows: Using Android phone hotspot connected wirelessly to my laptop.

    I also had the same problems outlined above when trying to install a virtual device using XAP. The fix posted by ApostolApostolov did not work with my set up and installation still failed with the same error.

    I fiddled around and eventually fixed it by navigating to the C:\Program Files\Xamarin Android Player\ folder and running first setNetworkRegistryValues.exe as Administrator, then DeviceManager.exe as Administrator. When I proceeded with the device install this time it set my network up correctly and 'ta da' my emulator worked correctly.

    Monday, August 17, 2015 1:23 PM
  • User55839 posted

    Still Having issues. Manually adding a network to virtual box gives me an error.

    "E_Fail"

    Saturday, August 29, 2015 4:25 AM
  • User104444 posted

    For the folks still having issues with XAP on Windows 10, there is a much better way to test/debug android apps, using the Visual Studio Emulator for Android. It is free and can be downloaded from https://visualstudio.com/en-us/features/msft-android-emulator-vs.aspx. The emulator requires Hyper-V so make sure to have that feature turned on. One installed start it up and it will show up in Xamarin Studio as a physical device. You can now deploy and debug your app without all the pains of the XAP.

    Tuesday, September 1, 2015 8:31 PM
  • User155489 posted

    i have same problem .ibut very easy to fix . just do this . i know this answer is to late .but it help you all can do it easy than way before

    Thursday, September 3, 2015 4:05 AM
  • User149772 posted

    I have tried everything on thing in this post but still can't get XAP running.

    I get errors from setNetworkRegistryValues.exe.

    Manually changing the host only adapter address to anything also does not work because XAP immediately changes it back to a 169 address.

    Running as admin does not work.

    Running setNetworkRegistryValues.exe and devicemamanger.exe as admin does not work.

    Configuring compatibility to Windows 8 does not make any difference.

    Repair does not work!

    Any help or ideas appreciated.

    Sunday, December 6, 2015 4:59 AM