virtualbox.org

I've installed Virtual Box 6.1.10 as administrator on Windows 10. The installation process is not creating a VirtualBox Host-Only Ethernet Adapter. The only error i'm finding in the logs (VBoxSVC.log) is "00:01:00.629591 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={d0a0163f-e254-4e5b-a1f2-011cf991c38d} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0". Not sure if this error is directly related to my issue or not.

Thanks

Try rebooting your host so no Virtualbox processes are running, then go to your host's network adapters, where you can right-click on them and set properties or disable/enable them. Try disabling the Host-Only adapters then re-enabling them.

If that doesn't get your guest going, run this command in the host's command prompt, and list the command output as text here on the forum:

CD "C:\Program Files\Oracle\VirtualBox"
vboxmanage list hostonlyifs
vboxmanage list dhcpservers

I only show one host network adapter, "Ethernet adapter Ethernet". The VB installation process didn't create the Host-Only adapter as it normally does or has done in the past for prior installations.

Listed below is the output from vboxmanage list hostonlyifs and vboxmanage list dhcpservers.

C:\Program Files\Oracle\VirtualBox>vboxmanage list hostonlyifs

C:\Program Files\Oracle\VirtualBox>vboxmanage list dhcpservers
NetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter
Dhcpd IP: 192.168.56.100
LowerIPAddress: 192.168.56.101
UpperIPAddress: 192.168.56.254
NetworkMask: 255.255.255.0
Enabled: Yes
Global Configuration:
minLeaseTime: default
defaultLeaseTime: default
maxLeaseTime: default
Forced options: None
Suppressed opts.: None
1/legacy: 255.255.255.0
Groups: None
Individual Configs: None

OK, looks like you don't have a Host-Only adapter.

Run these commands in a command prompt:

cd "C:\Program Files\Oracle\Virtualbox"
vboxmanage dhcpserver remove --netname "HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter"

Go to the main Virtualbox window, File Menu, Host Network Manager. Make a new Host-Only network. Note that the IP address range may not be 192.168.56.###. If you want you can change the third octet from what it is to 56 in the Adapter and DHCP Server tabs, before you use the Host-Only network. (Be careful to not change the masks, leave them at 255.255.255.0)

Finally, attach your guest to the new Host-Only network.

Ran vboxmanage dhcpserver remove --netname "HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter". Then tried to create a Host Only Adapter but it failed with the following:

vboxmanage dhcpserver remove --netname "HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter"

Failed to create a host network interface.

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).

Please contact the product vendor!.

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

The issue has been resolved. The application bit9 was preventing the host-only and the bridged adapter from being installed correctly. The bit9 agent on this server was disable but somehow bit9 was still interfering with the pum deployment.

Sorry I missed your report back, but it's good you found the culprit! Glad you're back up and running.