virtualbox.org

Yes I know this is a beta OS, but I figured there is some way to get this to work and I was right. I first tried bridge networking but that is completely busted in Windows 10. The VB 5 beta bridged adapter actually works fine but Vagrant doesn't support 5 yet. So in 4.3 I noticed that when creating a host only adapter it did error but the new host only adapters showed up in the device manager. Each time you try it adds a new one but it didn't show up in the list in VB. And then digging further I noticed that host only adapters show up to edit in virtualbox ONLY when you run virtualbox as administrator. However, it errors on creation whether running as admin or not. Once created however you can edit and save it just fine. So what you do is try to create one and it will error. Restart virtualbox as administrator. In the adapters you will have the automatically created one and you can edit is as normal and add it to adapters on VMs. With this I was able to get our vagrant working fine while turning off auto_config so it doesn't try to create a new interface each time. Once again I had to run the command line as admin so vagrant was running virtualbox as administrator. So the most recent issues after 10041 appear to stem from permissions on the newly created host only adapter and VB can only be run as admin in the newest builds if you want host only adapters.

Did you get a solution? I am using Genymotion that requires a host only network, but running VB as admin is not an option for Genymotion.

Anybody have a solution for this? Still not working with Windows 10 build 10158. I think at this point it's not going to be fixed by a Windows update, it's almost final. What's interesting is that it actually DOES create the host-only adapter if you look in Device Manager -> Network Adapters. But something is going wrong at the end of the process that reports E_FAIL. I think it is probably very close to working.

Please keep all discussion about Windows 10 host on the dedicated topic.