VERR_SUPDRV_COMPONENT_NOT_FOUND

[TroyH]

I wanted to share a fix that took 2 days of Googling to find. So you've been upgrading VB for a while on your Windows host and all of a sudden you see this error (VERR_SUPDRV_COMPONENT_NOT_FOUND) appear when you go to launch one of your VB machines. This error gets thrown because your machine is using either the built-in VB Host-Only network adapter OR the Bridged Adapter, and the VB installation failed to deploy the adapter drivers .. at least that was the case in my host environment (Win7 Ent x64).

The first thing to look at is the driver install log found here: (C:\Windows\inf\setupapi.app.log). My logs contained this ERROR:

>>> [DIF_INSTALLDEVICE - ROOT\MFE_FIREHKMP\0009]
>>> Section start 2014/01/02 16:32:52.778
cmd: C:\Windows\system32\svchost.exe -k netsvcs
cci: NdisCoinst: Guid of the adapter is {D20A4512-3299-4E64-BEBF-64A163C0B940}
cci: NdisCoinst: IfType 1, Characteristics 0x29, IsIrdaDevice 0, PhysicalMediaType -1, MediaType -1, IsBridge 0, FoundGuidInDownlevel 0, EnableDhcp 2
cci: NdisCoinst: Connection name is Local Area Connection* 1045
!!! cci: NdisCoinst: NcipAllocateNetLuidIndex failed with error 0x5aa
!!! dvi: CoInstaller 1: failed(0x000005aa)!
!!! dvi: Error 1450: Insufficient system resources exist to complete the requested service.
<<< Section end 2014/01/02 16:33:11.108
<<< [Exit status: FAILURE(0x000005aa)]

The install had an issue with assigning an index (NcipAllocateNetLuidIndex), and threw the error "Insufficient system resources exist to complete the requested service." Now unless you are familiar with driver installations, especially network drivers, you would not know to go digging around "IfTypes" .. the one in question above is "1", which is found in the registry here:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\NDIS\IfTypes\1]
"IfType"=dword:00000001
"IfUsedNetLuidIndices"=hex:ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,\
ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,\
ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,\
ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,\
ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,\
ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

You'll notice the IfUsedNetLuidIndices value is either corrupted or full .. this is what was causing my driver installation to fail. What it should look like is this:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\NDIS\IfTypes\1]
"IfType"=dword:00000001
"IfUsedNetLuidIndices"=hex:ff,ff,ff,ff,ff,3f,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,08,00,00,00,00,00,00,00,\
00,00,00,00,00,00,00,00,00,00,00

To fix this, you need something to modify the binary entry in the registry.

Once this is reset, I uninstalled VB, rebooted, then proceeded to re-install it.

[TroyH]

Here's the thread that contained a tool that resets the IfTypes https://supportforums.cisco.com/thread/2187313

Here's the tool https://skydrive.live.com/?cid=86bdd34d ... PB4O4uVxek.