Virtual Box: Version 5.0.0 r101573
OS Version: 10.0.10240 (Windows 10 Build 10240)
When I add a new host-only network it fails out with the listed error. The Result Code is E_FAIL (0x80004005). If I close out of the VB preferences screen and come back, the NIC shows in the list and it also shows as an adapter in the Network Connections section of my PC. While the NIC is selectable on new VM creation it doesn't work correctly. Whether statically configured or set to get DHCP it isn't able to communicate on the configured subnet.
I can provide any information necessary to help identify/resolve this problem. Also I realize that Windows 10 technically isn't released (for another 7 days) but version 10240 has been identified as the RTM from Microsoft. Any help on this matter would be greatly appreciated.
Failed to create the host network interface.
Re: Failed to create the host network interface.
Not sure how this got posted in Windows Guests but it should have been posted in VirtualBox on Windows Hosts. I don't seem to be able to move it.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Failed to create the host network interface.
Moved it for you.
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Failed to create the host network interface.
It's actually more relevant when VirtualBox first starts claiming support for Win10 guests. While some work has obviously been done, AFAIK there is been no official mention of support. So you kinda have to take it as it is.cringer wrote:I realize that Windows 10 technically isn't released (for another 7 days) but version 10240 has been identified as the RTM from Microsoft.
Anyway, this kind of error usually means that the host-only driver was not installed correctly. How does it appear in Device Manager?
Re: Failed to create the host network interface.
Well the dropdown in VB does list Windows 10 as an OS so it should be relevant enough. Also I figured it was possible another community member has found a fix or walk around. 
In device manager it shows up like any other network adapter. No warnings or anything and when I open it up it says "this device is working properly". Another thing to mention is that the default host-only network adapter that installed with VB works fine, it's adding additional ones that cause the error. I even compared the Adapter properties between the two and there is no difference.
In device manager it shows up like any other network adapter. No warnings or anything and when I open it up it says "this device is working properly". Another thing to mention is that the default host-only network adapter that installed with VB works fine, it's adding additional ones that cause the error. I even compared the Adapter properties between the two and there is no difference.