Windows 10 host only creation failes [5.1.1]

[Dosenblech]

Hi!

On the latest devel build VirtualBox-5.1.1-108727-Win.exe and on a few other builds I tried I can't create host only network adapters. It didn't even create one after installation. I've seen a few similiar threads and tried different workarounds such as doing it with vboxmanage, the VBox-Win10-fix-14040.exe, admin privileges, NDIS5 driver, no UAC, compatibility mode and so on.

Translated error message from GUI:

A host interface could not be created.

Querying NetCfgInstanceId failed (0x00000002).

Error code:E_FAIL (0x80004005)
Component:HostNetworkInterfaceWrap
Interface:IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}

[Aleksey Ilyushin]

Thanks for the provided logs! I do not see neither vboxnetadp6.sys (host-only) nor vboxnetlwf.sys (bridged) drivers installed on your system. This could be an installation issue. Please uninstall VirtualBox, then install it back with logging enabled as described here. I only need the installer log. Driver installation logs are already included into the bug report you have provided.

[Dosenblech]

Now it won't let me finish my installation despite I rebooted and deleted the old folder.

Installation failed! Error: Critical error

Attached two logs, the later one I tried with admin privileges.

[Aleksey Ilyushin]

Thanks for the logs! Both times the installer failed at creating host-only interface. Let me try to reproduce the problem locally and get back to you.

[Aleksey Ilyushin]

I cannot reproduce the problem locally, everything works fine here. Try following these steps:

1. Make sure no installation of VirtualBox is listed in Control Panel;
2. Install VirtualBox without host-only networking by selecting "Entire feature won't be available" for "VirtualBox Host-Only Networking" on "Custom Setup" page during installation;
3. Generate and upload another bug report so I could see the current state.

Thanks in advance!

[Dosenblech]

The installation still failed, see attached log. Deselect NAT feature too?

[Dosenblech]

Installation succeeded without NAT and hostif, attached the bugreport.

[Aleksey Ilyushin]

I am 99% sure that the installer fails because network configuration engine fails to load VBoxNetFltNobj.dll, hence VBoxNetCfgWinInstallComponent failed, hr (0x8007007e) message in the installer log. Now, this DLL is not needed for NDIS6 drivers, but it looks like you got it registered with network configuration engine by applying all kinds of workarounds. I suggest you to re-install your system and, please, refrain from using all these heal-yourself remedies floating around the Internet in the future. If something does not work out of the box, file a bug report and we will try to help. If you want to confirm or refute my guess, install ​ProcMon from TechNet, capture system events during VirtualBox installation (with bridge and host-only networking) and try to find VBoxNetFltNobj.dll in the captured events. Sorry about not being able to help you further at this point.

[Dosenblech]

Okay, that's sad to hear. Anyway thanks for your efforts!