Host-only adapter can not be created on Windows 10 (VirtualBox v5.1.12)

[Allan Kjær]

I was able to install VirtualBox 5.1.12 on Windows 10, but only because I do not install the host-only adapter during installation. If this option is selected the install fails.

After install the command:

''VBoxManage.exe hostonlyif create''

results in:

''0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Querying NetCfgInstanceId failed (0x00000002)
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''

I was unable to find a log file to attach.

Our users use GENYMOTION and VirtualBox to test Android apps. GENYMOTION use a host-only adapter, so GENYMOTION is unable to run.

[Frank Mehnert]

Please upload the VBoxSVC.log file which you can find in the \Users\USER\.VirtualBox directory.

[Allan Kjær]

Replying to frank:

Please upload the VBoxSVC.log file which you can find in the \Users\USER\.VirtualBox directory.

Hi Frank,

It's done. But there's not much information in the log. It seems that the latest log entry is from the 20th of December 2016.

[Frank Mehnert]

The VBoxSVC.log file shows that VBoxNetAdp6.sys is not loaded, that's the reason.

[Allan Kjær]

Replying to frank:

The VBoxSVC.log file shows that VBoxNetAdp6.sys is not loaded, that's the reason.

Hi Frank,

Alright. So it's a bug that VBoxNetAdp6.sys is not loaded?

[Frank Mehnert]

VboxNetAdp6.sys is not installed. Perhaps the feature was disabled during VirtualBox installation.

[Allan Kjær]

Hi Frank,

As I wrote to begin with the installation fails if the host-only adapter is enabled during installation (please see attached video).

[Allan Kjær]

Install fail (7z file, MP4 is too large to attach)

[Frank Mehnert]

In that case please provide an installer log, see here.

[Socratis]

Right-click on the installer, select "Run as Administrator". Choose NOT to run VirtualBox at the end of the installation. See if that helps...

[Allan Kjær]

Replying to socratis:

Right-click on the installer, select "Run as Administrator". Choose NOT to run VirtualBox at the end of the installation. See if that helps...

I run the installation as administrator all the time. It's not possible to NOT run VirtualBox (or RUN it) at the end because the installation fails.

[Allan Kjær]

Install log

[Allan Kjær]

Replying to frank:

In that case please provide an installer log, see here.

Hi Frank,

Done.

[Socratis]

Replying to techallan:

I run the installation as administrator all the time. It's not possible to NOT run VirtualBox (or RUN it) at the end because the installation fails.

Please note that there are two very different things. Huge difference actually:

1. Run while being an administrator. Local or domain doesn't really matter, as long as your permissions are appropriately set.
2. Right-click and select "Run as Administrator". Being logged in as an administrator or not does not matter. This is the mode I propose to everyone with installation problems and it hasn't failed so far.

And you certainly should NOT be running VirtualBox as administrator for everyday use. If you have to, something is not right in your system.

[Allan Kjær]

Replying to socratis:

Replying to techallan:

I run the installation as administrator all the time. It's not possible to NOT run VirtualBox (or RUN it) at the end because the installation fails.

Please note that there are two very different things. Huge difference actually:

1. Run while being an administrator. Local or domain doesn't really matter, as long as your permissions are appropriately set.
2. Right-click and select "Run as Administrator". Being logged in as an administrator or not does not matter. This is the mode I propose to everyone with installation problems and it hasn't failed so far.

And you certainly should NOT be running VirtualBox as administrator for everyday use. If you have to, something is not right in your system.

I know :-) I work as an IT-administrator so I know my way around IT.

[VVP]

Hello, as i see from the installation log a Virtualbox installation was marked as "unsuccessful" and i suppose it happened due to a failed attempt to create a Host-Only interface:

MSI (s) (B0:78) [11:40:24:081]: Executing op: ActionStart(Name=ca_CreateHostOnlyInterfaceNDIS6,,)
MSI (s) (B0:78) [11:40:24:083]: Executing op: CustomActionSchedule(Action=ca_CreateHostOnlyInterfaceNDIS6,ActionType=3073,Source=BinaryData,
Target=Ndis6CreateHostOnlyInterface,
CustomActionData=C:\Program Files\Oracle\VirtualBox\drivers\network\netadp6\)
MSI (s) (B0:F0) [11:40:24:087]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI5D5.tmp, Entrypoint: Ndis6CreateHostOnlyInterface
CreateHostOnlyInterface: Creating host-only interface
CreateHostOnlyInterface: NetAdpDir property = C:\Program Files\Oracle\VirtualBox\drivers\network\netadp6\
CreateHostOnlyInterface: Resulting INF path = C:\Program Files\Oracle\VirtualBox\drivers\network\netadp6\VBoxNetAdp6.inf
CreateHostOnlyInterface: Calling VBoxDrvCfgInfInstall(C:\Program Files\Oracle\VirtualBox\drivers\network\netadp6\VBoxNetAdp6.inf)
CreateHostOnlyInterface: VBoxDrvCfgInfInstall returns 0x0
UpdateHostOnlyInterfaces: VBoxNetCfgWinUpdateHostOnlyNetworkInterface failed, hr = 0xe000020b
CreateHostOnlyInterface: calling VBoxNetCfgWinCreateHostOnlyNetworkInterface
Timed out while waiting for NetCfgInstanceId, try again immediately...
Timed out again while waiting for NetCfgInstanceId, try again after a while...
NetSetupSvc is not running
CustomAction ca_CreateHostOnlyInterfaceNDIS6 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

[Allan Kjær]

Replying to VVP:

Hello, as i see from the installation log a Virtualbox installation was marked as "unsuccessful" and i suppose it happened due to a failed attempt to create a Host-Only interface:

MSI (s) (B0:78) [11:40:24:081]: Executing op: ActionStart(Name=ca_CreateHostOnlyInterfaceNDIS6,,)
MSI (s) (B0:78) [11:40:24:083]: Executing op: CustomActionSchedule(Action=ca_CreateHostOnlyInterfaceNDIS6,ActionType=3073,Source=BinaryData,
Target=Ndis6CreateHostOnlyInterface,
CustomActionData=C:\Program Files\Oracle\VirtualBox\drivers\network\netadp6\)
MSI (s) (B0:F0) [11:40:24:087]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI5D5.tmp, Entrypoint: Ndis6CreateHostOnlyInterface
CreateHostOnlyInterface: Creating host-only interface
CreateHostOnlyInterface: NetAdpDir property = C:\Program Files\Oracle\VirtualBox\drivers\network\netadp6\
CreateHostOnlyInterface: Resulting INF path = C:\Program Files\Oracle\VirtualBox\drivers\network\netadp6\VBoxNetAdp6.inf
CreateHostOnlyInterface: Calling VBoxDrvCfgInfInstall(C:\Program Files\Oracle\VirtualBox\drivers\network\netadp6\VBoxNetAdp6.inf)
CreateHostOnlyInterface: VBoxDrvCfgInfInstall returns 0x0
UpdateHostOnlyInterfaces: VBoxNetCfgWinUpdateHostOnlyNetworkInterface failed, hr = 0xe000020b
CreateHostOnlyInterface: calling VBoxNetCfgWinCreateHostOnlyNetworkInterface
Timed out while waiting for NetCfgInstanceId, try again immediately...
Timed out again while waiting for NetCfgInstanceId, try again after a while...
NetSetupSvc is not running
CustomAction ca_CreateHostOnlyInterfaceNDIS6 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Sure. I guess it's a bug in the installation? I've tried this on 2 different Windows 10 Enterprise installation, different Windows 10 Enterprise builds, though.

[VVP]

Apologize for repeating about the failed installation, but if the host-only interface wasn't installed the other commands like "VBoxManage.exe hostonlyif create" will lead to the same results.

[Allan Kjær]

Replying to VVP:

Apologize for repeating about the failed installation, but if the host-only interface wasn't installed the other commands like "VBoxManage.exe hostonlyif create" will lead to the same results.

Yes. When running the vboxmanage command the experience is the same as when enabling the interface during installation. The interface shows up in Windows' device manager for a few seconds and then disappears again.

[VVP]

just for information. A fresh test - the latest 5.1.12 version is installed on Win10 1511 build normally. Host-only adapter is created.

[Allan Kjær]

Replying to VVP:

just for information. A fresh test - the latest 5.1.12 version is installed on Win10 1511 build normally. Host-only adapter is created.

I'm running Windows 10 Enterprise, version 1607, build 14393.693.

[Frank Mehnert]

So the Windows 10 build is most likely the reason for the problem.

[Allan Kjær]

Replying to frank:

So the Windows 10 build is most likely the reason for the problem.

Alright. This could be, but it should still work on build 14393, right?

[Frank Mehnert]

Yes, it should work. I just upgraded my Windows 10 to 14393.693 and installed VBox 5.1.12 including support for host-only adapters. No problem experienced, the VBoxNetAdp6.sys driver was properly installed.

[Aleksey Ilyushin]

Please install VirtualBox without host-only support, then run VBoxBugReport and send the resulting archive to me at aleksey dot ilyushin at oracle dot com. The tool collects system info including logs, network configuration, etc.

[Allan Kjær]

Replying to aleksey:

Please install VirtualBox without host-only support, then run VBoxBugReport and send the resulting archive to me at aleksey dot ilyushin at oracle dot com. The tool collects system info including logs, network configuration, etc.

Hi Aleksey. This is done now. Thanks.

[Frank Mehnert]

Fix is part of VBox 5.1.16.