No Host-only network at win10

Discussions related to using VirtualBox on Windows hosts.
Post Reply
x9854
Posts: 2
Joined: 18. Jun 2017, 14:27

No Host-only network at win10

Post by x9854 »

hi all!

today im install latest VBox and in network connections im not see Host-only interface @_@
then i try to create new i got an arror:

Code: Select all

Failed to create virtual host network adapter.
Querying NetCfgInstanceId failed (0x00000002).

err code: E_FAIL (0x80004005)
component: HostNetworkInterfaceWrap
interface: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}
VBox intalled with admin rules and started with too.
UAC is disabled.

I tried to reinstall VBox - not helped.

Plz help me :!:
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: No Host-only network at win10

Post by scottgus1 »

x9854 wrote:VBox intalled with admin rules
Let's define this a bit more carefully: to install Virtualbox properly you must right-click the Virtualbox installer program and choose "Run As Administrator" from the right-click menu, even if your account is an administrator account. (Note that right-click-Run-As-Administrator is not log-off-log-back-on-as-Administrator-double-click, and it is not I'm-already-an-Administrator-so-I-don't-have-to. Running the installer with a usual double-click under an Admin account will still not give you the necessary permissions.)

Please uninstall once again, then reboot, then re-run the installer using the above recommended method. Be sure that when you are running the installer you have all the options turned on. Then if you still don't have a Host-Only adapter, please post back.
x9854
Posts: 2
Joined: 18. Jun 2017, 14:27

Re: No Host-only network at win10

Post by x9854 »

hmmm... strange but its work, but after 2 reinstals (in ur instructions)

TYWM
Alex Matei
Posts: 2
Joined: 28. Oct 2017, 11:14

Re: No Host-only network at win10

Post by Alex Matei »

Hi,

I am using Windows 10 Home Edition, 64bit , version 1709 build 16299.19 Fall Creators Update, I upgraded this weekend.

I uninstalled VirtualBox completely and installed as indicated (right-click, run-As-Administrator on VirtualBox-5.1.28-117968-Win.exe)

1. During installation no VirtualBox Host-Only Network adapter is created in Control Panel - Network Connections. Is that normal ?
(see the attached image please)

2. When I try to create manually following File - Preferences - Network - Host only Networks tab, click the + button, after waiting a while I get this error:

Querying NetCfgInstanceId failed (0x00000002).
Result Code: E_FAIL (0x80004005)
Component: HostNetworkInterfaceWrap
Interface: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}

What can I do ?

When I look in "C:\Users\Alex\.VirtualBox\VBoxSVC.log" I see

VirtualBox COM Server 5.1.28 r117968 win.amd64 (Sep 13 2017 10:02:48) release log
00:00:00.000000 main Log opened 2017-10-28T09:22:02.919412400Z
00:00:00.000000 main Build Type: release
00:00:00.000000 main OS Product: Windows 10
00:00:00.000000 main OS Release: 10.0.16299
00:00:00.000000 main OS Service Pack:
00:00:00.046857 main DMI Product Name: All Series
00:00:00.062470 main DMI Product Version: System Version
00:00:00.062470 main Host RAM: 4001MB (3.9GB) total, 1884MB available
00:00:00.062470 main Executable: D:\Programe\Oracle\VirtualBox\VBoxSVC.exe
00:00:00.062470 main Process ID: 8824
00:00:00.062470 main Package type: WINDOWS_64BITS_GENERIC
00:00:00.062470 VirtualBox: object creation starts
00:00:00.093774 Home directory: 'C:\Users\Cristian\.VirtualBox'
00:00:00.093774 Installed Drivers:
00:00:00.093774 C:\WINDOWS\system32\DRIVERS\VBoxDrv.sys (Version: 5.1.28.17968)
00:00:00.093774 C:\WINDOWS\system32\DRIVERS\VBoxUSBMon.sys (Version: 5.1.28.17968)
00:00:00.093774 C:\WINDOWS\system32\DRIVERS\VBoxNetLwf.sys (Version: 5.1.28.17968)
00:00:00.388828 HostDnsMonitor: old information
00:00:00.388828 no server entries
00:00:00.388828 no domain set
00:00:00.388828 no search string entries
00:00:00.388828 HostDnsMonitor: new information
00:00:00.388828 server 1: 192.168.0.1
00:00:00.388828 no domain set
00:00:00.388828 no search string entries
00:00:00.389328 HostDnsMonitorProxy::notify
00:00:00.436485 VD: VDInit finished
00:00:00.436485 VirtualBox: object created
00:01:47.488023 SVCHelper ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={455f8c45-44a0-a470-ba20-27890b96dba9} aComponent={HostNetworkInterfaceWrap} aText={Querying NetCfgInstanceId failed (0x00000002)}, preserve=false aResultDetail=0

The same error occurs if I try the latest installation kit VirtualBox-5.2.0-118431-Win.exe

This time I I try to create manually following File - Preferences - Host Network Manager, click the Create + button, after waiting a while I get the same error as above.
Attachments
HostOnlyNetwork.jpg
HostOnlyNetwork.jpg (18.38 KiB) Viewed 20758 times
KaceyBR
Posts: 3
Joined: 6. Nov 2017, 23:56

Re: No Host-only network at win10

Post by KaceyBR »

I'm experiencing the same issue as Alex. Any help would be greatly appreciated, since VirtualBox is now unusable on a number of Windows 10 machines in my office. If there's additional information I can provide to help please let me know.

My Machine: Windows 10 Enterprise, 64 bit, ver 1607 OS Build 14393.1770

Attempted to install VirtualBox-5.2.0-118431. Completely uninstalled a previous version, and rebooted PC. After reboot, ran the installer as Administrator. No error is reported during installation, but no network adapter is generated. Trying to create one from the (administrator) command line produces the following:

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


VBoxSVCLog reports the following:

(From install)
00:01:16.822328 SVCHelper ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={455f8c45-44a0-a470-ba20-27890b96dba9} aComponent={HostNetworkInterfaceWrap} aText={Querying NetCfgInstanceId failed (0x00000002)}, preserve=false aResultDetail=0

(From hostonlyif create command)
00:01:21.838084 main VirtualBox: object deletion starts
00:01:21.843054 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
00:01:21.844062 main VirtualBox: object deleted
BillG
Volunteer
Posts: 5102
Joined: 19. Sep 2009, 04:44
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows 10,7 and earlier
Location: Sydney, Australia

Re: No Host-only network at win10

Post by BillG »

That sounds rather odd. I have no trouble with host only adapters with Windows 10 and VirtualBox 5.2.0.

VirtualBox will create a host only adapter by default when it is installed. (If the host is Windows you can see the adapter in network and sharing center). This can be prevented during the install process if desired. Whether you do this or not, you can add a host only adapter from the VirtualBox Manager screen. Select Global Tools in the top right of the window. Then select Host Network Manager and click Create.

If this does not work for you (even after a restart of the host), I would try a reinstall of VirtualBox.
Bill
KaceyBR
Posts: 3
Joined: 6. Nov 2017, 23:56

Re: No Host-only network at win10

Post by KaceyBR »

Bill,

Thank you for the reply. Unfortunately the problem repeats after several re-installation attempts. I've gone through multiple iterations of doing a full uninstall, reboot, fresh installation (with Run as Administrator) with the same results. I've also attempted adding the extension pack and then running the add host-only adapter operation from the command line and the GUI, but both produces the errors above.

I've been digging through Symantec and EMET logs to see if anything suggests they're blocking VBox from creating the adapter. So far I've seen nothing, but I can't rule out that a Windows setting or program is causing it. The only thing I've seen are entries in the Windows System log (via Event Viewer) with a message that says the following whenever I try adding the host-only adapter:
Driver Management has concluded the process to add Service VBoxNetAdp for Device Instance ID ROOT\NET\0001 with the following status: 0.
Are there additional steps that I can take on Windows 10 during the uninstall to completely remove any old drivers or other artifacts that may be causing conflicts? I've seen previous posts about deleting folders within AppData for example but that folder isn't present after Win7. Thanks in advance!
KaceyBR
Posts: 3
Joined: 6. Nov 2017, 23:56

Re: No Host-only network at win10

Post by KaceyBR »

Nevermind, I have found a fix I believe to my issue. Performing File->Reset Warnings seems to fix the issue and allows VB to create the host-only adapter. Thanks anyways, I hope someone else is helped by this.
BillG
Volunteer
Posts: 5102
Joined: 19. Sep 2009, 04:44
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows 10,7 and earlier
Location: Sydney, Australia

Re: No Host-only network at win10

Post by BillG »

Where did you reset warnings? in Windows, in VirtualBox or in Symantec?
Bill
Post Reply