Unable to create Host Only Network Adaptor

[vsian]

Hi, I am trying to create Host Only Network Adaptor in Virtualbox, but encountered the error the error "Querying NetCfgInstanceId failed (0x00000002)." .

Have tried to reinstall but still encountering the same issue. This is a work laptop, so not able to disable antivirus (Windows Defender).

Virtualbox version: 6.1.26 with extension pack
Winver: 21H1 (Build 19043.1110)

Any idea what else can I do to troubleshoot this issue?

[mpack]

AV is not relevant to this problem.

You had an option during VirtualBox installation to install the "Host Only" virtual network card. I'm guessing you either turned that option off, or you didn't have sufficient admin rights to install drivers.

[cricpy]

I have the same problem.
I try to create the host-only adapter and this is the message:
└─$ VBoxManage.exe hostonlyif create
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-6.1\src\VBox\Main\src-server\HostNetworkInterfaceImpl.cpp' (76) in long __cdecl HostNetworkInterface::init(class com::Utf8Str,class com::Utf8Str,class com::Guid,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0046).
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 95 of file VBoxManageHostonly.cpp

I try re install VBox, check my PC with scf /scannow and nothing...

Any suggestion?

[vsian]

AV is not relevant to this problem.

You had an option during VirtualBox installation to install the "Host Only" virtual network card. I'm guessing you either turned that option off, or you didn't have sufficient admin rights to install drivers.

This is the settings for the installation:

Virtualbox installation.png (14.85 KiB) Viewed 8085 times

When I tried with my account with Network Operator Rights to create the Host Only Adaptor, I encountered the following:

Error - User with Network Operator.png (11.58 KiB) Viewed 8085 times

When I used an account with local admin rights, I encountered the following:

Error - User with Network Operator.png (11.58 KiB) Viewed 8085 times

Is there a way to install the Virtualbox Host Only Adaptor drivers by itself? As the local admin account does have the rights to install drivers.

[fth0]

Is there a way to install the Virtualbox Host Only Adaptor drivers by itself?

In the Windows Explorer, right click on the following file and select Install:

Code: Select all

C:\Program Files\Oracle\VirtualBox\drivers\network\netadp6\VBoxNetAdp6.inf

[cricpy]

I tried to install manually as indicated, but it doesn't work either. In device manager it shows the following error (attached image)

VBox-Ndis.png (13.81 KiB) Viewed 8057 times

In the device properties you can see the following:
El dispositivo ROOT\NET\0000 tuvo un problema al iniciarse.
Nombre del controlador: oem4.inf
GUID de clase: {4d36e972-e325-11ce-bfc1-08002be10318}
Servicio: VBoxNetAdp
Filtros inferiores:
Filtros superiores:
Problema: 0x27
Estado del problema: 0xC0000045

I have tried various alternatives and none seem to work.

At the moment it only works in NAT mode

Thank

[jorgensen]

This is a work laptop, so not able to disable antivirus (Windows Defender).

Properly you are not allowed to make changes to the network.

[vsian]

The issue managed to resolve after updating my chipset drivers. Not sure how that resolved the issue, but the Virtualbox Host Only adaptor appeared after that.

[mpack]

The fact that you're up and running is good news. However...

The issue managed to resolve after updating my chipset drivers

Chipset drivers for what? The Host-Only network card is entirely simulated, it has nothing to do with any physical cards in the host. There are no chipsets to need drivers for.

If you were talking about bridged networking then this would make more sense. Personally I suspect that a host reset might have made the real difference.

[cricpy]

In my case you can "fix" by installing version 6.1.20
For now I do not plan to update.

Greetings

[mpack]

Yes, burying your head in the sand instead of understanding the problem - always a good way to go.

[cricpy]

I don't think that is burying your head in the ground. But not all of us have that spirit of looking for a solution to everything ... This is not something important to me, so I don't want to invest too much time either.

[vsian]

The fact that you're up and running is good news. However...

The issue managed to resolve after updating my chipset drivers

Chipset drivers for what? The Host-Only network card is entirely simulated, it has nothing to do with any physical cards in the host. There are no chipsets to need drivers for.

If you were talking about bridged networking then this would make more sense. Personally I suspect that a host reset might have made the real difference.

For my case, I was using a Dell 5310 laptop. I had installed the following chipset drivers and it somehow worked after the installation (+ reboot).

https://www.dell.com/support/home/en-sg ... 310-laptop

[Martin]

Most probably it was just the (full) reboot which did resolve your problem.

[vsian]

Most probably it was just the (full) reboot which did resolve your problem.

The laptop had been rebooted multiple times prior to that installation. And the issue resolved after installing the chipset software for 2 other dell laptops. So yeah.