VirtualBox Host-Only Ethernet Adapter install failed

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Xcheng
Posts: 2
Joined: 14. Jan 2024, 08:16

VirtualBox Host-Only Ethernet Adapter install failed

Post by Xcheng »

VirtualBox Host-Only Ethernet Adapter install failed

"VirtualBox Host-Only Ethernet Adapter"Cannot be installed correctly...

The computer above displays a normal Vbox network adapter
The computer below shows an abnormal Vbox network adapter with the word # 3.

Currently, there are issues with the use of virtual machines using the host only default network card, and manual modification of the network card configuration to VirtualBox Host Only Ethernet Adapter # 3 is required to function properly.

But some other software I use uses the Oracle VirtualBox module, which leads to fatal errors in other software.
Such as Huawei ENSP, H3C Cloud Lab, etc

install.log failed

Code: Select all

MSI (s) (10:94) [02:28:52:030]: Adding new sources is allowed.
MSI (s) (10:94) [02:28:52:030]: Set LastUsedSource to: C:\Users\Xcheng\AppData\Local\Temp\50xz2pfpjkqbs6j00y3z2q8a\.
MSI (s) (10:94) [02:28:52:034]: Set LastUsedType to: n.
MSI (s) (10:94) [02:28:52:034]: Set LastUsedIndex to: 1.
MSI (s) (10:94) [02:28:52:034]: Executing op: ActionStart(Name=ca_CreateHostOnlyInterfaceNDIS6,,)
MSI (s) (10:94) [02:28:52:034]: Executing op: CustomActionSchedule(Action=ca_CreateHostOnlyInterfaceNDIS6,ActionType=3073,Source=BinaryData,Target=Ndis6CreateHostOnlyInterface,CustomActionData=C:\Program Files\Oracle\VirtualBox\drivers\network\netadp6\)
MSI (s) (10:80) [02:28:52:034]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI8869.tmp, Entrypoint: Ndis6CreateHostOnlyInterface
CreateHostOnlyInterface: Creating host-only interface
CreateHostOnlyInterface: NetAdpDir property = C:\Program Files\Oracle\VirtualBox\drivers\network\netadp6\
CreateHostOnlyInterface: Resulting INF path = C:\Program Files\Oracle\VirtualBox\drivers\network\netadp6\VBoxNetAdp6.inf
CreateHostOnlyInterface: Calling VBoxDrvCfgInfInstall(C:\Program Files\Oracle\VirtualBox\drivers\network\netadp6\VBoxNetAdp6.inf)
CreateHostOnlyInterface: VBoxDrvCfgInfInstall returns 0x0
CreateHostOnlyInterface: VBoxNetCfgWinUpdateHostOnlyNetworkInterface failed, hr = 0xe000020b
CreateHostOnlyInterface: calling VBoxNetCfgWinCreateHostOnlyNetworkInterface
setupapi.dev.log

Code: Select all

>>>  [SetupUninstallOEMInf - oem22.inf]
>>>  Section start 2024/01/13 01:42:44.338
      cmd: C:\Windows\System32\MsiExec.exe -Embedding 2D40284240DA65196D8AF22825BF7186 E Global\MSI0000
     inf: Flags: 0x00000001
     dvs: {DrvSetupUninstallDriver - C:\WINDOWS\INF\oem22.inf}
     dvs:      Flags: 0x10000001
     dvs:      {Driver Setup Delete Driver Package: oem22.inf} 01:42:44.338
!    utl:           INF INF 'oem22.inf' still in use by device 'ROOT\NET\0000'.
!    utl:           Primary INF 'oem22.inf' is still in use by devices.
!    dvs:           Forcing uninstall of INF 'oem22.inf' still in use by devices.
     utl:           Invalidated INF 'oem22.inf' on device 'ROOT\NET\0000'.
     ump:           Delete flags: 0x00010002
     pol:           {Driver package policy check} 01:42:44.511
     pol:           {Driver package policy check - exit(0x00000000)} 01:42:44.511
     sto:           {Unstage Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\vboxnetadp6.inf_amd64_bde29c361ad265bb\vboxnetadp6.inf} 01:42:44.526
     inf:                Provider       = Oracle Corporation
     inf:                Class GUID     = {4d36e972-e325-11ce-bfc1-08002be10318}
     inf:                Driver Version = 07/09/2020,5.2.44.0
     inf:                Catalog File   = VBoxNetAdp6.cat
     inf:                Version Flags  = 0x00000001
     sto:                {Core Driver Package Delete: vboxnetadp6.inf_amd64_bde29c361ad265bb} 01:42:44.526
     sto:                     {DRIVERSTORE DELETE BEGIN} 01:42:44.526
     sto:                     {DRIVERSTORE DELETE BEGIN: exit(0x00000000)} 01:42:44.526
     sto:                     {Unconfigure Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\vboxnetadp6.inf_amd64_bde29c361ad265bb\vboxnetadp6.inf}
     inf:                          Class GUID     = {4d36e972-e325-11ce-bfc1-08002be10318}
     inf:                          Class Options  = Configurable
     inf:                          {Unconfigure Driver: VirtualBox Host-Only Ethernet Adapter}
     inf:                               Section Name = VBoxNetAdp6.ndi
     inf:                               {Add Service: VBoxNetAdp}
     inf:                                    Service 'VBoxNetAdp' remains with owner '!vboxnetadp6.inf_amd64_bde29c361ad265bb'.
     inf:                                    Service 'VBoxNetAdp' still in use by 1 source.
     inf:                               {Add Service: exit(0x00000000)}
     inf:                               File 'C:\WINDOWS\System32\drivers\VBoxNetAdp6.sys' remains with owner '!vboxnetadp6.inf_amd64_bde29c361ad265bb'.
     inf:                               File 'C:\WINDOWS\System32\drivers\VBoxNetAdp6.sys' still in use by 2 sources.
     inf:                          {Unconfigure Driver: exit(0x00000000)}
     flq:                          {FILE_QUEUE_COMMIT} 01:42:44.542
     flq:                          {FILE_QUEUE_COMMIT - exit(0x00000000)} 01:42:44.542
     sto:                     {Unconfigure Driver Package: exit(0x00000000)}
     idb:                     {Unpublish Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\vboxnetadp6.inf_amd64_bde29c361ad265bb\vboxnetadp6.inf} 01:42:44.542
     idb:                          Clearing active driver package 'vboxnetadp6.inf_amd64_bde29c361ad265bb'.
     cpy:                          Unpublished 'oem22.inf'.
!    cpy:                          Unable to delete 'C:\WINDOWS\inf\oem22.pnf'. Error = 0x00000020
     idb:                          Deindexed 2 device IDs for 'vboxnetadp6.inf_amd64_bde29c361ad265bb'.
     sto:                          Flushed driver database node 'DRIVERS'. Time = 0 ms
     sto:                          Flushed driver database node 'SYSTEM'. Time = 15 ms
     idb:                     {Unpublish Driver Package: exit(0x00000000)} 01:42:44.573
     idb:                     {Unregister Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\vboxnetadp6.inf_amd64_bde29c361ad265bb\vboxnetadp6.inf} 01:42:44.573
     idb:                          Unregistered driver package 'vboxnetadp6.inf_amd64_bde29c361ad265bb' from 'oem22.inf'.
     idb:                          Deleted driver package object 'vboxnetadp6.inf_amd64_bde29c361ad265bb' from DRIVERS database node.
     idb:                          Deleted driver INF file object 'oem22.inf' from DRIVERS database node.
     idb:                     {Unregister Driver Package: exit(0x00000000)} 01:42:44.573
     cpy:                     {Delete Directory: C:\WINDOWS\System32\DriverStore\FileRepository\vboxnetadp6.inf_amd64_bde29c361ad265bb} 01:42:44.573
     cpy:                     {Delete Directory: exit(0x00000000)} 01:42:44.573
     sto:                     {DRIVERSTORE DELETE END} 01:42:44.573
     sig:                          Uninstalled catalog 'oem22.cat'.
     sto:                     {DRIVERSTORE DELETE END: exit(0x00000000)} 01:42:44.589
     sto:                {Core Driver Package Delete: exit(0x00000000)} 01:42:44.589
     sto:           {Unstage Driver Package: exit(0x00000000)} 01:42:44.589
     dvs:      {Driver Setup Delete Driver Package - exit (0x00000000)} 01:42:44.589
     dvs: {DrvSetupUninstallDriver - exit(00000000)}
<<<  Section end 2024/01/13 01:42:44.589
<<<  [Exit status: SUCCESS]
setupapi.dev.log 2

Code: Select all

>>>  [Delete Device - ROOT\NET\0002]
>>>  Section start 2024/01/13 01:53:32.055
      cmd: "C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe" /Helper VirtualBox\SVCHelper\{c1a6d192-c6ec-4ef7-927e-407405138aa2}
     dvi: Query-and-Remove succeeded
<<<  Section end 2024/01/13 01:53:32.184
<<<  [Exit status: SUCCESS]


>>>  [Configure Driver Package - c:\windows\system32\driverstore\filerepository\vboxnetadp6.inf_amd64_6cf9a3795b72510a\vboxnetadp6.inf]
>>>  Section start 2024/01/13 01:53:36.241
      cmd: "C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe" /Helper VirtualBox\SVCHelper\{9da788c1-d010-4d72-a569-c01e8729e227}
     sto: Source Filter  = VBoxNetAdp6.ndi
     sto: Target Filter  = ROOT\NET\0001
     inf: Class GUID     = {4d36e972-e325-11ce-bfc1-08002be10318}
     inf: Class Options  = Configurable
!!!  idb: Failed to open driver package object 'vboxnetadp6.inf_amd64_6cf9a3795b72510a'. Error = 0x00000005
<<<  Section end 2024/01/13 01:53:36.283
<<<  [Exit status: FAILURE(0x00000005)]


>>>  [Restart Device - ROOT\NET\0001]
>>>  Section start 2024/01/13 01:53:36.292
      cmd: "C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe" /Helper VirtualBox\SVCHelper\{9da788c1-d010-4d72-a569-c01e8729e227}
     dvi: Device Status: 0x01802001
     dvi: Install Device: Starting device 'ROOT\NET\0001'. 01:53:36.306
     dvi: Install Device: Starting device completed. 01:53:36.320
!    dvi: Device pending start: Device has problem: 0x38 (CM_PROB_NEED_CLASS_CONFIG), problem status: 0x00000000.
<<<  Section end 2024/01/13 01:53:36.339
<<<  [Exit status: SUCCESS]


>>>  [Set network component display name]
>>>  Section start 2024/01/13 01:53:36.857
      cmd: "C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe" /Helper VirtualBox\SVCHelper\{9da788c1-d010-4d72-a569-c01e8729e227}
     inf: Old name: VirtualBox Host-Only Ethernet Adapter #3
     inf: New name: VirtualBox Host-Only Ethernet Adapter #2
     dvi: Committing changes to the binding graph
<<<  Section end 2024/01/13 01:53:37.139
<<<  [Exit status: SUCCESS]
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: VirtualBox Host-Only Ethernet Adapter install failed

Post by scottgus1 »

Xcheng wrote: 14. Jan 2024, 09:32 abnormal Vbox network adapter with the word # 3.

Currently, there are issues with the use of virtual machines using the host only default network card, and manual modification of the network card configuration to VirtualBox Host Only Ethernet Adapter # 3 is required to function properly.
This is Windows behavior, when a major Windows Update occurs, Windows sometimes renames & renumbers its attached network adapters. It's not caused by Virtualbox.

I'm not sure how to fix it though. One thing I would try is to take note of the settings for Host-Only adapters & networks, then delete all Host-Only adapters & networks, then web-search how to delete missing network adapters from Windows (these are where the #'s come from) then put back the Host-Only adapters and networks.
Xcheng
Posts: 2
Joined: 14. Jan 2024, 08:16

Re: VirtualBox Host-Only Ethernet Adapter install failed

Post by Xcheng »

scottgus1 wrote: 14. Jan 2024, 19:44
Xcheng wrote: 14. Jan 2024, 09:32 abnormal Vbox network adapter with the word # 3.

Currently, there are issues with the use of virtual machines using the host only default network card, and manual modification of the network card configuration to VirtualBox Host Only Ethernet Adapter # 3 is required to function properly.
This is Windows behavior, when a major Windows Update occurs, Windows sometimes renames & renumbers its attached network adapters. It's not caused by Virtualbox.

I'm not sure how to fix it though. One thing I would try is to take note of the settings for Host-Only adapters & networks, then delete all Host-Only adapters & networks, then web-search how to delete missing network adapters from Windows (these are where the #'s come from) then put back the Host-Only adapters and networks.
Thanks
I've tried contacting Microsoft for help.
Post Reply