Windows 10 / VB 5 No Hostonly

[PColella]

Just did a clean install of VirtualBox 5 on a clean install of Winodws 10 (official release) and I cannot get either a working Host Only adapter nor a Bridged adapter. Any help would be greatly appreciated.

Have tried running as administrator, and/or creating devices via command prompt with VBoxManage and although Host Only adapter gets created it does not show in VirtualBox control panel. Creating the device from within the control panel and from the command prompt returns an error.

Thanks

[Esowteric]

Same thing with VB 4.3.30-101610 and the test build 4.3.31-101881.

Everything worked fine in Windows 7 but in Windows 10 release, the bridged adapter won't automatically install. A manual install produces an incorrect success message, but though the updated driver is to be found in system32/drivers, it's not in the list of installable services to manually add to an Ethernet or Wifi adapter.

Running as admin, reinstall VB and repair VB made no difference. Have had to swap from bridged adapter to NAT to launch the guest, so at least I then have internet access.

[michaln]

VirtualBox 4.3 only supports NDIS 5.x networking interfaces, but support for those was dropped in Windows 10. So neither bridged nor host-only networking can possibly work. If that changes in the future, it will be noted in the changelog for some 4.3.xx update.

[PColella]

Thank you michaln for your response regarding VirtualBox 4.3 I'm sure that is helpful information to the person asking about 4.3.

Do you have any insight regarding the original question concerning VirtualBox 5 (current windows version 5.0.0 r101573) and getting either a bridged or host only adapter working in Windows 10 official release?

Thanks

[PColella]

SOLUTION for those experiencing the same problem - VB displays an error when creating Host-only Adapter but creates a non functional one.

Simple go to Device Manager and Update the driver. This worked for me. It also got my Bridged adapters working.