VirtualBox

Ticket #15019 (new defect)

Opened 22 months ago

Last modified 6 months ago

Unable to create Host-Only Network in Windows 10

Reported by: rkurniawan Owned by:
Priority: major Component: network/hostif
Version: VirtualBox 5.0.12 Keywords:
Cc: Guest type: all
Host type: Windows

Description

I was unable to create host-only network in Windows 10 Home Single Language using VBoxManage hostonlyif create with following output:

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

Attachments

bugreport.tgz Download (40.8 KB) - added by rkurniawan 21 months ago.
Capture.JPG Download (37.4 KB) - added by gokumar 21 months ago.
Error
Cattura.PNG Download (19.9 KB) - added by Vito 15 months ago.
NDIS6 bridged unselected

Change History

comment:1 follow-up: ↓ 17 Changed 21 months ago by Spanky

I'm seeing the same error with VirtualBox 5.0.14, running with Vagrant 1.8.1 on Windows 7 Enterprise:

D:\Development\XNAT\1.7\xnat_vagrant>vagrant up
Loading default.yaml for Vagrant configuration...
Loading additional customizations from custom.yaml...
Bringing machine 'xnatdev' up with 'virtualbox' provider...
==> xnatdev: Importing base box 'xnatstack-ubuntu1504-docker'...
==> xnatdev: Matching MAC address for NAT networking...
==> xnatdev: Setting the name of the VM: xnatdev
==> xnatdev: Clearing any previously set network interfaces...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "create"]

Stderr: 0%...
Progress state: E_INVALIDARG
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Assertion failed: [!aInterfaceName.isEmpty()] at 'F:\tinderbox\win-5.0\src\VBox\Main\src-server\HostNetworkInterfaceImpl.cpp' (74) in long __cdecl HostNetworkInterface::init(class com::Bstr,class com::Bstr,class com::Guid,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0036).
VBoxManage.exe: error: Please contact the product vendor!
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

This is a complete blocker. I'm not running anything particularly weird on the machine, the latest version of MS System Center Endpoint Protection for anti-virus (some similar errors seemed to indicate issues with Kaspersky security tools).

comment:2 Changed 21 months ago by aleksey

Please download build 105257, uninstall existing version of VirtualBox, install build 105257 and run VBoxBugReport tool. By default it creates bugreport.tgz in the current directory, so you should run it from the directory you have write access to. Alternatively you can specify full path and name with -o option. You can check the contents and send the resulting file to me at aleksey dot ilyushin at oracle dot com, as it may potentially contain some sensitive information, not suitable for posting here in the tracker -- it is up to you how to provide the file.

comment:3 Changed 21 months ago by frank

  • Priority changed from blocker to major

comment:4 Changed 21 months ago by gokumar

Exact same problem on "Version 5.0.12 r104815" (Windows 7)...

(default) Creating a new host-only adapter produced an error: C:\Program Files\O
racle\VirtualBox\VBoxManage.exe hostonlyif create failed:
(default) 0%...
(default) Progress state: E_FAIL
(default) VBoxManage.exe: error: Failed to create the host-only adapter
(default) VBoxManage.exe: error: SetupDiCreateDeviceInfo failed (0x00000005)
(default) VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component Ho
stNetworkInterfaceWrap, interface IHostNetworkInterface
(default) VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(
struct HandlerArg *)" at line 71 of file VBoxManageHostonly.cpp
(default)
(default) This is a known VirtualBox bug. Let's try to recover anyway...
Error creating machine: Error in driver during machine creation: Error setting u
p host only network on machine start: Failed to find a new host-only adapter
Looks like something went wrong... Press any key to continue...
Last edited 21 months ago by gokumar (previous) (diff)

comment:5 follow-up: ↓ 6 Changed 21 months ago by aleksey

Is anyone willing to try VBoxBugReport tool from build 105257? See details in comment:2.

comment:6 in reply to: ↑ 5 ; follow-up: ↓ 7 Changed 21 months ago by gokumar

Replying to aleksey:

Is anyone willing to try VBoxBugReport tool from build 105257? See details in comment:2.

Sent you the bug report by mail.

comment:7 in reply to: ↑ 6 ; follow-up: ↓ 8 Changed 21 months ago by aleksey

Replying to gokumar:

Sent you the bug report by mail.

Thanks a lot for the bug report. Judging by the logs this may have something to do with driver signing. Could you try to lower UAC setting all the way down in Control Panel (type uac in search box, click Change User Account Control Settings)? Just make sure you turn it back on after trying to create host-only adapter. If you still get errors, please send me another bug report using build 105380. It will pick up Setup API logs as well, which may provide more detailed information on the issue.

comment:8 in reply to: ↑ 7 ; follow-up: ↓ 9 Changed 21 months ago by gokumar

Replying to aleksey:

Replying to gokumar:

Sent you the bug report by mail.

Thanks a lot for the bug report. Judging by the logs this may have something to do with driver signing. Could you try to lower UAC setting all the way down in Control Panel (type uac in search box, click Change User Account Control Settings)? Just make sure you turn it back on after trying to create host-only adapter. If you still get errors, please send me another bug report using build 105380. It will pick up Setup API logs as well, which may provide more detailed information on the issue.

It is already at the lowest level. Do you want me to still use the build 105380 and send you the bug report?

comment:9 in reply to: ↑ 8 ; follow-up: ↓ 12 Changed 21 months ago by aleksey

Replying to gokumar:

It is already at the lowest level. Do you want me to still use the build 105380 and send you the bug report?

Yes, please do. I may be wrong about code signing.

Changed 21 months ago by rkurniawan

comment:10 Changed 21 months ago by rkurniawan

Using build 105380 I successfully created host only interface.

Here what I did:

  1. Lowering UAC to lowest level
  2. create host only interface using VBoxManage

I also attach the bug report.

comment:11 follow-up: ↓ 14 Changed 21 months ago by rkurniawan

I started the VM using the host adapter that was created, I got this error:

Failed to open a session for the virtual machine CentOS 7.

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_SUPDRV_COMPONENT_NOT_FOUND).

Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

Changed 21 months ago by gokumar

Error

comment:12 in reply to: ↑ 9 ; follow-up: ↓ 13 Changed 21 months ago by gokumar

Replying to aleksey:

Replying to gokumar:

It is already at the lowest level. Do you want me to still use the build 105380 and send you the bug report?

Yes, please do. I may be wrong about code signing.

With this, I am unable to run VBoxBugReport.exe. I get the following error. https://www.virtualbox.org/attachment/ticket/15019/Capture.JPG

Last edited 21 months ago by gokumar (previous) (diff)

comment:13 in reply to: ↑ 12 ; follow-up: ↓ 15 Changed 21 months ago by aleksey

Replying to gokumar:

With this, I am unable to run VBoxBugReport.exe. I get the following error. https://www.virtualbox.org/attachment/ticket/15019/Capture.JPG

This is most probably caused by the lack of write access to VirtualBox installation directory. Please run the tool for the directory you have write access to, or use -o option to specify the output file with path to a writable location. If you do have write access, then check if the output file already exists. The tool intentionally does not overwrite existing files in order not to loose important information.

comment:14 in reply to: ↑ 11 ; follow-up: ↓ 19 Changed 21 months ago by aleksey

Replying to rkurniawan:

I started the VM using the host adapter that was created, I got this error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_SUPDRV_COMPONENT_NOT_FOUND).

Thank you for providing the logs. Setup API logs indicate that the "VirtualBox NDIS6 Bridged Networking Driver" (aka VBoxNetLwf.sys) has been installed, but VBoxSVC.log and the output of adapter enumerator clearly indicate that the driver has not been loaded. Without the bridging driver VirtualBox cannot use host-only adapters (since 5.0). Two questions:

  1. Is there anything special about the way you install VirtualBox or you just launch the executable and follow the GUI prompts?
  2. Do you have  KB3033929 update installed? You can check it by running the following command:
    wmic qfe list brief | findstr 3033929
    

comment:15 in reply to: ↑ 13 ; follow-up: ↓ 16 Changed 21 months ago by gokumar

Replying to aleksey:

Replying to gokumar:

With this, I am unable to run VBoxBugReport.exe. I get the following error. https://www.virtualbox.org/attachment/ticket/15019/Capture.JPG

This is most probably caused by the lack of write access to VirtualBox installation directory. Please run the tool for the directory you have write access to, or use -o option to specify the output file with path to a writable location. If you do have write access, then check if the output file already exists. The tool intentionally does not overwrite existing files in order not to loose important information.

That helped. I ran as Administrator and I am now able to capture bug report. I have sent the bug report by email. I have replied to my last email just so that it does not fall in spam/junk and so that you get the context as well.

Thanks for helping out.

comment:16 in reply to: ↑ 15 ; follow-up: ↓ 18 Changed 21 months ago by aleksey

Replying to gokumar:

That helped. I ran as Administrator and I am now able to capture bug report. I have sent the bug report by email. I have replied to my last email just so that it does not fall in spam/junk and so that you get the context as well.

Thanks again for the bug report. Everything appears to be properly installed. Notice that your problem is actually different from the one the original reporter (rkurniawan) is experiencing. When you run VBoxManage hostonlyif create with build 105380 do you still get

(default) VBoxManage.exe: error: SetupDiCreateDeviceInfo failed (0x00000005)

or is it another error message? If the message is different this time please post it here. Does the user account that you run the command under have administrator privileges?

One more thing: according to the logs you have a host-only adapter, the one that gets created during VirtualBox installation, right? And do you get the error when trying to create another one? Did you try to remove the existing host-only adapter?

comment:17 in reply to: ↑ 1 Changed 21 months ago by aleksey

Replying to Spanky:

I'm seeing the same error with VirtualBox 5.0.14, running with Vagrant 1.8.1 on Windows 7 Enterprise:

What do you get if you run VBoxManage hostonlyif create from command prompt? The same error, or is it different somehow?

comment:18 in reply to: ↑ 16 Changed 21 months ago by gokumar

Replying to aleksey:

Replying to gokumar:

That helped. I ran as Administrator and I am now able to capture bug report. I have sent the bug report by email. I have replied to my last email just so that it does not fall in spam/junk and so that you get the context as well.

Thanks again for the bug report. Everything appears to be properly installed. Notice that your problem is actually different from the one the original reporter (rkurniawan) is experiencing. When you run VBoxManage hostonlyif create with build 105380 do you still get

(default) VBoxManage.exe: error: SetupDiCreateDeviceInfo failed (0x00000005)

or is it another error message? If the message is different this time please post it here. Does the user account that you run the command under have administrator privileges?

One more thing: according to the logs you have a host-only adapter, the one that gets created during VirtualBox installation, right? And do you get the error when trying to create another one? Did you try to remove the existing host-only adapter?

I still see the following errors:

(default) Progress state: E_FAIL

(default) VBoxManage.exe: error: Failed to create the host-only adapter

(default) VBoxManage.exe: error: SetupDiCreateDeviceInfo failed (0x00000005)

(default) VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component Ho
stNetworkInterfaceWrap, interface IHostNetworkInterface

(default) VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(
struct HandlerArg *)" at line 71 of file VBoxManageHostonly.cpp

Not sure what you mean by removing existing host-only adapter. You will have to help me if I have to remove. Let me explain what I am trying to do. I am trying to install Docker Toolbox on my windows 7 box. Post installation when I start "Docker Quickstart Terminal", I see the above errors.

comment:19 in reply to: ↑ 14 Changed 21 months ago by rkurniawan

Replying to aleksey:

Thank you for providing the logs. Setup API logs indicate that the "VirtualBox NDIS6 Bridged Networking Driver" (aka VBoxNetLwf.sys) has been installed, but VBoxSVC.log and the output of adapter enumerator clearly indicate that the driver has not been loaded. Without the bridging driver VirtualBox cannot use host-only adapters (since 5.0). Two questions:

  1. Is there anything special about the way you install VirtualBox or you just launch the executable and follow the GUI prompts?
  2. Do you have  KB3033929 update installed? You can check it by running the following command:
    wmic qfe list brief | findstr 3033929
    
  1. No, I just launched the executable and follow the GUI prompts.
  2. Do I need to install the update? Because I am using Windows 10 which was upgraded from Windows 8.1. The site tells the update is already inside Windows 8.1 so there is no need to install the update anymore. Also the command shown empty line.

comment:20 follow-up: ↓ 21 Changed 20 months ago by pazoozoo

I also experience this problem. After installation, I at least had one working interface: 192.168.56.0/24.

However, I cannot add any new host only interface, neither through the GUI nor using VBoxManage.

I would be fine for the moment if I could just add new interface somehow manually. Is there a way to copy an existing interface for a new subnet manually?

Besides that, the interface creation seems to be extremely shaky looking at the ticket history. A lot of problems with this crucual functionality! Would be good if that could be stabilized for future releases, expecially for Windows 10...

comment:21 in reply to: ↑ 20 Changed 20 months ago by aleksey

Replying to pazoozoo:

Besides that, the interface creation seems to be extremely shaky looking at the ticket history. A lot of problems with this crucual functionality! Would be good if that could be stabilized for future releases, expecially for Windows 10...

Please download and install the latest test build from here. Run VBoxBugReport and provide the resulting archive to me via aleksey dot ilyushin at oracle dot com. Your help is very much appreciated.

Changed 15 months ago by Vito

NDIS6 bridged unselected

comment:23 Changed 15 months ago by Vito

Hello, since the first time I had this same issue, every time I upgrade virtualbox (this just happened with 5.1.2 again) I run into this issue, that I regularly solve following these directions:  http://stackoverflow.com/questions/33725779/failed-to-open-create-the-internal-network-vagrant-on-windows10

(I re-enable the VirtualBox NDIS6 Bridged Networking Driver that the installer forgets to enable):

NDIS6 bridged unselected

Windows 10 professional 64 bit host.

comment:24 Changed 12 months ago by Abdel

In my case I had the same error when running a  vagrant setup. Turns out that I had to run the command with elevated administrator privileges inside Windows 10 (Run as administrator). I also removed the compatibility mode in the "VirtualBox.exe"

comment:25 Changed 11 months ago by Daedalus

I seem to be having the same issue as above, however, I don't seem to have the "VirtualBox Host-Only" network adapter in my network configurations list.

I am running version 5.0.30

C:\Program Files\Oracle\VirtualBox>VBoxManage.exe hostonlyif create
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

comment:26 Changed 10 months ago by Airell

Same issue still exists on 5.1.10:

c:\Program Files\Oracle\VirtualBox>VBoxManage -v
5.1.10r112026

c:\Program Files\Oracle\VirtualBox>VBoxManage.exe hostonlyif create
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

comment:27 Changed 6 months ago by AsadZaidi

Same issue still exists on 5.1.21:

C:\Program Files\Oracle\VirtualBox>VBoxManage.exe -v 5.1.21r115029

C:\Program Files\Oracle\VirtualBox>VBoxManage.exe hostonlyif create 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 94 of file VBoxManageHostonly.cpp

comment:28 Changed 6 months ago by Lillian

on 5.1.22 have this error:

...eting host-only interface: VirtualBox Host-Only Ethernet Adapter ' could not be foundr: The host network interface named 'VirtualBox Host-Only Ethernet Adapter VBoxManage.exe: error: Details: code E_INVALIDARG (0x80070057), component HostWrap, interface IHost, callee IUnknown VBoxManage.exe: error: Context: "FindHostNetworkInterfaceByName(Bstr(pszName).raw(), hif.asOutParam())" at line 139 of file VBoxManageHostonly.cpp " was not removed. Aborting...x Host-Only Ethernet Adapter

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use