Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when installing

OSR_Community_UserOSR_Community_User Member Posts: 110,218
Hey al,

We have a customer who is experiencing problems installing our NDIS miniport
driver. He's getting error 1450 (ERROR_NO_SYSTEM_RESOURCES), but states he
has plenty of disk space, etc. available. Looking through the setupapi.log
tells me two things:

1. There seem to be some certificate issues, but I'm seeing similar
errors/warnings on my machine, so my guess is that they're perhaps related
to WHQL (our driver isn't WHQL-certified).

2. The following piece of the log worries me:

ndv: Installing device...
dvi: {DIF_INSTALLDEVICE} 22:46:03.704
dvi: CoInstaller 1: Enter 22:46:03.705
cci: NdisCoinst: NetCfgInstanceId does not exist
cci: NdisCoinst: Guid of the adapter is
{C88CF875-4F7E-465E-BD02-DD2639E1A43A}
inf: Opened PNF: 'C:\Windows\INF\oem26.inf'
([strings])
cci: NdisCoinst: IfType from registry is 1
cci: NdisCoinst: IfType 1, Characteristics 0x1,
IsIrdaDevice 0, PhysicalMediaType -1, MediaType -1, IsBridge 0,
FoundGuidInDownlevel 0, EnableDhcp 2
cci: NdisCoinst: Connection name is Local Area
Connection 3
cci: NdisCoinst: NetLuidIndex does not exist
!!! cci: NdisCoinst: NcipAllocateNetLuidIndex failed
with error 0x5aa
!!! dvi: CoInstaller 1: failed(0x000005aa)!
!!! dvi: Error 1450: Insufficient system resources exist to
complete the requested service.
dvi: {DIF_INSTALLDEVICE - exit(0x000005aa)} 22:46:03.767
!!! ndv: Error(000005aa) installing device!
ndv: Device install status=0x000005aa
ndv: Performing device install final cleanup...
! ndv: Queueing up error report since device installation
failed...

I'm hoping some trained eyes here from NTDEV might see something in the log
that I don't. I've included the full setupapi.log below.

Thanks,
Soren

[Device Install Log]
OS Version = 6.1.7600
Service Pack = 0.0
Suite = 0x0100
ProductType = 1
Architecture = amd64

[BeginLog]



>>> [Device Install (UpdateDriverForPlugAndPlayDevices) - root\LbAdapter]
>>> Section start 2010/05/13 22:45:59.836
cmd: "C:\Program Files\Echobit\LAN Bridger\installer_helper_x64.exe"
install "C:\Program Files\Echobit\LAN Bridger\Driver\netLB_x64.inf"
"root\LbAdapter"
dvi: Set selected driver complete.
dvi: {Build Driver List} 22:46:00.748
cpy: Policy is set to make all digital signatures equal.
dvi: Processing a single INF: 'c:\program files\echobit\lan
bridger\driver\netlb_x64.inf'
inf: Opened INF: 'c:\program files\echobit\lan
bridger\driver\netlb_x64.inf' ([strings])
sig: {_VERIFY_FILE_SIGNATURE} 22:46:00.755
sig: Key = netlb_x64.inf
sig: FilePath = c:\program files\echobit\lan
bridger\driver\netlb_x64.inf
sig: Catalog = c:\program files\echobit\lan
bridger\driver\netLB_x64.cat
flq: {SPFILENOTIFY_CABINETINFO}
flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)}
flq: {SPFILENOTIFY_FILEEXTRACTED}
flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)}
! sig: Verifying file against specific (valid) catalog failed!
(0x800b0109)
! sig: Error 0x800b0109: A certificate chain processed, but
terminated in a root certificate which is not trusted by the trust provider.
sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 22:46:01.061
sig: {_VERIFY_FILE_SIGNATURE} 22:46:01.062
sig: Key = netlb_x64.inf
sig: FilePath = c:\program files\echobit\lan
bridger\driver\netlb_x64.inf
sig: Catalog = c:\program files\echobit\lan
bridger\driver\netLB_x64.cat
sig: Success: File is signed in Authenticode(tm) catalog.
sig: Error 0xe0000242: The publisher of an Authenticode(tm)
signed catalog has not yet been established as trusted.
sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 22:46:01.099
dvi: Created Driver Node:
dvi: HardwareID - root\LbAdapter
dvi: InfName - c:\program files\echobit\lan
bridger\driver\netlb_x64.inf
dvi: DevDesc - LAN Bridger Virtual Ethernet Adapter
dvi: DrvDesc - LAN Bridger Virtual Ethernet Adapter
dvi: Provider - Echobit LLC
dvi: Mfg - Echobit LLC
dvi: ModelsSec - Lb.NTamd64
dvi: InstallSec - LbAdapter.ndi
dvi: ActualSec - LbAdapter.ndi
dvi: Rank - 0x00ff0000
dvi: Signer - Echobit, LLC
dvi: Signer Score - Authenticode
dvi: DrvDate - 11/01/2008
dvi: Version - 6.0.0.1
dvi: {Build Driver List - exit(0x00000000)} 22:46:01.125
dvi: {DIF_SELECTBESTCOMPATDRV} 22:46:01.126
dvi: Using exported function 'NetClassInstaller' in module
'C:\Windows\system32\NetCfgx.dll'.
dvi: Class installer == NetCfgx.dll,NetClassInstaller
dvi: Using exported function 'NciDeviceInstall' in module
'C:\Windows\system32\nci.dll'.
dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
dvi: Using exported function 'WlanDeviceClassCoInstaller' in
module 'C:\Windows\system32\wlaninst.dll'.
dvi: CoInstaller 2 == wlaninst.dll,WlanDeviceClassCoInstaller
dvi: Using exported function 'WwanDeviceClassCoInstaller' in
module 'C:\Windows\system32\wwaninst.dll'.
dvi: CoInstaller 3 == wwaninst.dll,WwanDeviceClassCoInstaller
dvi: CoInstaller 1: Enter 22:46:01.142
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 22:46:01.145
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 22:46:01.149
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 22:46:01.152
dvi: Class installer: Exit
dvi: Default installer: Enter 22:46:01.155
dvi: {Select Best Driver}
dvi: Selected driver installs from section
[LbAdapter.ndi] in 'c:\program files\echobit\lan
bridger\driver\netlb_x64.inf'.
dvi: Set selected driver complete.
dvi: Selected:
dvi: Description - [LAN Bridger Virtual Ethernet
Adapter]
dvi: InfFile - [c:\program files\echobit\lan
bridger\driver\netlb_x64.inf]
dvi: Section - [LbAdapter.ndi]
dvi: Signer - [Echobit, LLC]
dvi: Rank - [0x00ff0000]
dvi: {Select Best Driver - exit(0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 22:46:01.171
inf: {SetupCopyOEMInf: c:\program files\echobit\lan
bridger\driver\netlb_x64.inf} 22:46:01.172
! inf: Package was already in store: skipping Driver Store add
inf: {SetupCopyOEMInf exit (0x00000000)} 22:46:01.852
inf: Opened PNF:
'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
sig: {_VERIFY_FILE_SIGNATURE} 22:46:01.861
sig: Key = netlb_x64.inf
sig: FilePath =
C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
1ce5dbcf7c93cc8\netlb_x64.inf
sig: Catalog =
C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
1ce5dbcf7c93cc8\netLB_x64.cat
! sig: Verifying file against specific (valid) catalog failed!
(0x800b0109)
! sig: Error 0x800b0109: A certificate chain processed, but
terminated in a root certificate which is not trusted by the trust provider.
sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 22:46:01.881
sig: {_VERIFY_FILE_SIGNATURE} 22:46:01.882
sig: Key = netlb_x64.inf
sig: FilePath =
C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
1ce5dbcf7c93cc8\netlb_x64.inf
sig: Catalog =
C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
1ce5dbcf7c93cc8\netLB_x64.cat
sig: Success: File is signed in Authenticode(tm) catalog.
sig: Error 0xe0000242: The publisher of an Authenticode(tm) signed
catalog has not yet been established as trusted.
sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 22:46:01.919
dvi: Selected driver installs from section [LbAdapter.ndi] in
'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
41ce5dbcf7c93cc8\netlb_x64.inf'.
dvi: Set selected driver complete.
dvi: {Plug and Play Service: Device Install for ROOT\NET\0000}
ump: Creating Install Process: DrvInst.exe 22:46:02.109
ndv: Infpath=C:\Windows\INF\oem26.inf
ndv:
DriverNodeName=netlb_x64.inf:Lb.NTamd64:LbAdapter.ndi:6.0.0.1:root\lbadapter
ndv:
DriverStorepath=C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf
_amd64_neutral_41ce5dbcf7c93cc8\netlb_x64.inf
ndv: Building driver list from driver node strong name...
inf: Opened PNF:
'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
sig: {_VERIFY_FILE_SIGNATURE} 22:46:02.559
sig: Key = netlb_x64.inf
sig: FilePath =
C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
1ce5dbcf7c93cc8\netlb_x64.inf
sig: Catalog =
C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
1ce5dbcf7c93cc8\netLB_x64.cat
flq: {SPFILENOTIFY_CABINETINFO}
flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)}
flq: {SPFILENOTIFY_FILEEXTRACTED}
flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)}
! sig: Verifying file against specific (valid) catalog failed!
(0x800b0109)
! sig: Error 0x800b0109: A certificate chain processed, but
terminated in a root certificate which is not trusted by the trust provider.
sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 22:46:02.648
sig: {_VERIFY_FILE_SIGNATURE} 22:46:02.649
sig: Key = netlb_x64.inf
sig: FilePath =
C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
1ce5dbcf7c93cc8\netlb_x64.inf
sig: Catalog =
C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
1ce5dbcf7c93cc8\netLB_x64.cat
sig: Success: File is signed in Authenticode(tm) catalog.
sig: Error 0xe0000242: The publisher of an Authenticode(tm)
signed catalog has not yet been established as trusted.
sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 22:46:02.686
dvi: Selected driver installs from section [LbAdapter.ndi] in
'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
41ce5dbcf7c93cc8\netlb_x64.inf'.
dvi: Set selected driver complete.
ndv: {Core Device Install} 22:46:02.691
inf: Opened PNF: 'C:\Windows\INF\oem26.inf' ([strings])
dvi: {DIF_ALLOW_INSTALL} 22:46:02.809
dvi: Using exported function 'NetClassInstaller' in
module 'C:\Windows\system32\NetCfgx.dll'.
dvi: Class installer == NetCfgx.dll,NetClassInstaller
dvi: Using exported function 'NciDeviceInstall' in
module 'C:\Windows\system32\nci.dll'.
dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
dvi: Using exported function
'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'.
dvi: CoInstaller 2 ==
wlaninst.dll,WlanDeviceClassCoInstaller
dvi: Using exported function
'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'.
dvi: CoInstaller 3 ==
wwaninst.dll,WwanDeviceClassCoInstaller
dvi: CoInstaller 1: Enter 22:46:02.830
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 22:46:02.833
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 22:46:02.835
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 22:46:02.839
inf: Opened PNF: 'C:\Windows\INF\oem26.inf'
([strings])
inf: AddReg=LbAdapter.Reg (oem26.inf line 33)
inf: AddReg=LbAdapter.Reg.Adapter.Params
(oem26.inf line 34)
dvi: Class installer: Exit
dvi: Default installer: Enter 22:46:02.917
dvi: Default installer: Exit
dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 22:46:02.920
ndv: Installing files...
dvi: {DIF_INSTALLDEVICEFILES} 22:46:02.924
dvi: CoInstaller 1: Enter 22:46:02.926
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 22:46:02.930
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 22:46:02.933
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 22:46:02.936
dvi: Class installer: Exit
dvi: Default installer: Enter 22:46:02.940
dvi: {Install FILES}
inf: Opened PNF:
'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
inf: {Install Inf Section [LbAdapter.ndi]}
inf: CopyFiles=LbAdapter.CopyFiles
(netlb_x64.inf line 35)
cpy: Open PnpLockdownPolicy: Err=2. This
is OK. Use LockDownPolicyDefault
flq: QueueSingleCopy...
flq: Inf :
'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
41ce5dbcf7c93cc8\netlb_x64.inf'
flq: SourceInf:
'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
41ce5dbcf7c93cc8\netlb_x64.inf'
flq: SourceSection: [sourcedisksfiles]
flq: Source root path based on SourceInf
flq: SourceRootPath:
'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
41ce5dbcf7c93cc8'
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000400
flq: {FILE_QUEUE_COPY}
flq: CopyStyle -
0x00000400
flq: SourceRootPath -
'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
41ce5dbcf7c93cc8'
flq: SourceFilename - 'lb.sys'
flq: TargetDirectory-
'C:\Windows\system32\DRIVERS'
flq: TargetFilename - 'lb.sys'
flq: SourceDesc - 'LAN
Bridger Virtual Ethernet Adapter Installation Disk'
flq: {FILE_QUEUE_COPY
exit(0x00000000)}
flq: {FILE_QUEUE_COPY exit(0x00000000)}
inf: {Install Inf Section [LbAdapter.ndi] exit
(0x00000000)}
dvi: Processing co-installer registration
section [LbAdapter.ndi.CoInstallers].
inf: {Install Inf Section
[LbAdapter.ndi.CoInstallers]}
inf: {Install Inf Section
[LbAdapter.ndi.CoInstallers] exit (0x00000000)}
dvi: Co-installers registered.
dvi: {Install INTERFACES}
dvi: Installing section
[LbAdapter.ndi.Interfaces]
dvi: {Install INTERFACES exit 00000000}
dvi: {Install FILES exit (0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 22:46:02.988
ndv: Pruning file queue...
dvi: {_SCAN_FILE_QUEUE}
flq: ScanQ flags=620
flq: SPQ_SCAN_PRUNE_COPY_QUEUE
flq: SPQ_SCAN_FILE_COMPARISON
flq: SPQ_SCAN_ACTIVATE_DRP
flq: ScanQ number of copy nodes=1
flq: File 'C:\Windows\system32\DRIVERS\lb.sys' pruned
from copy.
sig: Using catalog
'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem26.CA
T'.
flq: {SPFILENOTIFY_CABINETINFO}
flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)}
flq: {SPFILENOTIFY_FILEEXTRACTED}
flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)}
! sig: VerifyTrustFailed for
C:\Windows\system32\DRIVERS\lb.sys.
! sig: Error 0x800b0109: A certificate chain processed,
but terminated in a root certificate which is not trusted by the trust
provider.
cpy: DrpSetRegFileProt
'C:\Windows\system32\DRIVERS\lb.sys' Status=0 Class=OEM Legacy
flq: ScanQ action=200 DoPruning=32
flq: ScanQ end Validity flags=620 CopyNodes=0
dvi: {_SCAN_FILE_QUEUE exit(0, 0x00000000)}
ndv: Committing file queue...
flq: {_commit_file_queue}
flq: CommitQ DelNodes=0 RenNodes=0 CopyNodes=0
flq: CommitQ early exit: No nodes are queued
flq: {_commit_file_queue exit OK}
ndv: Registering CoInstallers...
dvi: {DIF_REGISTER_COINSTALLERS} 22:46:03.581
dvi: CoInstaller 1: Enter 22:46:03.583
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 22:46:03.586
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 22:46:03.589
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 22:46:03.591
dvi: Class installer: Exit
dvi: Default installer: Enter 22:46:03.594
inf: Opened PNF:
'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
inf: {Install Inf Section
[LbAdapter.ndi.CoInstallers]}
inf: {Install Inf Section
[LbAdapter.ndi.CoInstallers] exit (0x00000000)}
dvi: {DIF_DESTROYPRIVATEDATA} 22:46:03.645
dvi: CoInstaller 1: Enter 22:46:03.647
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 22:46:03.650
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 22:46:03.653
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 22:46:03.657
dvi: Class installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)}
22:46:03.661
dvi: Co-installers registered.
dvi: Default installer: Exit
dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)}
22:46:03.665
ndv: Installing interfaces...
dvi: {DIF_INSTALLINTERFACES} 22:46:03.667
dvi: Using exported function 'NciDeviceInstall' in
module 'C:\Windows\system32\nci.dll'.
dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
dvi: Using exported function
'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'.
dvi: CoInstaller 2 ==
wlaninst.dll,WlanDeviceClassCoInstaller
dvi: Using exported function
'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'.
dvi: CoInstaller 3 ==
wwaninst.dll,WwanDeviceClassCoInstaller
dvi: CoInstaller 1: Enter 22:46:03.679
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 22:46:03.682
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 22:46:03.685
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 22:46:03.689
dvi: Class installer: Exit
dvi: Default installer: Enter 22:46:03.692
dvi: {Install INTERFACES}
inf: Opened PNF:
'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
dvi: Installing section
[LbAdapter.ndi.Interfaces]
dvi: {Install INTERFACES exit 00000000}
dvi: Default installer: Exit
dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 22:46:03.701
ndv: Installing device...
dvi: {DIF_INSTALLDEVICE} 22:46:03.704
dvi: CoInstaller 1: Enter 22:46:03.705
cci: NdisCoinst: NetCfgInstanceId does not exist
cci: NdisCoinst: Guid of the adapter is
{C88CF875-4F7E-465E-BD02-DD2639E1A43A}
inf: Opened PNF: 'C:\Windows\INF\oem26.inf'
([strings])
cci: NdisCoinst: IfType from registry is 1
cci: NdisCoinst: IfType 1, Characteristics 0x1,
IsIrdaDevice 0, PhysicalMediaType -1, MediaType -1, IsBridge 0,
FoundGuidInDownlevel 0, EnableDhcp 2
cci: NdisCoinst: Connection name is Local Area
Connection 3
cci: NdisCoinst: NetLuidIndex does not exist
!!! cci: NdisCoinst: NcipAllocateNetLuidIndex failed
with error 0x5aa
!!! dvi: CoInstaller 1: failed(0x000005aa)!
!!! dvi: Error 1450: Insufficient system resources exist to
complete the requested service.
dvi: {DIF_INSTALLDEVICE - exit(0x000005aa)} 22:46:03.767
!!! ndv: Error(000005aa) installing device!
ndv: Device install status=0x000005aa
ndv: Performing device install final cleanup...
! ndv: Queueing up error report since device installation
failed...
ndv: {Core Device Install - exit(0x000005aa)} 22:46:03.774
dvi: {DIF_DESTROYPRIVATEDATA} 22:46:03.775
dvi: CoInstaller 1: Enter 22:46:03.777
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 22:46:03.780
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 22:46:03.783
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 22:46:03.787
dvi: Class installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 22:46:03.791
ump: Server install process exited with code 0x000005aa
22:46:03.822
ump: {Plug and Play Service: Device Install exit(000005aa)}
ndv: Device Install failed for new device...installing NULL driver.
dvi: {Plug and Play Service: Device Install for ROOT\NET\0000}
ump: Creating Install Process: DrvInst.exe 22:46:03.838
! ndv: Installing NULL driver!
dvi: Set selected driver complete.
dvi: {DIF_ALLOW_INSTALL} 22:46:03.975
dvi: Using exported function 'NetClassInstaller' in module
'C:\Windows\system32\NetCfgx.dll'.
dvi: Class installer == NetCfgx.dll,NetClassInstaller
dvi: Using exported function 'NciDeviceInstall' in module
'C:\Windows\system32\nci.dll'.
dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
dvi: Using exported function 'WlanDeviceClassCoInstaller' in
module 'C:\Windows\system32\wlaninst.dll'.
dvi: CoInstaller 2 == wlaninst.dll,WlanDeviceClassCoInstaller
dvi: Using exported function 'WwanDeviceClassCoInstaller' in
module 'C:\Windows\system32\wwaninst.dll'.
dvi: CoInstaller 3 == wwaninst.dll,WwanDeviceClassCoInstaller
dvi: CoInstaller 1: Enter 22:46:04.004
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 22:46:04.008
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 22:46:04.010
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 22:46:04.012
dvi: Class installer: Exit
dvi: Default installer: Enter 22:46:04.019
dvi: Default installer: Exit
dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 22:46:04.022
dvi: {DIF_INSTALLDEVICE} 22:46:04.024
dvi: CoInstaller 1: Enter 22:46:04.026
cci: NdisCoinst: Succesfully set NewDeviceInstall to 0
cci: NdisCoinst: Null driver install
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 22:46:04.034
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 22:46:04.037
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 22:46:04.041
cci: [NCI BEGIN INSTALL DEVICE for ROOT\NET\0000]
cci: NCI: Null driver install.
cci: NCI: NewDeviceInstall is 0. Assuming this is an
update
dvi: {DIF_REMOVE} 22:46:04.046
dvi: CoInstaller 1: Enter 22:46:04.049
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 22:46:04.052
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 22:46:04.055
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 22:46:04.058
cci: [NCI BEGIN REMOVE DEVICE for
ROOT\NET\0000]
cci: [NCI: BEGIN STORE EXTERNAL RESOURCE INFO]
cci: NCI: IfType=1
cci: NCI:
NetcfgInstanceId(GUID)={C88CF875-4F7E-465E-BD02-DD2639E1A43A}
cci: [NCI: END STORE EXTERNAL RESOURCE INFO]
dvi: {Remove DEVICE}
dvi: InstanceID = 'ROOT\NET\0000'
dvi: Devnode Status = 0x01802001
dvi: CM_Query_And_Remove_Subtree_Ex
returns 0x00000000
dvi: Devnode Status after
CM_Query_And_Remove_Subtree_Ex = 0x01802401
dvi: Query-and-Remove succeeded
dvi: {Delete DEVICE}
dvi: Device Instance uninstalled.
dvi: {Delete DEVICE exit (0x00000000)}
dvi: {Remove DEVICE exit (0x00000000)}
cci: NCI:Delayed Cleanup not required..
DevInstallParams.Flags=0x00800000
cci: NCI: Notifying binding engine of removal
cci: NCI: INetCfg UnInstaller Interface asking
for write lock. 22:46:04.180
cci: NCI: INetCfg UnInstaller Interface
acquired write lock. 22:46:04.182
cci: NCI: Init Notify Object for ms_ndiscap
cci: NCI: Init Notify Object for ms_ndiscap
complete
cci: NCI: Init Notify Object for ms_server
cci: NCI: Init Notify Object for ms_server
complete
cci: NCI: Init Notify Object for ms_steelhead
cci: NCI: Init Notify Object for ms_steelhead
complete
cci: NCI: Init Notify Object for ms_rassrv
cci: NCI: Init Notify Object for ms_rassrv
complete
cci: NCI: Init Notify Object for ms_msclient
cci: NCI: Init Notify Object for ms_msclient
complete
cci: NCI: Init Notify Object for ms_tcpip6
cci: NCI: Init Notify Object for ms_tcpip6
complete
cci: NCI: Init Notify Object for ms_tcpip
cci: NCI: Init Notify Object for ms_tcpip
complete
cci: NCI: Init Notify Object for ms_pppoe
cci: NCI: Init Notify Object for ms_pppoe
complete
cci: NCI: Init Notify Object for ms_pptp
cci: NCI: Init Notify Object for ms_pptp
complete
cci: NCI: Init Notify Object for ms_l2tp
cci: NCI: Init Notify Object for ms_l2tp
complete
cci: NCI: Init Notify Object for ms_ndiswan
cci: NCI: Init Notify Object for ms_ndiswan
complete
cci: NCI: Init Notify Object for ms_agilevpn
cci: NCI: Init Notify Object for ms_agilevpn
complete
cci: NCI: Init Notify Object for ms_sstp
cci: NCI: Init Notify Object for ms_sstp
complete
cci: [NCI: BEGIN Release Externally Managed
Resources]
cci: NCI: IfType=1
cci: NCI:
NetcfgInstanceId(GUID)={C88CF875-4F7E-465E-BD02-DD2639E1A43A}
! cci: !NCI: IfType Present, NetLuidIndex NOT
Present. pszPnpID= ROOT\NET\0000
cci: NCI: Successfully deleted Connection
Registry Key for GUID={C88CF875-4F7E-465E-BD02-DD2639E1A43A}
cci: [NCI: END Release Externally Managed
Resources]
cci: NCI: INetCfg UnInstaller Interface
Released write lock. 22:46:04.937
cci:

cci: [NCI END REMOVE DEVICE for ROOT\NET\0000.
Result 0x00000000]
dvi: Class installer: Exit
dvi: CoInstaller 1: Enter (Post Processing)
22:46:04.945
dvi: CoInstaller 1: Exit (Post Processing)
dvi: {DIF_REMOVE - exit(0x00000000)} 22:46:04.948
cci: [NCI END INSTALL DEVICE for ROOT\NET\0000]
dvi: Class installer: Exit
dvi: Default installer: Enter 22:46:04.952
!!! dvi: Error obtaining device ID!
!!! dvi: Cleaning up failed installation (00000006)
! dvi: Failed to set Config Flags property: 0x00000020
! dvi: Error 0xe000020b: The device instance does not
exist in the hardware tree.
!!! dvi: Default installer: failed!
!!! dvi: Error 6: The handle is invalid.
dvi: {DIF_INSTALLDEVICE - exit(0x00000006)} 22:46:04.962
dvi: {DIF_DESTROYPRIVATEDATA} 22:46:04.964
dvi: CoInstaller 1: Enter 22:46:04.966
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 22:46:04.969
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 22:46:04.972
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 22:46:04.975
dvi: Class installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 22:46:04.979
ump: Server install process exited with code 0x00000006
22:46:04.986
ump: {Plug and Play Service: Device Install exit(00000006)}
dvi: {Build Driver List} 22:46:04.990
! dvi: Driver list already built
dvi: {Build Driver List - exit(0x00000000)} 22:46:04.994
dvi: {DIF_SELECTBESTCOMPATDRV} 22:46:04.996
dvi: CoInstaller 1: Enter 22:46:04.998
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 22:46:05.000
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 22:46:05.002
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 22:46:05.006
dvi: Class installer: Exit
dvi: Default installer: Enter 22:46:05.009
dvi: {Select Best Driver}
dvi: Selected driver installs from section
[LbAdapter.ndi] in 'c:\program files\echobit\lan
bridger\driver\netlb_x64.inf'.
dvi: {DIF_DESTROYPRIVATEDATA} 22:46:05.014
dvi: CoInstaller 1: Enter 22:46:05.016
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 22:46:05.019
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 22:46:05.023
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 22:46:05.026
dvi: Class installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)}
22:46:05.029
dvi: Set selected driver complete.
dvi: Selected:
dvi: Description - [LAN Bridger Virtual Ethernet
Adapter]
dvi: InfFile - [c:\program files\echobit\lan
bridger\driver\netlb_x64.inf]
dvi: Section - [LbAdapter.ndi]
dvi: Signer - [Echobit, LLC]
dvi: Rank - [0x00ff0000]
dvi: {Select Best Driver - exit(0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 22:46:05.043
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 22:46:05.044
dvi: Using exported function 'NetClassInstaller' in module
'C:\Windows\system32\NetCfgx.dll'.
dvi: Class installer == NetCfgx.dll,NetClassInstaller
dvi: Using exported function 'NciDeviceInstall' in module
'C:\Windows\system32\nci.dll'.
dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
dvi: Using exported function 'WlanDeviceClassCoInstaller' in
module 'C:\Windows\system32\wlaninst.dll'.
dvi: CoInstaller 2 == wlaninst.dll,WlanDeviceClassCoInstaller
dvi: Using exported function 'WwanDeviceClassCoInstaller' in
module 'C:\Windows\system32\wwaninst.dll'.
dvi: CoInstaller 3 == wwaninst.dll,WwanDeviceClassCoInstaller
dvi: CoInstaller 1: Enter 22:46:05.062
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 22:46:05.065
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 22:46:05.069
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 22:46:05.072
!!! dvi: Class installer: failed(0xe000020b)!
!!! dvi: Error 0xe000020b: The device instance does not exist in the
hardware tree.
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020b)}
22:46:05.077
dvi: {DIF_DESTROYPRIVATEDATA} 22:46:05.079
dvi: CoInstaller 1: Enter 22:46:05.081
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 22:46:05.083
dvi: CoInstaller 2: Exit
dvi: CoInstaller 3: Enter 22:46:05.086
dvi: CoInstaller 3: Exit
dvi: Class installer: Enter 22:46:05.089
dvi: Class installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 22:46:05.092
<<< Section end 2010/05/13 22:46:05.094
<<< [Exit status: SUCCESS]

Comments

  • Jeffrey_Tippet_[MSFT]Jeffrey_Tippet_[MSFT] Member - All Emails Posts: 450
    I agree with your assessment -- the NcipAllocateNetLuidIndex bit looks to be the problem. I don't have a good guess as to what's gone wrong, but here's some background info that might help you figure it out. (This info is an implementation detail, subject to change, but may come in handy for troubleshooting):

    NDIS must allocate a (locally) unique number for each network interface, the NET_LUID. The NET_LUID consists of the ifType, paired with a unique ID number. To generate that unique ID, we keep track of the IDs that have already been assigned in
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NDIS\IfTypes\[ifType] ! IfUsedNetLuidIndices (REG_BINARY)
    for each ifType. For example, look in \6 if your NIC is Ethernet (ifType==6).

    In there, there is IfUsedNetLuidIndices, which is (IIRC) a bitmap of the unique IDs that have been assigned to other network interfaces. Make sure this value is present and not damaged (e.g., a huge number of 0xFF's). Typically, its value will be something like 0xFF 0x01, if you have 9 NICs. Note that you can't just whack this value and replace it with something else, since then NDIS will incorrectly assign the same NET_LUID to two interfaces, and all sorts of things will break when that happens.

    -----Original Message-----
    From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Soren Dreijer
    Sent: Thursday, May 13, 2010 7:29 PM
    To: Windows System Software Devs Interest List
    Subject: [ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when installing

    Hey al,

    We have a customer who is experiencing problems installing our NDIS miniport driver. He's getting error 1450 (ERROR_NO_SYSTEM_RESOURCES), but states he has plenty of disk space, etc. available. Looking through the setupapi.log tells me two things:

    1. There seem to be some certificate issues, but I'm seeing similar errors/warnings on my machine, so my guess is that they're perhaps related to WHQL (our driver isn't WHQL-certified).

    2. The following piece of the log worries me:

    ndv: Installing device...
    dvi: {DIF_INSTALLDEVICE} 22:46:03.704
    dvi: CoInstaller 1: Enter 22:46:03.705
    cci: NdisCoinst: NetCfgInstanceId does not exist
    cci: NdisCoinst: Guid of the adapter is
    {C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    inf: Opened PNF: 'C:\Windows\INF\oem26.inf'
    ([strings])
    cci: NdisCoinst: IfType from registry is 1
    cci: NdisCoinst: IfType 1, Characteristics 0x1,
    IsIrdaDevice 0, PhysicalMediaType -1, MediaType -1, IsBridge 0, FoundGuidInDownlevel 0, EnableDhcp 2
    cci: NdisCoinst: Connection name is Local Area
    Connection 3
    cci: NdisCoinst: NetLuidIndex does not exist
    !!! cci: NdisCoinst: NcipAllocateNetLuidIndex failed
    with error 0x5aa
    !!! dvi: CoInstaller 1: failed(0x000005aa)!
    !!! dvi: Error 1450: Insufficient system resources exist to
    complete the requested service.
    dvi: {DIF_INSTALLDEVICE - exit(0x000005aa)} 22:46:03.767
    !!! ndv: Error(000005aa) installing device!
    ndv: Device install status=0x000005aa
    ndv: Performing device install final cleanup...
    ! ndv: Queueing up error report since device installation
    failed...

    I'm hoping some trained eyes here from NTDEV might see something in the log that I don't. I've included the full setupapi.log below.

    Thanks,
    Soren

    [Device Install Log]
    OS Version = 6.1.7600
    Service Pack = 0.0
    Suite = 0x0100
    ProductType = 1
    Architecture = amd64

    [BeginLog]



    >>> [Device Install (UpdateDriverForPlugAndPlayDevices) -
    >>> root\LbAdapter] Section start 2010/05/13 22:45:59.836
    cmd: "C:\Program Files\Echobit\LAN Bridger\installer_helper_x64.exe"
    install "C:\Program Files\Echobit\LAN Bridger\Driver\netLB_x64.inf"
    "root\LbAdapter"
    dvi: Set selected driver complete.
    dvi: {Build Driver List} 22:46:00.748
    cpy: Policy is set to make all digital signatures equal.
    dvi: Processing a single INF: 'c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf'
    inf: Opened INF: 'c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf' ([strings])
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:00.755
    sig: Key = netlb_x64.inf
    sig: FilePath = c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf
    sig: Catalog = c:\program files\echobit\lan
    bridger\driver\netLB_x64.cat
    flq: {SPFILENOTIFY_CABINETINFO}
    flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)}
    flq: {SPFILENOTIFY_FILEEXTRACTED}
    flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)}
    ! sig: Verifying file against specific (valid) catalog failed!
    (0x800b0109)
    ! sig: Error 0x800b0109: A certificate chain processed, but
    terminated in a root certificate which is not trusted by the trust provider.
    sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 22:46:01.061
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:01.062
    sig: Key = netlb_x64.inf
    sig: FilePath = c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf
    sig: Catalog = c:\program files\echobit\lan
    bridger\driver\netLB_x64.cat
    sig: Success: File is signed in Authenticode(tm) catalog.
    sig: Error 0xe0000242: The publisher of an Authenticode(tm)
    signed catalog has not yet been established as trusted.
    sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 22:46:01.099
    dvi: Created Driver Node:
    dvi: HardwareID - root\LbAdapter
    dvi: InfName - c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf
    dvi: DevDesc - LAN Bridger Virtual Ethernet Adapter
    dvi: DrvDesc - LAN Bridger Virtual Ethernet Adapter
    dvi: Provider - Echobit LLC
    dvi: Mfg - Echobit LLC
    dvi: ModelsSec - Lb.NTamd64
    dvi: InstallSec - LbAdapter.ndi
    dvi: ActualSec - LbAdapter.ndi
    dvi: Rank - 0x00ff0000
    dvi: Signer - Echobit, LLC
    dvi: Signer Score - Authenticode
    dvi: DrvDate - 11/01/2008
    dvi: Version - 6.0.0.1
    dvi: {Build Driver List - exit(0x00000000)} 22:46:01.125
    dvi: {DIF_SELECTBESTCOMPATDRV} 22:46:01.126
    dvi: Using exported function 'NetClassInstaller' in module
    'C:\Windows\system32\NetCfgx.dll'.
    dvi: Class installer == NetCfgx.dll,NetClassInstaller
    dvi: Using exported function 'NciDeviceInstall' in module
    'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function 'WlanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 == wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function 'WwanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 == wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:01.142
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:01.145
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:01.149
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:01.152
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:01.155
    dvi: {Select Best Driver}
    dvi: Selected driver installs from section
    [LbAdapter.ndi] in 'c:\program files\echobit\lan bridger\driver\netlb_x64.inf'.
    dvi: Set selected driver complete.
    dvi: Selected:
    dvi: Description - [LAN Bridger Virtual Ethernet
    Adapter]
    dvi: InfFile - [c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf]
    dvi: Section - [LbAdapter.ndi]
    dvi: Signer - [Echobit, LLC]
    dvi: Rank - [0x00ff0000]
    dvi: {Select Best Driver - exit(0x00000000)}
    dvi: Default installer: Exit
    dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 22:46:01.171
    inf: {SetupCopyOEMInf: c:\program files\echobit\lan bridger\driver\netlb_x64.inf} 22:46:01.172
    ! inf: Package was already in store: skipping Driver Store add
    inf: {SetupCopyOEMInf exit (0x00000000)} 22:46:01.852
    inf: Opened PNF:
    'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:01.861
    sig: Key = netlb_x64.inf
    sig: FilePath =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netlb_x64.inf
    sig: Catalog =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netLB_x64.cat
    ! sig: Verifying file against specific (valid) catalog failed!
    (0x800b0109)
    ! sig: Error 0x800b0109: A certificate chain processed, but
    terminated in a root certificate which is not trusted by the trust provider.
    sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 22:46:01.881
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:01.882
    sig: Key = netlb_x64.inf
    sig: FilePath =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netlb_x64.inf
    sig: Catalog =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netLB_x64.cat
    sig: Success: File is signed in Authenticode(tm) catalog.
    sig: Error 0xe0000242: The publisher of an Authenticode(tm) signed
    catalog has not yet been established as trusted.
    sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 22:46:01.919
    dvi: Selected driver installs from section [LbAdapter.ndi] in 'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf'.
    dvi: Set selected driver complete.
    dvi: {Plug and Play Service: Device Install for ROOT\NET\0000}
    ump: Creating Install Process: DrvInst.exe 22:46:02.109
    ndv: Infpath=C:\Windows\INF\oem26.inf
    ndv:
    DriverNodeName=netlb_x64.inf:Lb.NTamd64:LbAdapter.ndi:6.0.0.1:root\lbadapter
    ndv:
    DriverStorepath=C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf
    _amd64_neutral_41ce5dbcf7c93cc8\netlb_x64.inf
    ndv: Building driver list from driver node strong name...
    inf: Opened PNF:
    'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:02.559
    sig: Key = netlb_x64.inf
    sig: FilePath =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netlb_x64.inf
    sig: Catalog =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netLB_x64.cat
    flq: {SPFILENOTIFY_CABINETINFO}
    flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)}
    flq: {SPFILENOTIFY_FILEEXTRACTED}
    flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)}
    ! sig: Verifying file against specific (valid) catalog failed!
    (0x800b0109)
    ! sig: Error 0x800b0109: A certificate chain processed, but
    terminated in a root certificate which is not trusted by the trust provider.
    sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 22:46:02.648
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:02.649
    sig: Key = netlb_x64.inf
    sig: FilePath =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netlb_x64.inf
    sig: Catalog =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netLB_x64.cat
    sig: Success: File is signed in Authenticode(tm) catalog.
    sig: Error 0xe0000242: The publisher of an Authenticode(tm)
    signed catalog has not yet been established as trusted.
    sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 22:46:02.686
    dvi: Selected driver installs from section [LbAdapter.ndi] in
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf'.
    dvi: Set selected driver complete.
    ndv: {Core Device Install} 22:46:02.691
    inf: Opened PNF: 'C:\Windows\INF\oem26.inf' ([strings])
    dvi: {DIF_ALLOW_INSTALL} 22:46:02.809
    dvi: Using exported function 'NetClassInstaller' in
    module 'C:\Windows\system32\NetCfgx.dll'.
    dvi: Class installer == NetCfgx.dll,NetClassInstaller
    dvi: Using exported function 'NciDeviceInstall' in
    module 'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function
    'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 ==
    wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function
    'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 ==
    wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:02.830
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:02.833
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:02.835
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:02.839
    inf: Opened PNF: 'C:\Windows\INF\oem26.inf'
    ([strings])
    inf: AddReg=LbAdapter.Reg (oem26.inf line 33)
    inf: AddReg=LbAdapter.Reg.Adapter.Params
    (oem26.inf line 34)
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:02.917
    dvi: Default installer: Exit
    dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 22:46:02.920
    ndv: Installing files...
    dvi: {DIF_INSTALLDEVICEFILES} 22:46:02.924
    dvi: CoInstaller 1: Enter 22:46:02.926
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:02.930
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:02.933
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:02.936
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:02.940
    dvi: {Install FILES}
    inf: Opened PNF:
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    inf: {Install Inf Section [LbAdapter.ndi]}
    inf: CopyFiles=LbAdapter.CopyFiles
    (netlb_x64.inf line 35)
    cpy: Open PnpLockdownPolicy: Err=2. This
    is OK. Use LockDownPolicyDefault
    flq: QueueSingleCopy...
    flq: Inf :
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf'
    flq: SourceInf:
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf'
    flq: SourceSection: [sourcedisksfiles]
    flq: Source root path based on SourceInf
    flq: SourceRootPath:
    'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8'
    flq: {FILE_QUEUE_COPY}
    flq: CopyStyle - 0x00000400
    flq: {FILE_QUEUE_COPY}
    flq: CopyStyle -
    0x00000400
    flq: SourceRootPath -
    'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8'
    flq: SourceFilename - 'lb.sys'
    flq: TargetDirectory-
    'C:\Windows\system32\DRIVERS'
    flq: TargetFilename - 'lb.sys'
    flq: SourceDesc - 'LAN
    Bridger Virtual Ethernet Adapter Installation Disk'
    flq: {FILE_QUEUE_COPY
    exit(0x00000000)}
    flq: {FILE_QUEUE_COPY exit(0x00000000)}
    inf: {Install Inf Section [LbAdapter.ndi] exit
    (0x00000000)}
    dvi: Processing co-installer registration
    section [LbAdapter.ndi.CoInstallers].
    inf: {Install Inf Section
    [LbAdapter.ndi.CoInstallers]}
    inf: {Install Inf Section
    [LbAdapter.ndi.CoInstallers] exit (0x00000000)}
    dvi: Co-installers registered.
    dvi: {Install INTERFACES}
    dvi: Installing section
    [LbAdapter.ndi.Interfaces]
    dvi: {Install INTERFACES exit 00000000}
    dvi: {Install FILES exit (0x00000000)}
    dvi: Default installer: Exit
    dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 22:46:02.988
    ndv: Pruning file queue...
    dvi: {_SCAN_FILE_QUEUE}
    flq: ScanQ flags=620
    flq: SPQ_SCAN_PRUNE_COPY_QUEUE
    flq: SPQ_SCAN_FILE_COMPARISON
    flq: SPQ_SCAN_ACTIVATE_DRP
    flq: ScanQ number of copy nodes=1
    flq: File 'C:\Windows\system32\DRIVERS\lb.sys' pruned
    from copy.
    sig: Using catalog
    'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem26.CA
    T'.
    flq: {SPFILENOTIFY_CABINETINFO}
    flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)}
    flq: {SPFILENOTIFY_FILEEXTRACTED}
    flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)}
    ! sig: VerifyTrustFailed for
    C:\Windows\system32\DRIVERS\lb.sys.
    ! sig: Error 0x800b0109: A certificate chain processed,
    but terminated in a root certificate which is not trusted by the trust provider.
    cpy: DrpSetRegFileProt
    'C:\Windows\system32\DRIVERS\lb.sys' Status=0 Class=OEM Legacy
    flq: ScanQ action=200 DoPruning=32
    flq: ScanQ end Validity flags=620 CopyNodes=0
    dvi: {_SCAN_FILE_QUEUE exit(0, 0x00000000)}
    ndv: Committing file queue...
    flq: {_commit_file_queue}
    flq: CommitQ DelNodes=0 RenNodes=0 CopyNodes=0
    flq: CommitQ early exit: No nodes are queued
    flq: {_commit_file_queue exit OK}
    ndv: Registering CoInstallers...
    dvi: {DIF_REGISTER_COINSTALLERS} 22:46:03.581
    dvi: CoInstaller 1: Enter 22:46:03.583
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:03.586
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:03.589
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:03.591
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:03.594
    inf: Opened PNF:
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    inf: {Install Inf Section
    [LbAdapter.ndi.CoInstallers]}
    inf: {Install Inf Section
    [LbAdapter.ndi.CoInstallers] exit (0x00000000)}
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:03.645
    dvi: CoInstaller 1: Enter 22:46:03.647
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:03.650
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:03.653
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:03.657
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)}
    22:46:03.661
    dvi: Co-installers registered.
    dvi: Default installer: Exit
    dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)}
    22:46:03.665
    ndv: Installing interfaces...
    dvi: {DIF_INSTALLINTERFACES} 22:46:03.667
    dvi: Using exported function 'NciDeviceInstall' in
    module 'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function
    'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 ==
    wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function
    'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 ==
    wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:03.679
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:03.682
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:03.685
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:03.689
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:03.692
    dvi: {Install INTERFACES}
    inf: Opened PNF:
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    dvi: Installing section
    [LbAdapter.ndi.Interfaces]
    dvi: {Install INTERFACES exit 00000000}
    dvi: Default installer: Exit
    dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 22:46:03.701
    ndv: Installing device...
    dvi: {DIF_INSTALLDEVICE} 22:46:03.704
    dvi: CoInstaller 1: Enter 22:46:03.705
    cci: NdisCoinst: NetCfgInstanceId does not exist
    cci: NdisCoinst: Guid of the adapter is
    {C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    inf: Opened PNF: 'C:\Windows\INF\oem26.inf'
    ([strings])
    cci: NdisCoinst: IfType from registry is 1
    cci: NdisCoinst: IfType 1, Characteristics 0x1,
    IsIrdaDevice 0, PhysicalMediaType -1, MediaType -1, IsBridge 0, FoundGuidInDownlevel 0, EnableDhcp 2
    cci: NdisCoinst: Connection name is Local Area
    Connection 3
    cci: NdisCoinst: NetLuidIndex does not exist
    !!! cci: NdisCoinst: NcipAllocateNetLuidIndex failed
    with error 0x5aa
    !!! dvi: CoInstaller 1: failed(0x000005aa)!
    !!! dvi: Error 1450: Insufficient system resources exist to
    complete the requested service.
    dvi: {DIF_INSTALLDEVICE - exit(0x000005aa)} 22:46:03.767
    !!! ndv: Error(000005aa) installing device!
    ndv: Device install status=0x000005aa
    ndv: Performing device install final cleanup...
    ! ndv: Queueing up error report since device installation
    failed...
    ndv: {Core Device Install - exit(0x000005aa)} 22:46:03.774
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:03.775
    dvi: CoInstaller 1: Enter 22:46:03.777
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:03.780
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:03.783
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:03.787
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 22:46:03.791
    ump: Server install process exited with code 0x000005aa
    22:46:03.822
    ump: {Plug and Play Service: Device Install exit(000005aa)}
    ndv: Device Install failed for new device...installing NULL driver.
    dvi: {Plug and Play Service: Device Install for ROOT\NET\0000}
    ump: Creating Install Process: DrvInst.exe 22:46:03.838
    ! ndv: Installing NULL driver!
    dvi: Set selected driver complete.
    dvi: {DIF_ALLOW_INSTALL} 22:46:03.975
    dvi: Using exported function 'NetClassInstaller' in module
    'C:\Windows\system32\NetCfgx.dll'.
    dvi: Class installer == NetCfgx.dll,NetClassInstaller
    dvi: Using exported function 'NciDeviceInstall' in module
    'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function 'WlanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 == wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function 'WwanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 == wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:04.004
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:04.008
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:04.010
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:04.012
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:04.019
    dvi: Default installer: Exit
    dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 22:46:04.022
    dvi: {DIF_INSTALLDEVICE} 22:46:04.024
    dvi: CoInstaller 1: Enter 22:46:04.026
    cci: NdisCoinst: Succesfully set NewDeviceInstall to 0
    cci: NdisCoinst: Null driver install
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:04.034
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:04.037
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:04.041
    cci: [NCI BEGIN INSTALL DEVICE for ROOT\NET\0000]
    cci: NCI: Null driver install.
    cci: NCI: NewDeviceInstall is 0. Assuming this is an
    update
    dvi: {DIF_REMOVE} 22:46:04.046
    dvi: CoInstaller 1: Enter 22:46:04.049
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:04.052
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:04.055
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:04.058
    cci: [NCI BEGIN REMOVE DEVICE for
    ROOT\NET\0000]
    cci: [NCI: BEGIN STORE EXTERNAL RESOURCE INFO]
    cci: NCI: IfType=1
    cci: NCI:
    NetcfgInstanceId(GUID)={C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    cci: [NCI: END STORE EXTERNAL RESOURCE INFO]
    dvi: {Remove DEVICE}
    dvi: InstanceID = 'ROOT\NET\0000'
    dvi: Devnode Status = 0x01802001
    dvi: CM_Query_And_Remove_Subtree_Ex
    returns 0x00000000
    dvi: Devnode Status after
    CM_Query_And_Remove_Subtree_Ex = 0x01802401
    dvi: Query-and-Remove succeeded
    dvi: {Delete DEVICE}
    dvi: Device Instance uninstalled.
    dvi: {Delete DEVICE exit (0x00000000)}
    dvi: {Remove DEVICE exit (0x00000000)}
    cci: NCI:Delayed Cleanup not required..
    DevInstallParams.Flags=0x00800000
    cci: NCI: Notifying binding engine of removal
    cci: NCI: INetCfg UnInstaller Interface asking
    for write lock. 22:46:04.180
    cci: NCI: INetCfg UnInstaller Interface
    acquired write lock. 22:46:04.182
    cci: NCI: Init Notify Object for ms_ndiscap
    cci: NCI: Init Notify Object for ms_ndiscap
    complete
    cci: NCI: Init Notify Object for ms_server
    cci: NCI: Init Notify Object for ms_server
    complete
    cci: NCI: Init Notify Object for ms_steelhead
    cci: NCI: Init Notify Object for ms_steelhead
    complete
    cci: NCI: Init Notify Object for ms_rassrv
    cci: NCI: Init Notify Object for ms_rassrv
    complete
    cci: NCI: Init Notify Object for ms_msclient
    cci: NCI: Init Notify Object for ms_msclient
    complete
    cci: NCI: Init Notify Object for ms_tcpip6
    cci: NCI: Init Notify Object for ms_tcpip6
    complete
    cci: NCI: Init Notify Object for ms_tcpip
    cci: NCI: Init Notify Object for ms_tcpip
    complete
    cci: NCI: Init Notify Object for ms_pppoe
    cci: NCI: Init Notify Object for ms_pppoe
    complete
    cci: NCI: Init Notify Object for ms_pptp
    cci: NCI: Init Notify Object for ms_pptp
    complete
    cci: NCI: Init Notify Object for ms_l2tp
    cci: NCI: Init Notify Object for ms_l2tp
    complete
    cci: NCI: Init Notify Object for ms_ndiswan
    cci: NCI: Init Notify Object for ms_ndiswan
    complete
    cci: NCI: Init Notify Object for ms_agilevpn
    cci: NCI: Init Notify Object for ms_agilevpn
    complete
    cci: NCI: Init Notify Object for ms_sstp
    cci: NCI: Init Notify Object for ms_sstp
    complete
    cci: [NCI: BEGIN Release Externally Managed
    Resources]
    cci: NCI: IfType=1
    cci: NCI:
    NetcfgInstanceId(GUID)={C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    ! cci: !NCI: IfType Present, NetLuidIndex NOT
    Present. pszPnpID= ROOT\NET\0000
    cci: NCI: Successfully deleted Connection
    Registry Key for GUID={C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    cci: [NCI: END Release Externally Managed
    Resources]
    cci: NCI: INetCfg UnInstaller Interface
    Released write lock. 22:46:04.937
    cci:

    cci: [NCI END REMOVE DEVICE for ROOT\NET\0000.
    Result 0x00000000]
    dvi: Class installer: Exit
    dvi: CoInstaller 1: Enter (Post Processing)
    22:46:04.945
    dvi: CoInstaller 1: Exit (Post Processing)
    dvi: {DIF_REMOVE - exit(0x00000000)} 22:46:04.948
    cci: [NCI END INSTALL DEVICE for ROOT\NET\0000]
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:04.952
    !!! dvi: Error obtaining device ID!
    !!! dvi: Cleaning up failed installation (00000006)
    ! dvi: Failed to set Config Flags property: 0x00000020
    ! dvi: Error 0xe000020b: The device instance does not
    exist in the hardware tree.
    !!! dvi: Default installer: failed!
    !!! dvi: Error 6: The handle is invalid.
    dvi: {DIF_INSTALLDEVICE - exit(0x00000006)} 22:46:04.962
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:04.964
    dvi: CoInstaller 1: Enter 22:46:04.966
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:04.969
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:04.972
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:04.975
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 22:46:04.979
    ump: Server install process exited with code 0x00000006
    22:46:04.986
    ump: {Plug and Play Service: Device Install exit(00000006)}
    dvi: {Build Driver List} 22:46:04.990
    ! dvi: Driver list already built
    dvi: {Build Driver List - exit(0x00000000)} 22:46:04.994
    dvi: {DIF_SELECTBESTCOMPATDRV} 22:46:04.996
    dvi: CoInstaller 1: Enter 22:46:04.998
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:05.000
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:05.002
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:05.006
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:05.009
    dvi: {Select Best Driver}
    dvi: Selected driver installs from section
    [LbAdapter.ndi] in 'c:\program files\echobit\lan bridger\driver\netlb_x64.inf'.
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:05.014
    dvi: CoInstaller 1: Enter 22:46:05.016
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:05.019
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:05.023
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:05.026
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)}
    22:46:05.029
    dvi: Set selected driver complete.
    dvi: Selected:
    dvi: Description - [LAN Bridger Virtual Ethernet
    Adapter]
    dvi: InfFile - [c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf]
    dvi: Section - [LbAdapter.ndi]
    dvi: Signer - [Echobit, LLC]
    dvi: Rank - [0x00ff0000]
    dvi: {Select Best Driver - exit(0x00000000)}
    dvi: Default installer: Exit
    dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 22:46:05.043
    dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 22:46:05.044
    dvi: Using exported function 'NetClassInstaller' in module
    'C:\Windows\system32\NetCfgx.dll'.
    dvi: Class installer == NetCfgx.dll,NetClassInstaller
    dvi: Using exported function 'NciDeviceInstall' in module
    'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function 'WlanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 == wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function 'WwanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 == wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:05.062
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:05.065
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:05.069
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:05.072
    !!! dvi: Class installer: failed(0xe000020b)!
    !!! dvi: Error 0xe000020b: The device instance does not exist in the
    hardware tree.
    dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020b)}
    22:46:05.077
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:05.079
    dvi: CoInstaller 1: Enter 22:46:05.081
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:05.083
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:05.086
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:05.089
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 22:46:05.092 <<< Section end 2010/05/13 22:46:05.094 <<< [Exit status: SUCCESS]



    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
  • OSR_Community_UserOSR_Community_User Member Posts: 110,218
    Thanks for the elaborate explanation, Jeffrey. I'll take a look at the
    customer's machine to see if the IfUsedNetLuidIndices value has been
    corrupted somehow. If I shouldn't manually change it, however, how do I fix
    it if it seems like the key has been corrupted?

    Thanks,
    Soren

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Jeffrey Tippet
    Sent: Saturday, May 15, 2010 11:49 AM
    To: Windows System Software Devs Interest List
    Subject: RE: [ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when
    installing

    I agree with your assessment -- the NcipAllocateNetLuidIndex bit looks to be
    the problem. I don't have a good guess as to what's gone wrong, but here's
    some background info that might help you figure it out. (This info is an
    implementation detail, subject to change, but may come in handy for
    troubleshooting):

    NDIS must allocate a (locally) unique number for each network interface, the
    NET_LUID. The NET_LUID consists of the ifType, paired with a unique ID
    number. To generate that unique ID, we keep track of the IDs that have
    already been assigned in

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NDIS\IfTypes\[ifType] !
    IfUsedNetLuidIndices (REG_BINARY)
    for each ifType. For example, look in \6 if your NIC is Ethernet
    (ifType==6).

    In there, there is IfUsedNetLuidIndices, which is (IIRC) a bitmap of the
    unique IDs that have been assigned to other network interfaces. Make sure
    this value is present and not damaged (e.g., a huge number of 0xFF's).
    Typically, its value will be something like 0xFF 0x01, if you have 9 NICs.
    Note that you can't just whack this value and replace it with something
    else, since then NDIS will incorrectly assign the same NET_LUID to two
    interfaces, and all sorts of things will break when that happens.

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Soren Dreijer
    Sent: Thursday, May 13, 2010 7:29 PM
    To: Windows System Software Devs Interest List
    Subject: [ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when installing

    Hey al,

    We have a customer who is experiencing problems installing our NDIS miniport
    driver. He's getting error 1450 (ERROR_NO_SYSTEM_RESOURCES), but states he
    has plenty of disk space, etc. available. Looking through the setupapi.log
    tells me two things:

    1. There seem to be some certificate issues, but I'm seeing similar
    errors/warnings on my machine, so my guess is that they're perhaps related
    to WHQL (our driver isn't WHQL-certified).

    2. The following piece of the log worries me:

    ndv: Installing device...
    dvi: {DIF_INSTALLDEVICE} 22:46:03.704
    dvi: CoInstaller 1: Enter 22:46:03.705
    cci: NdisCoinst: NetCfgInstanceId does not exist
    cci: NdisCoinst: Guid of the adapter is
    {C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    inf: Opened PNF: 'C:\Windows\INF\oem26.inf'
    ([strings])
    cci: NdisCoinst: IfType from registry is 1
    cci: NdisCoinst: IfType 1, Characteristics 0x1,
    IsIrdaDevice 0, PhysicalMediaType -1, MediaType -1, IsBridge 0,
    FoundGuidInDownlevel 0, EnableDhcp 2
    cci: NdisCoinst: Connection name is Local Area
    Connection 3
    cci: NdisCoinst: NetLuidIndex does not exist
    !!! cci: NdisCoinst: NcipAllocateNetLuidIndex failed
    with error 0x5aa
    !!! dvi: CoInstaller 1: failed(0x000005aa)!
    !!! dvi: Error 1450: Insufficient system resources exist to
    complete the requested service.
    dvi: {DIF_INSTALLDEVICE - exit(0x000005aa)} 22:46:03.767
    !!! ndv: Error(000005aa) installing device!
    ndv: Device install status=0x000005aa
    ndv: Performing device install final cleanup...
    ! ndv: Queueing up error report since device installation
    failed...

    I'm hoping some trained eyes here from NTDEV might see something in the log
    that I don't. I've included the full setupapi.log below.

    Thanks,
    Soren

    [Device Install Log]
    OS Version = 6.1.7600
    Service Pack = 0.0
    Suite = 0x0100
    ProductType = 1
    Architecture = amd64

    [BeginLog]



    >>> [Device Install (UpdateDriverForPlugAndPlayDevices) -
    >>> root\LbAdapter] Section start 2010/05/13 22:45:59.836
    cmd: "C:\Program Files\Echobit\LAN Bridger\installer_helper_x64.exe"
    install "C:\Program Files\Echobit\LAN Bridger\Driver\netLB_x64.inf"
    "root\LbAdapter"
    dvi: Set selected driver complete.
    dvi: {Build Driver List} 22:46:00.748
    cpy: Policy is set to make all digital signatures equal.
    dvi: Processing a single INF: 'c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf'
    inf: Opened INF: 'c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf' ([strings])
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:00.755
    sig: Key = netlb_x64.inf
    sig: FilePath = c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf
    sig: Catalog = c:\program files\echobit\lan
    bridger\driver\netLB_x64.cat
    flq: {SPFILENOTIFY_CABINETINFO}
    flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)}
    flq: {SPFILENOTIFY_FILEEXTRACTED}
    flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)}
    ! sig: Verifying file against specific (valid) catalog failed!
    (0x800b0109)
    ! sig: Error 0x800b0109: A certificate chain processed, but
    terminated in a root certificate which is not trusted by the trust provider.
    sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 22:46:01.061
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:01.062
    sig: Key = netlb_x64.inf
    sig: FilePath = c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf
    sig: Catalog = c:\program files\echobit\lan
    bridger\driver\netLB_x64.cat
    sig: Success: File is signed in Authenticode(tm) catalog.
    sig: Error 0xe0000242: The publisher of an Authenticode(tm)
    signed catalog has not yet been established as trusted.
    sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 22:46:01.099
    dvi: Created Driver Node:
    dvi: HardwareID - root\LbAdapter
    dvi: InfName - c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf
    dvi: DevDesc - LAN Bridger Virtual Ethernet Adapter
    dvi: DrvDesc - LAN Bridger Virtual Ethernet Adapter
    dvi: Provider - Echobit LLC
    dvi: Mfg - Echobit LLC
    dvi: ModelsSec - Lb.NTamd64
    dvi: InstallSec - LbAdapter.ndi
    dvi: ActualSec - LbAdapter.ndi
    dvi: Rank - 0x00ff0000
    dvi: Signer - Echobit, LLC
    dvi: Signer Score - Authenticode
    dvi: DrvDate - 11/01/2008
    dvi: Version - 6.0.0.1
    dvi: {Build Driver List - exit(0x00000000)} 22:46:01.125
    dvi: {DIF_SELECTBESTCOMPATDRV} 22:46:01.126
    dvi: Using exported function 'NetClassInstaller' in module
    'C:\Windows\system32\NetCfgx.dll'.
    dvi: Class installer == NetCfgx.dll,NetClassInstaller
    dvi: Using exported function 'NciDeviceInstall' in module
    'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function 'WlanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 == wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function 'WwanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 == wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:01.142
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:01.145
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:01.149
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:01.152
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:01.155
    dvi: {Select Best Driver}
    dvi: Selected driver installs from section
    [LbAdapter.ndi] in 'c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf'.
    dvi: Set selected driver complete.
    dvi: Selected:
    dvi: Description - [LAN Bridger Virtual Ethernet
    Adapter]
    dvi: InfFile - [c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf]
    dvi: Section - [LbAdapter.ndi]
    dvi: Signer - [Echobit, LLC]
    dvi: Rank - [0x00ff0000]
    dvi: {Select Best Driver - exit(0x00000000)}
    dvi: Default installer: Exit
    dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 22:46:01.171
    inf: {SetupCopyOEMInf: c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf} 22:46:01.172
    ! inf: Package was already in store: skipping Driver Store add
    inf: {SetupCopyOEMInf exit (0x00000000)} 22:46:01.852
    inf: Opened PNF:
    'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:01.861
    sig: Key = netlb_x64.inf
    sig: FilePath =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netlb_x64.inf
    sig: Catalog =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netLB_x64.cat
    ! sig: Verifying file against specific (valid) catalog failed!
    (0x800b0109)
    ! sig: Error 0x800b0109: A certificate chain processed, but
    terminated in a root certificate which is not trusted by the trust provider.
    sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 22:46:01.881
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:01.882
    sig: Key = netlb_x64.inf
    sig: FilePath =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netlb_x64.inf
    sig: Catalog =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netLB_x64.cat
    sig: Success: File is signed in Authenticode(tm) catalog.
    sig: Error 0xe0000242: The publisher of an Authenticode(tm) signed
    catalog has not yet been established as trusted.
    sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 22:46:01.919
    dvi: Selected driver installs from section [LbAdapter.ndi] in
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf'.
    dvi: Set selected driver complete.
    dvi: {Plug and Play Service: Device Install for ROOT\NET\0000}
    ump: Creating Install Process: DrvInst.exe 22:46:02.109
    ndv: Infpath=C:\Windows\INF\oem26.inf
    ndv:
    DriverNodeName=netlb_x64.inf:Lb.NTamd64:LbAdapter.ndi:6.0.0.1:root\lbadapter
    ndv:
    DriverStorepath=C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf
    _amd64_neutral_41ce5dbcf7c93cc8\netlb_x64.inf
    ndv: Building driver list from driver node strong name...
    inf: Opened PNF:
    'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:02.559
    sig: Key = netlb_x64.inf
    sig: FilePath =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netlb_x64.inf
    sig: Catalog =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netLB_x64.cat
    flq: {SPFILENOTIFY_CABINETINFO}
    flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)}
    flq: {SPFILENOTIFY_FILEEXTRACTED}
    flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)}
    ! sig: Verifying file against specific (valid) catalog failed!
    (0x800b0109)
    ! sig: Error 0x800b0109: A certificate chain processed, but
    terminated in a root certificate which is not trusted by the trust provider.
    sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 22:46:02.648
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:02.649
    sig: Key = netlb_x64.inf
    sig: FilePath =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netlb_x64.inf
    sig: Catalog =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netLB_x64.cat
    sig: Success: File is signed in Authenticode(tm) catalog.
    sig: Error 0xe0000242: The publisher of an Authenticode(tm)
    signed catalog has not yet been established as trusted.
    sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 22:46:02.686
    dvi: Selected driver installs from section [LbAdapter.ndi] in
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf'.
    dvi: Set selected driver complete.
    ndv: {Core Device Install} 22:46:02.691
    inf: Opened PNF: 'C:\Windows\INF\oem26.inf' ([strings])
    dvi: {DIF_ALLOW_INSTALL} 22:46:02.809
    dvi: Using exported function 'NetClassInstaller' in
    module 'C:\Windows\system32\NetCfgx.dll'.
    dvi: Class installer == NetCfgx.dll,NetClassInstaller
    dvi: Using exported function 'NciDeviceInstall' in
    module 'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function
    'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 ==
    wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function
    'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 ==
    wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:02.830
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:02.833
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:02.835
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:02.839
    inf: Opened PNF: 'C:\Windows\INF\oem26.inf'
    ([strings])
    inf: AddReg=LbAdapter.Reg (oem26.inf line 33)
    inf: AddReg=LbAdapter.Reg.Adapter.Params
    (oem26.inf line 34)
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:02.917
    dvi: Default installer: Exit
    dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 22:46:02.920
    ndv: Installing files...
    dvi: {DIF_INSTALLDEVICEFILES} 22:46:02.924
    dvi: CoInstaller 1: Enter 22:46:02.926
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:02.930
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:02.933
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:02.936
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:02.940
    dvi: {Install FILES}
    inf: Opened PNF:
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    inf: {Install Inf Section [LbAdapter.ndi]}
    inf: CopyFiles=LbAdapter.CopyFiles
    (netlb_x64.inf line 35)
    cpy: Open PnpLockdownPolicy: Err=2. This
    is OK. Use LockDownPolicyDefault
    flq: QueueSingleCopy...
    flq: Inf :
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf'
    flq: SourceInf:
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf'
    flq: SourceSection: [sourcedisksfiles]
    flq: Source root path based on SourceInf
    flq: SourceRootPath:
    'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8'
    flq: {FILE_QUEUE_COPY}
    flq: CopyStyle - 0x00000400
    flq: {FILE_QUEUE_COPY}
    flq: CopyStyle -
    0x00000400
    flq: SourceRootPath -
    'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8'
    flq: SourceFilename - 'lb.sys'
    flq: TargetDirectory-
    'C:\Windows\system32\DRIVERS'
    flq: TargetFilename - 'lb.sys'
    flq: SourceDesc - 'LAN
    Bridger Virtual Ethernet Adapter Installation Disk'
    flq: {FILE_QUEUE_COPY
    exit(0x00000000)}
    flq: {FILE_QUEUE_COPY exit(0x00000000)}
    inf: {Install Inf Section [LbAdapter.ndi] exit
    (0x00000000)}
    dvi: Processing co-installer registration
    section [LbAdapter.ndi.CoInstallers].
    inf: {Install Inf Section
    [LbAdapter.ndi.CoInstallers]}
    inf: {Install Inf Section
    [LbAdapter.ndi.CoInstallers] exit (0x00000000)}
    dvi: Co-installers registered.
    dvi: {Install INTERFACES}
    dvi: Installing section
    [LbAdapter.ndi.Interfaces]
    dvi: {Install INTERFACES exit 00000000}
    dvi: {Install FILES exit (0x00000000)}
    dvi: Default installer: Exit
    dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 22:46:02.988
    ndv: Pruning file queue...
    dvi: {_SCAN_FILE_QUEUE}
    flq: ScanQ flags=620
    flq: SPQ_SCAN_PRUNE_COPY_QUEUE
    flq: SPQ_SCAN_FILE_COMPARISON
    flq: SPQ_SCAN_ACTIVATE_DRP
    flq: ScanQ number of copy nodes=1
    flq: File 'C:\Windows\system32\DRIVERS\lb.sys' pruned
    from copy.
    sig: Using catalog
    'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem26.CA
    T'.
    flq: {SPFILENOTIFY_CABINETINFO}
    flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)}
    flq: {SPFILENOTIFY_FILEEXTRACTED}
    flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)}
    ! sig: VerifyTrustFailed for
    C:\Windows\system32\DRIVERS\lb.sys.
    ! sig: Error 0x800b0109: A certificate chain processed,
    but terminated in a root certificate which is not trusted by the trust
    provider.
    cpy: DrpSetRegFileProt
    'C:\Windows\system32\DRIVERS\lb.sys' Status=0 Class=OEM Legacy
    flq: ScanQ action=200 DoPruning=32
    flq: ScanQ end Validity flags=620 CopyNodes=0
    dvi: {_SCAN_FILE_QUEUE exit(0, 0x00000000)}
    ndv: Committing file queue...
    flq: {_commit_file_queue}
    flq: CommitQ DelNodes=0 RenNodes=0 CopyNodes=0
    flq: CommitQ early exit: No nodes are queued
    flq: {_commit_file_queue exit OK}
    ndv: Registering CoInstallers...
    dvi: {DIF_REGISTER_COINSTALLERS} 22:46:03.581
    dvi: CoInstaller 1: Enter 22:46:03.583
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:03.586
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:03.589
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:03.591
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:03.594
    inf: Opened PNF:
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    inf: {Install Inf Section
    [LbAdapter.ndi.CoInstallers]}
    inf: {Install Inf Section
    [LbAdapter.ndi.CoInstallers] exit (0x00000000)}
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:03.645
    dvi: CoInstaller 1: Enter 22:46:03.647
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:03.650
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:03.653
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:03.657
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)}
    22:46:03.661
    dvi: Co-installers registered.
    dvi: Default installer: Exit
    dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)}
    22:46:03.665
    ndv: Installing interfaces...
    dvi: {DIF_INSTALLINTERFACES} 22:46:03.667
    dvi: Using exported function 'NciDeviceInstall' in
    module 'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function
    'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 ==
    wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function
    'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 ==
    wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:03.679
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:03.682
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:03.685
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:03.689
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:03.692
    dvi: {Install INTERFACES}
    inf: Opened PNF:
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    dvi: Installing section
    [LbAdapter.ndi.Interfaces]
    dvi: {Install INTERFACES exit 00000000}
    dvi: Default installer: Exit
    dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 22:46:03.701
    ndv: Installing device...
    dvi: {DIF_INSTALLDEVICE} 22:46:03.704
    dvi: CoInstaller 1: Enter 22:46:03.705
    cci: NdisCoinst: NetCfgInstanceId does not exist
    cci: NdisCoinst: Guid of the adapter is
    {C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    inf: Opened PNF: 'C:\Windows\INF\oem26.inf'
    ([strings])
    cci: NdisCoinst: IfType from registry is 1
    cci: NdisCoinst: IfType 1, Characteristics 0x1,
    IsIrdaDevice 0, PhysicalMediaType -1, MediaType -1, IsBridge 0,
    FoundGuidInDownlevel 0, EnableDhcp 2
    cci: NdisCoinst: Connection name is Local Area
    Connection 3
    cci: NdisCoinst: NetLuidIndex does not exist
    !!! cci: NdisCoinst: NcipAllocateNetLuidIndex failed
    with error 0x5aa
    !!! dvi: CoInstaller 1: failed(0x000005aa)!
    !!! dvi: Error 1450: Insufficient system resources exist to
    complete the requested service.
    dvi: {DIF_INSTALLDEVICE - exit(0x000005aa)} 22:46:03.767
    !!! ndv: Error(000005aa) installing device!
    ndv: Device install status=0x000005aa
    ndv: Performing device install final cleanup...
    ! ndv: Queueing up error report since device installation
    failed...
    ndv: {Core Device Install - exit(0x000005aa)} 22:46:03.774
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:03.775
    dvi: CoInstaller 1: Enter 22:46:03.777
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:03.780
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:03.783
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:03.787
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 22:46:03.791
    ump: Server install process exited with code 0x000005aa
    22:46:03.822
    ump: {Plug and Play Service: Device Install exit(000005aa)}
    ndv: Device Install failed for new device...installing NULL driver.
    dvi: {Plug and Play Service: Device Install for ROOT\NET\0000}
    ump: Creating Install Process: DrvInst.exe 22:46:03.838
    ! ndv: Installing NULL driver!
    dvi: Set selected driver complete.
    dvi: {DIF_ALLOW_INSTALL} 22:46:03.975
    dvi: Using exported function 'NetClassInstaller' in module
    'C:\Windows\system32\NetCfgx.dll'.
    dvi: Class installer == NetCfgx.dll,NetClassInstaller
    dvi: Using exported function 'NciDeviceInstall' in module
    'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function 'WlanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 == wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function 'WwanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 == wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:04.004
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:04.008
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:04.010
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:04.012
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:04.019
    dvi: Default installer: Exit
    dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 22:46:04.022
    dvi: {DIF_INSTALLDEVICE} 22:46:04.024
    dvi: CoInstaller 1: Enter 22:46:04.026
    cci: NdisCoinst: Succesfully set NewDeviceInstall to 0
    cci: NdisCoinst: Null driver install
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:04.034
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:04.037
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:04.041
    cci: [NCI BEGIN INSTALL DEVICE for ROOT\NET\0000]
    cci: NCI: Null driver install.
    cci: NCI: NewDeviceInstall is 0. Assuming this is an
    update
    dvi: {DIF_REMOVE} 22:46:04.046
    dvi: CoInstaller 1: Enter 22:46:04.049
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:04.052
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:04.055
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:04.058
    cci: [NCI BEGIN REMOVE DEVICE for
    ROOT\NET\0000]
    cci: [NCI: BEGIN STORE EXTERNAL RESOURCE INFO]
    cci: NCI: IfType=1
    cci: NCI:
    NetcfgInstanceId(GUID)={C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    cci: [NCI: END STORE EXTERNAL RESOURCE INFO]
    dvi: {Remove DEVICE}
    dvi: InstanceID = 'ROOT\NET\0000'
    dvi: Devnode Status = 0x01802001
    dvi: CM_Query_And_Remove_Subtree_Ex
    returns 0x00000000
    dvi: Devnode Status after
    CM_Query_And_Remove_Subtree_Ex = 0x01802401
    dvi: Query-and-Remove succeeded
    dvi: {Delete DEVICE}
    dvi: Device Instance uninstalled.
    dvi: {Delete DEVICE exit (0x00000000)}
    dvi: {Remove DEVICE exit (0x00000000)}
    cci: NCI:Delayed Cleanup not required..
    DevInstallParams.Flags=0x00800000
    cci: NCI: Notifying binding engine of removal
    cci: NCI: INetCfg UnInstaller Interface asking
    for write lock. 22:46:04.180
    cci: NCI: INetCfg UnInstaller Interface
    acquired write lock. 22:46:04.182
    cci: NCI: Init Notify Object for ms_ndiscap
    cci: NCI: Init Notify Object for ms_ndiscap
    complete
    cci: NCI: Init Notify Object for ms_server
    cci: NCI: Init Notify Object for ms_server
    complete
    cci: NCI: Init Notify Object for ms_steelhead
    cci: NCI: Init Notify Object for ms_steelhead
    complete
    cci: NCI: Init Notify Object for ms_rassrv
    cci: NCI: Init Notify Object for ms_rassrv
    complete
    cci: NCI: Init Notify Object for ms_msclient
    cci: NCI: Init Notify Object for ms_msclient
    complete
    cci: NCI: Init Notify Object for ms_tcpip6
    cci: NCI: Init Notify Object for ms_tcpip6
    complete
    cci: NCI: Init Notify Object for ms_tcpip
    cci: NCI: Init Notify Object for ms_tcpip
    complete
    cci: NCI: Init Notify Object for ms_pppoe
    cci: NCI: Init Notify Object for ms_pppoe
    complete
    cci: NCI: Init Notify Object for ms_pptp
    cci: NCI: Init Notify Object for ms_pptp
    complete
    cci: NCI: Init Notify Object for ms_l2tp
    cci: NCI: Init Notify Object for ms_l2tp
    complete
    cci: NCI: Init Notify Object for ms_ndiswan
    cci: NCI: Init Notify Object for ms_ndiswan
    complete
    cci: NCI: Init Notify Object for ms_agilevpn
    cci: NCI: Init Notify Object for ms_agilevpn
    complete
    cci: NCI: Init Notify Object for ms_sstp
    cci: NCI: Init Notify Object for ms_sstp
    complete
    cci: [NCI: BEGIN Release Externally Managed
    Resources]
    cci: NCI: IfType=1
    cci: NCI:
    NetcfgInstanceId(GUID)={C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    ! cci: !NCI: IfType Present, NetLuidIndex NOT
    Present. pszPnpID= ROOT\NET\0000
    cci: NCI: Successfully deleted Connection
    Registry Key for GUID={C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    cci: [NCI: END Release Externally Managed
    Resources]
    cci: NCI: INetCfg UnInstaller Interface
    Released write lock. 22:46:04.937
    cci:

    cci: [NCI END REMOVE DEVICE for ROOT\NET\0000.
    Result 0x00000000]
    dvi: Class installer: Exit
    dvi: CoInstaller 1: Enter (Post Processing)
    22:46:04.945
    dvi: CoInstaller 1: Exit (Post Processing)
    dvi: {DIF_REMOVE - exit(0x00000000)} 22:46:04.948
    cci: [NCI END INSTALL DEVICE for ROOT\NET\0000]
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:04.952
    !!! dvi: Error obtaining device ID!
    !!! dvi: Cleaning up failed installation (00000006)
    ! dvi: Failed to set Config Flags property: 0x00000020
    ! dvi: Error 0xe000020b: The device instance does not
    exist in the hardware tree.
    !!! dvi: Default installer: failed!
    !!! dvi: Error 6: The handle is invalid.
    dvi: {DIF_INSTALLDEVICE - exit(0x00000006)} 22:46:04.962
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:04.964
    dvi: CoInstaller 1: Enter 22:46:04.966
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:04.969
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:04.972
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:04.975
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 22:46:04.979
    ump: Server install process exited with code 0x00000006
    22:46:04.986
    ump: {Plug and Play Service: Device Install exit(00000006)}
    dvi: {Build Driver List} 22:46:04.990
    ! dvi: Driver list already built
    dvi: {Build Driver List - exit(0x00000000)} 22:46:04.994
    dvi: {DIF_SELECTBESTCOMPATDRV} 22:46:04.996
    dvi: CoInstaller 1: Enter 22:46:04.998
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:05.000
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:05.002
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:05.006
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:05.009
    dvi: {Select Best Driver}
    dvi: Selected driver installs from section
    [LbAdapter.ndi] in 'c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf'.
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:05.014
    dvi: CoInstaller 1: Enter 22:46:05.016
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:05.019
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:05.023
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:05.026
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)}
    22:46:05.029
    dvi: Set selected driver complete.
    dvi: Selected:
    dvi: Description - [LAN Bridger Virtual Ethernet
    Adapter]
    dvi: InfFile - [c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf]
    dvi: Section - [LbAdapter.ndi]
    dvi: Signer - [Echobit, LLC]
    dvi: Rank - [0x00ff0000]
    dvi: {Select Best Driver - exit(0x00000000)}
    dvi: Default installer: Exit
    dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 22:46:05.043
    dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 22:46:05.044
    dvi: Using exported function 'NetClassInstaller' in module
    'C:\Windows\system32\NetCfgx.dll'.
    dvi: Class installer == NetCfgx.dll,NetClassInstaller
    dvi: Using exported function 'NciDeviceInstall' in module
    'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function 'WlanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 == wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function 'WwanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 == wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:05.062
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:05.065
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:05.069
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:05.072
    !!! dvi: Class installer: failed(0xe000020b)!
    !!! dvi: Error 0xe000020b: The device instance does not exist in the
    hardware tree.
    dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020b)}
    22:46:05.077
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:05.079
    dvi: CoInstaller 1: Enter 22:46:05.081
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:05.083
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:05.086
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:05.089
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 22:46:05.092 <<<
    Section end 2010/05/13 22:46:05.094 <<< [Exit status: SUCCESS]



    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • OSR_Community_UserOSR_Community_User Member Posts: 110,218
    Hi Jeffrey,

    I had the customer look up the registry key you mentioned, but it looked
    fine. I also had him take a look at the backup ControlSets but they looked
    fine as well:

    CurrentControlSet: 77 4b 00
    ControlSet001: 77 4b 00
    ControlSet002: 77 4b 02

    As far as I can tell, there's room in the bitmap for more unique ID numbers.
    Do you have any other ideas what could be causing NcipAllocateNetLuidIndex
    to fail?

    Thanks,
    Soren

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Jeffrey Tippet
    Sent: Saturday, May 15, 2010 11:49 AM
    To: Windows System Software Devs Interest List
    Subject: RE: [ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when
    installing

    I agree with your assessment -- the NcipAllocateNetLuidIndex bit looks to be
    the problem. I don't have a good guess as to what's gone wrong, but here's
    some background info that might help you figure it out. (This info is an
    implementation detail, subject to change, but may come in handy for
    troubleshooting):

    NDIS must allocate a (locally) unique number for each network interface, the
    NET_LUID. The NET_LUID consists of the ifType, paired with a unique ID
    number. To generate that unique ID, we keep track of the IDs that have
    already been assigned in

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NDIS\IfTypes\[ifType] !
    IfUsedNetLuidIndices (REG_BINARY)
    for each ifType. For example, look in \6 if your NIC is Ethernet
    (ifType==6).

    In there, there is IfUsedNetLuidIndices, which is (IIRC) a bitmap of the
    unique IDs that have been assigned to other network interfaces. Make sure
    this value is present and not damaged (e.g., a huge number of 0xFF's).
    Typically, its value will be something like 0xFF 0x01, if you have 9 NICs.
    Note that you can't just whack this value and replace it with something
    else, since then NDIS will incorrectly assign the same NET_LUID to two
    interfaces, and all sorts of things will break when that happens.

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Soren Dreijer
    Sent: Thursday, May 13, 2010 7:29 PM
    To: Windows System Software Devs Interest List
    Subject: [ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when installing

    Hey al,

    We have a customer who is experiencing problems installing our NDIS miniport
    driver. He's getting error 1450 (ERROR_NO_SYSTEM_RESOURCES), but states he
    has plenty of disk space, etc. available. Looking through the setupapi.log
    tells me two things:

    1. There seem to be some certificate issues, but I'm seeing similar
    errors/warnings on my machine, so my guess is that they're perhaps related
    to WHQL (our driver isn't WHQL-certified).

    2. The following piece of the log worries me:

    ndv: Installing device...
    dvi: {DIF_INSTALLDEVICE} 22:46:03.704
    dvi: CoInstaller 1: Enter 22:46:03.705
    cci: NdisCoinst: NetCfgInstanceId does not exist
    cci: NdisCoinst: Guid of the adapter is
    {C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    inf: Opened PNF: 'C:\Windows\INF\oem26.inf'
    ([strings])
    cci: NdisCoinst: IfType from registry is 1
    cci: NdisCoinst: IfType 1, Characteristics 0x1,
    IsIrdaDevice 0, PhysicalMediaType -1, MediaType -1, IsBridge 0,
    FoundGuidInDownlevel 0, EnableDhcp 2
    cci: NdisCoinst: Connection name is Local Area
    Connection 3
    cci: NdisCoinst: NetLuidIndex does not exist
    !!! cci: NdisCoinst: NcipAllocateNetLuidIndex failed
    with error 0x5aa
    !!! dvi: CoInstaller 1: failed(0x000005aa)!
    !!! dvi: Error 1450: Insufficient system resources exist to
    complete the requested service.
    dvi: {DIF_INSTALLDEVICE - exit(0x000005aa)} 22:46:03.767
    !!! ndv: Error(000005aa) installing device!
    ndv: Device install status=0x000005aa
    ndv: Performing device install final cleanup...
    ! ndv: Queueing up error report since device installation
    failed...

    I'm hoping some trained eyes here from NTDEV might see something in the log
    that I don't. I've included the full setupapi.log below.

    Thanks,
    Soren

    [Device Install Log]
    OS Version = 6.1.7600
    Service Pack = 0.0
    Suite = 0x0100
    ProductType = 1
    Architecture = amd64

    [BeginLog]



    >>> [Device Install (UpdateDriverForPlugAndPlayDevices) -
    >>> root\LbAdapter] Section start 2010/05/13 22:45:59.836
    cmd: "C:\Program Files\Echobit\LAN Bridger\installer_helper_x64.exe"
    install "C:\Program Files\Echobit\LAN Bridger\Driver\netLB_x64.inf"
    "root\LbAdapter"
    dvi: Set selected driver complete.
    dvi: {Build Driver List} 22:46:00.748
    cpy: Policy is set to make all digital signatures equal.
    dvi: Processing a single INF: 'c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf'
    inf: Opened INF: 'c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf' ([strings])
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:00.755
    sig: Key = netlb_x64.inf
    sig: FilePath = c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf
    sig: Catalog = c:\program files\echobit\lan
    bridger\driver\netLB_x64.cat
    flq: {SPFILENOTIFY_CABINETINFO}
    flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)}
    flq: {SPFILENOTIFY_FILEEXTRACTED}
    flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)}
    ! sig: Verifying file against specific (valid) catalog failed!
    (0x800b0109)
    ! sig: Error 0x800b0109: A certificate chain processed, but
    terminated in a root certificate which is not trusted by the trust provider.
    sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 22:46:01.061
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:01.062
    sig: Key = netlb_x64.inf
    sig: FilePath = c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf
    sig: Catalog = c:\program files\echobit\lan
    bridger\driver\netLB_x64.cat
    sig: Success: File is signed in Authenticode(tm) catalog.
    sig: Error 0xe0000242: The publisher of an Authenticode(tm)
    signed catalog has not yet been established as trusted.
    sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 22:46:01.099
    dvi: Created Driver Node:
    dvi: HardwareID - root\LbAdapter
    dvi: InfName - c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf
    dvi: DevDesc - LAN Bridger Virtual Ethernet Adapter
    dvi: DrvDesc - LAN Bridger Virtual Ethernet Adapter
    dvi: Provider - Echobit LLC
    dvi: Mfg - Echobit LLC
    dvi: ModelsSec - Lb.NTamd64
    dvi: InstallSec - LbAdapter.ndi
    dvi: ActualSec - LbAdapter.ndi
    dvi: Rank - 0x00ff0000
    dvi: Signer - Echobit, LLC
    dvi: Signer Score - Authenticode
    dvi: DrvDate - 11/01/2008
    dvi: Version - 6.0.0.1
    dvi: {Build Driver List - exit(0x00000000)} 22:46:01.125
    dvi: {DIF_SELECTBESTCOMPATDRV} 22:46:01.126
    dvi: Using exported function 'NetClassInstaller' in module
    'C:\Windows\system32\NetCfgx.dll'.
    dvi: Class installer == NetCfgx.dll,NetClassInstaller
    dvi: Using exported function 'NciDeviceInstall' in module
    'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function 'WlanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 == wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function 'WwanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 == wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:01.142
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:01.145
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:01.149
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:01.152
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:01.155
    dvi: {Select Best Driver}
    dvi: Selected driver installs from section
    [LbAdapter.ndi] in 'c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf'.
    dvi: Set selected driver complete.
    dvi: Selected:
    dvi: Description - [LAN Bridger Virtual Ethernet
    Adapter]
    dvi: InfFile - [c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf]
    dvi: Section - [LbAdapter.ndi]
    dvi: Signer - [Echobit, LLC]
    dvi: Rank - [0x00ff0000]
    dvi: {Select Best Driver - exit(0x00000000)}
    dvi: Default installer: Exit
    dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 22:46:01.171
    inf: {SetupCopyOEMInf: c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf} 22:46:01.172
    ! inf: Package was already in store: skipping Driver Store add
    inf: {SetupCopyOEMInf exit (0x00000000)} 22:46:01.852
    inf: Opened PNF:
    'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:01.861
    sig: Key = netlb_x64.inf
    sig: FilePath =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netlb_x64.inf
    sig: Catalog =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netLB_x64.cat
    ! sig: Verifying file against specific (valid) catalog failed!
    (0x800b0109)
    ! sig: Error 0x800b0109: A certificate chain processed, but
    terminated in a root certificate which is not trusted by the trust provider.
    sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 22:46:01.881
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:01.882
    sig: Key = netlb_x64.inf
    sig: FilePath =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netlb_x64.inf
    sig: Catalog =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netLB_x64.cat
    sig: Success: File is signed in Authenticode(tm) catalog.
    sig: Error 0xe0000242: The publisher of an Authenticode(tm) signed
    catalog has not yet been established as trusted.
    sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 22:46:01.919
    dvi: Selected driver installs from section [LbAdapter.ndi] in
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf'.
    dvi: Set selected driver complete.
    dvi: {Plug and Play Service: Device Install for ROOT\NET\0000}
    ump: Creating Install Process: DrvInst.exe 22:46:02.109
    ndv: Infpath=C:\Windows\INF\oem26.inf
    ndv:
    DriverNodeName=netlb_x64.inf:Lb.NTamd64:LbAdapter.ndi:6.0.0.1:root\lbadapter
    ndv:
    DriverStorepath=C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf
    _amd64_neutral_41ce5dbcf7c93cc8\netlb_x64.inf
    ndv: Building driver list from driver node strong name...
    inf: Opened PNF:
    'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:02.559
    sig: Key = netlb_x64.inf
    sig: FilePath =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netlb_x64.inf
    sig: Catalog =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netLB_x64.cat
    flq: {SPFILENOTIFY_CABINETINFO}
    flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)}
    flq: {SPFILENOTIFY_FILEEXTRACTED}
    flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)}
    ! sig: Verifying file against specific (valid) catalog failed!
    (0x800b0109)
    ! sig: Error 0x800b0109: A certificate chain processed, but
    terminated in a root certificate which is not trusted by the trust provider.
    sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 22:46:02.648
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:02.649
    sig: Key = netlb_x64.inf
    sig: FilePath =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netlb_x64.inf
    sig: Catalog =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netLB_x64.cat
    sig: Success: File is signed in Authenticode(tm) catalog.
    sig: Error 0xe0000242: The publisher of an Authenticode(tm)
    signed catalog has not yet been established as trusted.
    sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 22:46:02.686
    dvi: Selected driver installs from section [LbAdapter.ndi] in
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf'.
    dvi: Set selected driver complete.
    ndv: {Core Device Install} 22:46:02.691
    inf: Opened PNF: 'C:\Windows\INF\oem26.inf' ([strings])
    dvi: {DIF_ALLOW_INSTALL} 22:46:02.809
    dvi: Using exported function 'NetClassInstaller' in
    module 'C:\Windows\system32\NetCfgx.dll'.
    dvi: Class installer == NetCfgx.dll,NetClassInstaller
    dvi: Using exported function 'NciDeviceInstall' in
    module 'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function
    'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 ==
    wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function
    'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 ==
    wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:02.830
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:02.833
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:02.835
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:02.839
    inf: Opened PNF: 'C:\Windows\INF\oem26.inf'
    ([strings])
    inf: AddReg=LbAdapter.Reg (oem26.inf line 33)
    inf: AddReg=LbAdapter.Reg.Adapter.Params
    (oem26.inf line 34)
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:02.917
    dvi: Default installer: Exit
    dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 22:46:02.920
    ndv: Installing files...
    dvi: {DIF_INSTALLDEVICEFILES} 22:46:02.924
    dvi: CoInstaller 1: Enter 22:46:02.926
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:02.930
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:02.933
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:02.936
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:02.940
    dvi: {Install FILES}
    inf: Opened PNF:
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    inf: {Install Inf Section [LbAdapter.ndi]}
    inf: CopyFiles=LbAdapter.CopyFiles
    (netlb_x64.inf line 35)
    cpy: Open PnpLockdownPolicy: Err=2. This
    is OK. Use LockDownPolicyDefault
    flq: QueueSingleCopy...
    flq: Inf :
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf'
    flq: SourceInf:
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf'
    flq: SourceSection: [sourcedisksfiles]
    flq: Source root path based on SourceInf
    flq: SourceRootPath:
    'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8'
    flq: {FILE_QUEUE_COPY}
    flq: CopyStyle - 0x00000400
    flq: {FILE_QUEUE_COPY}
    flq: CopyStyle -
    0x00000400
    flq: SourceRootPath -
    'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8'
    flq: SourceFilename - 'lb.sys'
    flq: TargetDirectory-
    'C:\Windows\system32\DRIVERS'
    flq: TargetFilename - 'lb.sys'
    flq: SourceDesc - 'LAN
    Bridger Virtual Ethernet Adapter Installation Disk'
    flq: {FILE_QUEUE_COPY
    exit(0x00000000)}
    flq: {FILE_QUEUE_COPY exit(0x00000000)}
    inf: {Install Inf Section [LbAdapter.ndi] exit
    (0x00000000)}
    dvi: Processing co-installer registration
    section [LbAdapter.ndi.CoInstallers].
    inf: {Install Inf Section
    [LbAdapter.ndi.CoInstallers]}
    inf: {Install Inf Section
    [LbAdapter.ndi.CoInstallers] exit (0x00000000)}
    dvi: Co-installers registered.
    dvi: {Install INTERFACES}
    dvi: Installing section
    [LbAdapter.ndi.Interfaces]
    dvi: {Install INTERFACES exit 00000000}
    dvi: {Install FILES exit (0x00000000)}
    dvi: Default installer: Exit
    dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 22:46:02.988
    ndv: Pruning file queue...
    dvi: {_SCAN_FILE_QUEUE}
    flq: ScanQ flags=620
    flq: SPQ_SCAN_PRUNE_COPY_QUEUE
    flq: SPQ_SCAN_FILE_COMPARISON
    flq: SPQ_SCAN_ACTIVATE_DRP
    flq: ScanQ number of copy nodes=1
    flq: File 'C:\Windows\system32\DRIVERS\lb.sys' pruned
    from copy.
    sig: Using catalog
    'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem26.CA
    T'.
    flq: {SPFILENOTIFY_CABINETINFO}
    flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)}
    flq: {SPFILENOTIFY_FILEEXTRACTED}
    flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)}
    ! sig: VerifyTrustFailed for
    C:\Windows\system32\DRIVERS\lb.sys.
    ! sig: Error 0x800b0109: A certificate chain processed,
    but terminated in a root certificate which is not trusted by the trust
    provider.
    cpy: DrpSetRegFileProt
    'C:\Windows\system32\DRIVERS\lb.sys' Status=0 Class=OEM Legacy
    flq: ScanQ action=200 DoPruning=32
    flq: ScanQ end Validity flags=620 CopyNodes=0
    dvi: {_SCAN_FILE_QUEUE exit(0, 0x00000000)}
    ndv: Committing file queue...
    flq: {_commit_file_queue}
    flq: CommitQ DelNodes=0 RenNodes=0 CopyNodes=0
    flq: CommitQ early exit: No nodes are queued
    flq: {_commit_file_queue exit OK}
    ndv: Registering CoInstallers...
    dvi: {DIF_REGISTER_COINSTALLERS} 22:46:03.581
    dvi: CoInstaller 1: Enter 22:46:03.583
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:03.586
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:03.589
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:03.591
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:03.594
    inf: Opened PNF:
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    inf: {Install Inf Section
    [LbAdapter.ndi.CoInstallers]}
    inf: {Install Inf Section
    [LbAdapter.ndi.CoInstallers] exit (0x00000000)}
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:03.645
    dvi: CoInstaller 1: Enter 22:46:03.647
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:03.650
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:03.653
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:03.657
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)}
    22:46:03.661
    dvi: Co-installers registered.
    dvi: Default installer: Exit
    dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)}
    22:46:03.665
    ndv: Installing interfaces...
    dvi: {DIF_INSTALLINTERFACES} 22:46:03.667
    dvi: Using exported function 'NciDeviceInstall' in
    module 'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function
    'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 ==
    wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function
    'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 ==
    wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:03.679
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:03.682
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:03.685
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:03.689
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:03.692
    dvi: {Install INTERFACES}
    inf: Opened PNF:
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    dvi: Installing section
    [LbAdapter.ndi.Interfaces]
    dvi: {Install INTERFACES exit 00000000}
    dvi: Default installer: Exit
    dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 22:46:03.701
    ndv: Installing device...
    dvi: {DIF_INSTALLDEVICE} 22:46:03.704
    dvi: CoInstaller 1: Enter 22:46:03.705
    cci: NdisCoinst: NetCfgInstanceId does not exist
    cci: NdisCoinst: Guid of the adapter is
    {C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    inf: Opened PNF: 'C:\Windows\INF\oem26.inf'
    ([strings])
    cci: NdisCoinst: IfType from registry is 1
    cci: NdisCoinst: IfType 1, Characteristics 0x1,
    IsIrdaDevice 0, PhysicalMediaType -1, MediaType -1, IsBridge 0,
    FoundGuidInDownlevel 0, EnableDhcp 2
    cci: NdisCoinst: Connection name is Local Area
    Connection 3
    cci: NdisCoinst: NetLuidIndex does not exist
    !!! cci: NdisCoinst: NcipAllocateNetLuidIndex failed
    with error 0x5aa
    !!! dvi: CoInstaller 1: failed(0x000005aa)!
    !!! dvi: Error 1450: Insufficient system resources exist to
    complete the requested service.
    dvi: {DIF_INSTALLDEVICE - exit(0x000005aa)} 22:46:03.767
    !!! ndv: Error(000005aa) installing device!
    ndv: Device install status=0x000005aa
    ndv: Performing device install final cleanup...
    ! ndv: Queueing up error report since device installation
    failed...
    ndv: {Core Device Install - exit(0x000005aa)} 22:46:03.774
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:03.775
    dvi: CoInstaller 1: Enter 22:46:03.777
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:03.780
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:03.783
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:03.787
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 22:46:03.791
    ump: Server install process exited with code 0x000005aa
    22:46:03.822
    ump: {Plug and Play Service: Device Install exit(000005aa)}
    ndv: Device Install failed for new device...installing NULL driver.
    dvi: {Plug and Play Service: Device Install for ROOT\NET\0000}
    ump: Creating Install Process: DrvInst.exe 22:46:03.838
    ! ndv: Installing NULL driver!
    dvi: Set selected driver complete.
    dvi: {DIF_ALLOW_INSTALL} 22:46:03.975
    dvi: Using exported function 'NetClassInstaller' in module
    'C:\Windows\system32\NetCfgx.dll'.
    dvi: Class installer == NetCfgx.dll,NetClassInstaller
    dvi: Using exported function 'NciDeviceInstall' in module
    'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function 'WlanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 == wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function 'WwanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 == wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:04.004
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:04.008
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:04.010
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:04.012
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:04.019
    dvi: Default installer: Exit
    dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 22:46:04.022
    dvi: {DIF_INSTALLDEVICE} 22:46:04.024
    dvi: CoInstaller 1: Enter 22:46:04.026
    cci: NdisCoinst: Succesfully set NewDeviceInstall to 0
    cci: NdisCoinst: Null driver install
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:04.034
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:04.037
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:04.041
    cci: [NCI BEGIN INSTALL DEVICE for ROOT\NET\0000]
    cci: NCI: Null driver install.
    cci: NCI: NewDeviceInstall is 0. Assuming this is an
    update
    dvi: {DIF_REMOVE} 22:46:04.046
    dvi: CoInstaller 1: Enter 22:46:04.049
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:04.052
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:04.055
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:04.058
    cci: [NCI BEGIN REMOVE DEVICE for
    ROOT\NET\0000]
    cci: [NCI: BEGIN STORE EXTERNAL RESOURCE INFO]
    cci: NCI: IfType=1
    cci: NCI:
    NetcfgInstanceId(GUID)={C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    cci: [NCI: END STORE EXTERNAL RESOURCE INFO]
    dvi: {Remove DEVICE}
    dvi: InstanceID = 'ROOT\NET\0000'
    dvi: Devnode Status = 0x01802001
    dvi: CM_Query_And_Remove_Subtree_Ex
    returns 0x00000000
    dvi: Devnode Status after
    CM_Query_And_Remove_Subtree_Ex = 0x01802401
    dvi: Query-and-Remove succeeded
    dvi: {Delete DEVICE}
    dvi: Device Instance uninstalled.
    dvi: {Delete DEVICE exit (0x00000000)}
    dvi: {Remove DEVICE exit (0x00000000)}
    cci: NCI:Delayed Cleanup not required..
    DevInstallParams.Flags=0x00800000
    cci: NCI: Notifying binding engine of removal
    cci: NCI: INetCfg UnInstaller Interface asking
    for write lock. 22:46:04.180
    cci: NCI: INetCfg UnInstaller Interface
    acquired write lock. 22:46:04.182
    cci: NCI: Init Notify Object for ms_ndiscap
    cci: NCI: Init Notify Object for ms_ndiscap
    complete
    cci: NCI: Init Notify Object for ms_server
    cci: NCI: Init Notify Object for ms_server
    complete
    cci: NCI: Init Notify Object for ms_steelhead
    cci: NCI: Init Notify Object for ms_steelhead
    complete
    cci: NCI: Init Notify Object for ms_rassrv
    cci: NCI: Init Notify Object for ms_rassrv
    complete
    cci: NCI: Init Notify Object for ms_msclient
    cci: NCI: Init Notify Object for ms_msclient
    complete
    cci: NCI: Init Notify Object for ms_tcpip6
    cci: NCI: Init Notify Object for ms_tcpip6
    complete
    cci: NCI: Init Notify Object for ms_tcpip
    cci: NCI: Init Notify Object for ms_tcpip
    complete
    cci: NCI: Init Notify Object for ms_pppoe
    cci: NCI: Init Notify Object for ms_pppoe
    complete
    cci: NCI: Init Notify Object for ms_pptp
    cci: NCI: Init Notify Object for ms_pptp
    complete
    cci: NCI: Init Notify Object for ms_l2tp
    cci: NCI: Init Notify Object for ms_l2tp
    complete
    cci: NCI: Init Notify Object for ms_ndiswan
    cci: NCI: Init Notify Object for ms_ndiswan
    complete
    cci: NCI: Init Notify Object for ms_agilevpn
    cci: NCI: Init Notify Object for ms_agilevpn
    complete
    cci: NCI: Init Notify Object for ms_sstp
    cci: NCI: Init Notify Object for ms_sstp
    complete
    cci: [NCI: BEGIN Release Externally Managed
    Resources]
    cci: NCI: IfType=1
    cci: NCI:
    NetcfgInstanceId(GUID)={C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    ! cci: !NCI: IfType Present, NetLuidIndex NOT
    Present. pszPnpID= ROOT\NET\0000
    cci: NCI: Successfully deleted Connection
    Registry Key for GUID={C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    cci: [NCI: END Release Externally Managed
    Resources]
    cci: NCI: INetCfg UnInstaller Interface
    Released write lock. 22:46:04.937
    cci:

    cci: [NCI END REMOVE DEVICE for ROOT\NET\0000.
    Result 0x00000000]
    dvi: Class installer: Exit
    dvi: CoInstaller 1: Enter (Post Processing)
    22:46:04.945
    dvi: CoInstaller 1: Exit (Post Processing)
    dvi: {DIF_REMOVE - exit(0x00000000)} 22:46:04.948
    cci: [NCI END INSTALL DEVICE for ROOT\NET\0000]
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:04.952
    !!! dvi: Error obtaining device ID!
    !!! dvi: Cleaning up failed installation (00000006)
    ! dvi: Failed to set Config Flags property: 0x00000020
    ! dvi: Error 0xe000020b: The device instance does not
    exist in the hardware tree.
    !!! dvi: Default installer: failed!
    !!! dvi: Error 6: The handle is invalid.
    dvi: {DIF_INSTALLDEVICE - exit(0x00000006)} 22:46:04.962
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:04.964
    dvi: CoInstaller 1: Enter 22:46:04.966
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:04.969
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:04.972
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:04.975
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 22:46:04.979
    ump: Server install process exited with code 0x00000006
    22:46:04.986
    ump: {Plug and Play Service: Device Install exit(00000006)}
    dvi: {Build Driver List} 22:46:04.990
    ! dvi: Driver list already built
    dvi: {Build Driver List - exit(0x00000000)} 22:46:04.994
    dvi: {DIF_SELECTBESTCOMPATDRV} 22:46:04.996
    dvi: CoInstaller 1: Enter 22:46:04.998
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:05.000
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:05.002
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:05.006
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:05.009
    dvi: {Select Best Driver}
    dvi: Selected driver installs from section
    [LbAdapter.ndi] in 'c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf'.
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:05.014
    dvi: CoInstaller 1: Enter 22:46:05.016
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:05.019
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:05.023
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:05.026
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)}
    22:46:05.029
    dvi: Set selected driver complete.
    dvi: Selected:
    dvi: Description - [LAN Bridger Virtual Ethernet
    Adapter]
    dvi: InfFile - [c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf]
    dvi: Section - [LbAdapter.ndi]
    dvi: Signer - [Echobit, LLC]
    dvi: Rank - [0x00ff0000]
    dvi: {Select Best Driver - exit(0x00000000)}
    dvi: Default installer: Exit
    dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 22:46:05.043
    dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 22:46:05.044
    dvi: Using exported function 'NetClassInstaller' in module
    'C:\Windows\system32\NetCfgx.dll'.
    dvi: Class installer == NetCfgx.dll,NetClassInstaller
    dvi: Using exported function 'NciDeviceInstall' in module
    'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function 'WlanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 == wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function 'WwanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 == wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:05.062
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:05.065
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:05.069
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:05.072
    !!! dvi: Class installer: failed(0xe000020b)!
    !!! dvi: Error 0xe000020b: The device instance does not exist in the
    hardware tree.
    dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020b)}
    22:46:05.077
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:05.079
    dvi: CoInstaller 1: Enter 22:46:05.081
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:05.083
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:05.086
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:05.089
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 22:46:05.092 <<<
    Section end 2010/05/13 22:46:05.094 <<< [Exit status: SUCCESS]



    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • Soren_DreijerSoren_Dreijer Member Posts: 80
    Alright, so looking at the IfType 1 in the registry indicated the problem. I see a very long binary value with all FF's, which means the bitmap is full. How do I best go about cleaning this up on the customer's computer? Ideally, he shouldn't have any IF_TYPE_OTHER devices at all, should he? If so, maybe I can just set it back to 0?

    Cheers,
    Soren
  • Jeffrey_Tippet_[MSFT]Jeffrey_Tippet_[MSFT] Member - All Emails Posts: 450
    Sorry, AFAIK, that registry value is the only point of failure that would cause that error code. (Aside from a severe shortage of free memory, but you already checked that). I don't have any other guesses.

    -----Original Message-----
    From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Soren Dreijer
    Sent: Sunday, May 16, 2010 8:44 AM
    To: Windows System Software Devs Interest List
    Subject: RE: [ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when installing

    Hi Jeffrey,

    I had the customer look up the registry key you mentioned, but it looked fine. I also had him take a look at the backup ControlSets but they looked fine as well:

    CurrentControlSet: 77 4b 00
    ControlSet001: 77 4b 00
    ControlSet002: 77 4b 02

    As far as I can tell, there's room in the bitmap for more unique ID numbers.
    Do you have any other ideas what could be causing NcipAllocateNetLuidIndex to fail?

    Thanks,
    Soren

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Jeffrey Tippet
    Sent: Saturday, May 15, 2010 11:49 AM
    To: Windows System Software Devs Interest List
    Subject: RE: [ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when installing

    I agree with your assessment -- the NcipAllocateNetLuidIndex bit looks to be the problem. I don't have a good guess as to what's gone wrong, but here's some background info that might help you figure it out. (This info is an implementation detail, subject to change, but may come in handy for
    troubleshooting):

    NDIS must allocate a (locally) unique number for each network interface, the NET_LUID. The NET_LUID consists of the ifType, paired with a unique ID number. To generate that unique ID, we keep track of the IDs that have already been assigned in

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NDIS\IfTypes\[ifType] !
    IfUsedNetLuidIndices (REG_BINARY)
    for each ifType. For example, look in \6 if your NIC is Ethernet (ifType==6).

    In there, there is IfUsedNetLuidIndices, which is (IIRC) a bitmap of the unique IDs that have been assigned to other network interfaces. Make sure this value is present and not damaged (e.g., a huge number of 0xFF's).
    Typically, its value will be something like 0xFF 0x01, if you have 9 NICs.
    Note that you can't just whack this value and replace it with something else, since then NDIS will incorrectly assign the same NET_LUID to two interfaces, and all sorts of things will break when that happens.

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Soren Dreijer
    Sent: Thursday, May 13, 2010 7:29 PM
    To: Windows System Software Devs Interest List
    Subject: [ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when installing

    Hey al,

    We have a customer who is experiencing problems installing our NDIS miniport driver. He's getting error 1450 (ERROR_NO_SYSTEM_RESOURCES), but states he has plenty of disk space, etc. available. Looking through the setupapi.log tells me two things:

    1. There seem to be some certificate issues, but I'm seeing similar errors/warnings on my machine, so my guess is that they're perhaps related to WHQL (our driver isn't WHQL-certified).

    2. The following piece of the log worries me:

    ndv: Installing device...
    dvi: {DIF_INSTALLDEVICE} 22:46:03.704
    dvi: CoInstaller 1: Enter 22:46:03.705
    cci: NdisCoinst: NetCfgInstanceId does not exist
    cci: NdisCoinst: Guid of the adapter is
    {C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    inf: Opened PNF: 'C:\Windows\INF\oem26.inf'
    ([strings])
    cci: NdisCoinst: IfType from registry is 1
    cci: NdisCoinst: IfType 1, Characteristics 0x1,
    IsIrdaDevice 0, PhysicalMediaType -1, MediaType -1, IsBridge 0, FoundGuidInDownlevel 0, EnableDhcp 2
    cci: NdisCoinst: Connection name is Local Area
    Connection 3
    cci: NdisCoinst: NetLuidIndex does not exist
    !!! cci: NdisCoinst: NcipAllocateNetLuidIndex failed
    with error 0x5aa
    !!! dvi: CoInstaller 1: failed(0x000005aa)!
    !!! dvi: Error 1450: Insufficient system resources exist to
    complete the requested service.
    dvi: {DIF_INSTALLDEVICE - exit(0x000005aa)} 22:46:03.767
    !!! ndv: Error(000005aa) installing device!
    ndv: Device install status=0x000005aa
    ndv: Performing device install final cleanup...
    ! ndv: Queueing up error report since device installation
    failed...

    I'm hoping some trained eyes here from NTDEV might see something in the log that I don't. I've included the full setupapi.log below.

    Thanks,
    Soren

    [Device Install Log]
    OS Version = 6.1.7600
    Service Pack = 0.0
    Suite = 0x0100
    ProductType = 1
    Architecture = amd64

    [BeginLog]



    >>> [Device Install (UpdateDriverForPlugAndPlayDevices) -
    >>> root\LbAdapter] Section start 2010/05/13 22:45:59.836
    cmd: "C:\Program Files\Echobit\LAN Bridger\installer_helper_x64.exe"
    install "C:\Program Files\Echobit\LAN Bridger\Driver\netLB_x64.inf"
    "root\LbAdapter"
    dvi: Set selected driver complete.
    dvi: {Build Driver List} 22:46:00.748
    cpy: Policy is set to make all digital signatures equal.
    dvi: Processing a single INF: 'c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf'
    inf: Opened INF: 'c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf' ([strings])
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:00.755
    sig: Key = netlb_x64.inf
    sig: FilePath = c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf
    sig: Catalog = c:\program files\echobit\lan
    bridger\driver\netLB_x64.cat
    flq: {SPFILENOTIFY_CABINETINFO}
    flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)}
    flq: {SPFILENOTIFY_FILEEXTRACTED}
    flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)}
    ! sig: Verifying file against specific (valid) catalog failed!
    (0x800b0109)
    ! sig: Error 0x800b0109: A certificate chain processed, but
    terminated in a root certificate which is not trusted by the trust provider.
    sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 22:46:01.061
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:01.062
    sig: Key = netlb_x64.inf
    sig: FilePath = c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf
    sig: Catalog = c:\program files\echobit\lan
    bridger\driver\netLB_x64.cat
    sig: Success: File is signed in Authenticode(tm) catalog.
    sig: Error 0xe0000242: The publisher of an Authenticode(tm)
    signed catalog has not yet been established as trusted.
    sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 22:46:01.099
    dvi: Created Driver Node:
    dvi: HardwareID - root\LbAdapter
    dvi: InfName - c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf
    dvi: DevDesc - LAN Bridger Virtual Ethernet Adapter
    dvi: DrvDesc - LAN Bridger Virtual Ethernet Adapter
    dvi: Provider - Echobit LLC
    dvi: Mfg - Echobit LLC
    dvi: ModelsSec - Lb.NTamd64
    dvi: InstallSec - LbAdapter.ndi
    dvi: ActualSec - LbAdapter.ndi
    dvi: Rank - 0x00ff0000
    dvi: Signer - Echobit, LLC
    dvi: Signer Score - Authenticode
    dvi: DrvDate - 11/01/2008
    dvi: Version - 6.0.0.1
    dvi: {Build Driver List - exit(0x00000000)} 22:46:01.125
    dvi: {DIF_SELECTBESTCOMPATDRV} 22:46:01.126
    dvi: Using exported function 'NetClassInstaller' in module
    'C:\Windows\system32\NetCfgx.dll'.
    dvi: Class installer == NetCfgx.dll,NetClassInstaller
    dvi: Using exported function 'NciDeviceInstall' in module
    'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function 'WlanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 == wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function 'WwanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 == wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:01.142
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:01.145
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:01.149
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:01.152
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:01.155
    dvi: {Select Best Driver}
    dvi: Selected driver installs from section
    [LbAdapter.ndi] in 'c:\program files\echobit\lan bridger\driver\netlb_x64.inf'.
    dvi: Set selected driver complete.
    dvi: Selected:
    dvi: Description - [LAN Bridger Virtual Ethernet
    Adapter]
    dvi: InfFile - [c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf]
    dvi: Section - [LbAdapter.ndi]
    dvi: Signer - [Echobit, LLC]
    dvi: Rank - [0x00ff0000]
    dvi: {Select Best Driver - exit(0x00000000)}
    dvi: Default installer: Exit
    dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 22:46:01.171
    inf: {SetupCopyOEMInf: c:\program files\echobit\lan bridger\driver\netlb_x64.inf} 22:46:01.172
    ! inf: Package was already in store: skipping Driver Store add
    inf: {SetupCopyOEMInf exit (0x00000000)} 22:46:01.852
    inf: Opened PNF:
    'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:01.861
    sig: Key = netlb_x64.inf
    sig: FilePath =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netlb_x64.inf
    sig: Catalog =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netLB_x64.cat
    ! sig: Verifying file against specific (valid) catalog failed!
    (0x800b0109)
    ! sig: Error 0x800b0109: A certificate chain processed, but
    terminated in a root certificate which is not trusted by the trust provider.
    sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 22:46:01.881
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:01.882
    sig: Key = netlb_x64.inf
    sig: FilePath =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netlb_x64.inf
    sig: Catalog =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netLB_x64.cat
    sig: Success: File is signed in Authenticode(tm) catalog.
    sig: Error 0xe0000242: The publisher of an Authenticode(tm) signed
    catalog has not yet been established as trusted.
    sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 22:46:01.919
    dvi: Selected driver installs from section [LbAdapter.ndi] in 'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf'.
    dvi: Set selected driver complete.
    dvi: {Plug and Play Service: Device Install for ROOT\NET\0000}
    ump: Creating Install Process: DrvInst.exe 22:46:02.109
    ndv: Infpath=C:\Windows\INF\oem26.inf
    ndv:
    DriverNodeName=netlb_x64.inf:Lb.NTamd64:LbAdapter.ndi:6.0.0.1:root\lbadapter
    ndv:
    DriverStorepath=C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf
    _amd64_neutral_41ce5dbcf7c93cc8\netlb_x64.inf
    ndv: Building driver list from driver node strong name...
    inf: Opened PNF:
    'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:02.559
    sig: Key = netlb_x64.inf
    sig: FilePath =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netlb_x64.inf
    sig: Catalog =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netLB_x64.cat
    flq: {SPFILENOTIFY_CABINETINFO}
    flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)}
    flq: {SPFILENOTIFY_FILEEXTRACTED}
    flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)}
    ! sig: Verifying file against specific (valid) catalog failed!
    (0x800b0109)
    ! sig: Error 0x800b0109: A certificate chain processed, but
    terminated in a root certificate which is not trusted by the trust provider.
    sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 22:46:02.648
    sig: {_VERIFY_FILE_SIGNATURE} 22:46:02.649
    sig: Key = netlb_x64.inf
    sig: FilePath =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netlb_x64.inf
    sig: Catalog =
    C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_4
    1ce5dbcf7c93cc8\netLB_x64.cat
    sig: Success: File is signed in Authenticode(tm) catalog.
    sig: Error 0xe0000242: The publisher of an Authenticode(tm)
    signed catalog has not yet been established as trusted.
    sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 22:46:02.686
    dvi: Selected driver installs from section [LbAdapter.ndi] in
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf'.
    dvi: Set selected driver complete.
    ndv: {Core Device Install} 22:46:02.691
    inf: Opened PNF: 'C:\Windows\INF\oem26.inf' ([strings])
    dvi: {DIF_ALLOW_INSTALL} 22:46:02.809
    dvi: Using exported function 'NetClassInstaller' in
    module 'C:\Windows\system32\NetCfgx.dll'.
    dvi: Class installer == NetCfgx.dll,NetClassInstaller
    dvi: Using exported function 'NciDeviceInstall' in
    module 'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function
    'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 ==
    wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function
    'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 ==
    wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:02.830
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:02.833
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:02.835
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:02.839
    inf: Opened PNF: 'C:\Windows\INF\oem26.inf'
    ([strings])
    inf: AddReg=LbAdapter.Reg (oem26.inf line 33)
    inf: AddReg=LbAdapter.Reg.Adapter.Params
    (oem26.inf line 34)
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:02.917
    dvi: Default installer: Exit
    dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 22:46:02.920
    ndv: Installing files...
    dvi: {DIF_INSTALLDEVICEFILES} 22:46:02.924
    dvi: CoInstaller 1: Enter 22:46:02.926
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:02.930
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:02.933
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:02.936
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:02.940
    dvi: {Install FILES}
    inf: Opened PNF:
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    inf: {Install Inf Section [LbAdapter.ndi]}
    inf: CopyFiles=LbAdapter.CopyFiles
    (netlb_x64.inf line 35)
    cpy: Open PnpLockdownPolicy: Err=2. This
    is OK. Use LockDownPolicyDefault
    flq: QueueSingleCopy...
    flq: Inf :
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf'
    flq: SourceInf:
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf'
    flq: SourceSection: [sourcedisksfiles]
    flq: Source root path based on SourceInf
    flq: SourceRootPath:
    'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8'
    flq: {FILE_QUEUE_COPY}
    flq: CopyStyle - 0x00000400
    flq: {FILE_QUEUE_COPY}
    flq: CopyStyle -
    0x00000400
    flq: SourceRootPath -
    'C:\Windows\System32\DriverStore\FileRepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8'
    flq: SourceFilename - 'lb.sys'
    flq: TargetDirectory-
    'C:\Windows\system32\DRIVERS'
    flq: TargetFilename - 'lb.sys'
    flq: SourceDesc - 'LAN
    Bridger Virtual Ethernet Adapter Installation Disk'
    flq: {FILE_QUEUE_COPY
    exit(0x00000000)}
    flq: {FILE_QUEUE_COPY exit(0x00000000)}
    inf: {Install Inf Section [LbAdapter.ndi] exit
    (0x00000000)}
    dvi: Processing co-installer registration
    section [LbAdapter.ndi.CoInstallers].
    inf: {Install Inf Section
    [LbAdapter.ndi.CoInstallers]}
    inf: {Install Inf Section
    [LbAdapter.ndi.CoInstallers] exit (0x00000000)}
    dvi: Co-installers registered.
    dvi: {Install INTERFACES}
    dvi: Installing section
    [LbAdapter.ndi.Interfaces]
    dvi: {Install INTERFACES exit 00000000}
    dvi: {Install FILES exit (0x00000000)}
    dvi: Default installer: Exit
    dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 22:46:02.988
    ndv: Pruning file queue...
    dvi: {_SCAN_FILE_QUEUE}
    flq: ScanQ flags=620
    flq: SPQ_SCAN_PRUNE_COPY_QUEUE
    flq: SPQ_SCAN_FILE_COMPARISON
    flq: SPQ_SCAN_ACTIVATE_DRP
    flq: ScanQ number of copy nodes=1
    flq: File 'C:\Windows\system32\DRIVERS\lb.sys' pruned
    from copy.
    sig: Using catalog
    'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem26.CA
    T'.
    flq: {SPFILENOTIFY_CABINETINFO}
    flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)}
    flq: {SPFILENOTIFY_FILEEXTRACTED}
    flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)}
    ! sig: VerifyTrustFailed for
    C:\Windows\system32\DRIVERS\lb.sys.
    ! sig: Error 0x800b0109: A certificate chain processed,
    but terminated in a root certificate which is not trusted by the trust provider.
    cpy: DrpSetRegFileProt
    'C:\Windows\system32\DRIVERS\lb.sys' Status=0 Class=OEM Legacy
    flq: ScanQ action=200 DoPruning=32
    flq: ScanQ end Validity flags=620 CopyNodes=0
    dvi: {_SCAN_FILE_QUEUE exit(0, 0x00000000)}
    ndv: Committing file queue...
    flq: {_commit_file_queue}
    flq: CommitQ DelNodes=0 RenNodes=0 CopyNodes=0
    flq: CommitQ early exit: No nodes are queued
    flq: {_commit_file_queue exit OK}
    ndv: Registering CoInstallers...
    dvi: {DIF_REGISTER_COINSTALLERS} 22:46:03.581
    dvi: CoInstaller 1: Enter 22:46:03.583
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:03.586
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:03.589
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:03.591
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:03.594
    inf: Opened PNF:
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    inf: {Install Inf Section
    [LbAdapter.ndi.CoInstallers]}
    inf: {Install Inf Section
    [LbAdapter.ndi.CoInstallers] exit (0x00000000)}
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:03.645
    dvi: CoInstaller 1: Enter 22:46:03.647
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:03.650
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:03.653
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:03.657
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)}
    22:46:03.661
    dvi: Co-installers registered.
    dvi: Default installer: Exit
    dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)}
    22:46:03.665
    ndv: Installing interfaces...
    dvi: {DIF_INSTALLINTERFACES} 22:46:03.667
    dvi: Using exported function 'NciDeviceInstall' in
    module 'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function
    'WlanDeviceClassCoInstaller' in module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 ==
    wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function
    'WwanDeviceClassCoInstaller' in module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 ==
    wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:03.679
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:03.682
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:03.685
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:03.689
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:03.692
    dvi: {Install INTERFACES}
    inf: Opened PNF:
    'c:\windows\system32\driverstore\filerepository\netlb_x64.inf_amd64_neutral_
    41ce5dbcf7c93cc8\netlb_x64.inf' ([strings])
    dvi: Installing section
    [LbAdapter.ndi.Interfaces]
    dvi: {Install INTERFACES exit 00000000}
    dvi: Default installer: Exit
    dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 22:46:03.701
    ndv: Installing device...
    dvi: {DIF_INSTALLDEVICE} 22:46:03.704
    dvi: CoInstaller 1: Enter 22:46:03.705
    cci: NdisCoinst: NetCfgInstanceId does not exist
    cci: NdisCoinst: Guid of the adapter is
    {C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    inf: Opened PNF: 'C:\Windows\INF\oem26.inf'
    ([strings])
    cci: NdisCoinst: IfType from registry is 1
    cci: NdisCoinst: IfType 1, Characteristics 0x1,
    IsIrdaDevice 0, PhysicalMediaType -1, MediaType -1, IsBridge 0, FoundGuidInDownlevel 0, EnableDhcp 2
    cci: NdisCoinst: Connection name is Local Area
    Connection 3
    cci: NdisCoinst: NetLuidIndex does not exist
    !!! cci: NdisCoinst: NcipAllocateNetLuidIndex failed
    with error 0x5aa
    !!! dvi: CoInstaller 1: failed(0x000005aa)!
    !!! dvi: Error 1450: Insufficient system resources exist to
    complete the requested service.
    dvi: {DIF_INSTALLDEVICE - exit(0x000005aa)} 22:46:03.767
    !!! ndv: Error(000005aa) installing device!
    ndv: Device install status=0x000005aa
    ndv: Performing device install final cleanup...
    ! ndv: Queueing up error report since device installation
    failed...
    ndv: {Core Device Install - exit(0x000005aa)} 22:46:03.774
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:03.775
    dvi: CoInstaller 1: Enter 22:46:03.777
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:03.780
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:03.783
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:03.787
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 22:46:03.791
    ump: Server install process exited with code 0x000005aa
    22:46:03.822
    ump: {Plug and Play Service: Device Install exit(000005aa)}
    ndv: Device Install failed for new device...installing NULL driver.
    dvi: {Plug and Play Service: Device Install for ROOT\NET\0000}
    ump: Creating Install Process: DrvInst.exe 22:46:03.838
    ! ndv: Installing NULL driver!
    dvi: Set selected driver complete.
    dvi: {DIF_ALLOW_INSTALL} 22:46:03.975
    dvi: Using exported function 'NetClassInstaller' in module
    'C:\Windows\system32\NetCfgx.dll'.
    dvi: Class installer == NetCfgx.dll,NetClassInstaller
    dvi: Using exported function 'NciDeviceInstall' in module
    'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function 'WlanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 == wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function 'WwanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 == wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:04.004
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:04.008
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:04.010
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:04.012
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:04.019
    dvi: Default installer: Exit
    dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 22:46:04.022
    dvi: {DIF_INSTALLDEVICE} 22:46:04.024
    dvi: CoInstaller 1: Enter 22:46:04.026
    cci: NdisCoinst: Succesfully set NewDeviceInstall to 0
    cci: NdisCoinst: Null driver install
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:04.034
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:04.037
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:04.041
    cci: [NCI BEGIN INSTALL DEVICE for ROOT\NET\0000]
    cci: NCI: Null driver install.
    cci: NCI: NewDeviceInstall is 0. Assuming this is an
    update
    dvi: {DIF_REMOVE} 22:46:04.046
    dvi: CoInstaller 1: Enter 22:46:04.049
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:04.052
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:04.055
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:04.058
    cci: [NCI BEGIN REMOVE DEVICE for
    ROOT\NET\0000]
    cci: [NCI: BEGIN STORE EXTERNAL RESOURCE INFO]
    cci: NCI: IfType=1
    cci: NCI:
    NetcfgInstanceId(GUID)={C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    cci: [NCI: END STORE EXTERNAL RESOURCE INFO]
    dvi: {Remove DEVICE}
    dvi: InstanceID = 'ROOT\NET\0000'
    dvi: Devnode Status = 0x01802001
    dvi: CM_Query_And_Remove_Subtree_Ex
    returns 0x00000000
    dvi: Devnode Status after
    CM_Query_And_Remove_Subtree_Ex = 0x01802401
    dvi: Query-and-Remove succeeded
    dvi: {Delete DEVICE}
    dvi: Device Instance uninstalled.
    dvi: {Delete DEVICE exit (0x00000000)}
    dvi: {Remove DEVICE exit (0x00000000)}
    cci: NCI:Delayed Cleanup not required..
    DevInstallParams.Flags=0x00800000
    cci: NCI: Notifying binding engine of removal
    cci: NCI: INetCfg UnInstaller Interface asking
    for write lock. 22:46:04.180
    cci: NCI: INetCfg UnInstaller Interface
    acquired write lock. 22:46:04.182
    cci: NCI: Init Notify Object for ms_ndiscap
    cci: NCI: Init Notify Object for ms_ndiscap
    complete
    cci: NCI: Init Notify Object for ms_server
    cci: NCI: Init Notify Object for ms_server
    complete
    cci: NCI: Init Notify Object for ms_steelhead
    cci: NCI: Init Notify Object for ms_steelhead
    complete
    cci: NCI: Init Notify Object for ms_rassrv
    cci: NCI: Init Notify Object for ms_rassrv
    complete
    cci: NCI: Init Notify Object for ms_msclient
    cci: NCI: Init Notify Object for ms_msclient
    complete
    cci: NCI: Init Notify Object for ms_tcpip6
    cci: NCI: Init Notify Object for ms_tcpip6
    complete
    cci: NCI: Init Notify Object for ms_tcpip
    cci: NCI: Init Notify Object for ms_tcpip
    complete
    cci: NCI: Init Notify Object for ms_pppoe
    cci: NCI: Init Notify Object for ms_pppoe
    complete
    cci: NCI: Init Notify Object for ms_pptp
    cci: NCI: Init Notify Object for ms_pptp
    complete
    cci: NCI: Init Notify Object for ms_l2tp
    cci: NCI: Init Notify Object for ms_l2tp
    complete
    cci: NCI: Init Notify Object for ms_ndiswan
    cci: NCI: Init Notify Object for ms_ndiswan
    complete
    cci: NCI: Init Notify Object for ms_agilevpn
    cci: NCI: Init Notify Object for ms_agilevpn
    complete
    cci: NCI: Init Notify Object for ms_sstp
    cci: NCI: Init Notify Object for ms_sstp
    complete
    cci: [NCI: BEGIN Release Externally Managed
    Resources]
    cci: NCI: IfType=1
    cci: NCI:
    NetcfgInstanceId(GUID)={C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    ! cci: !NCI: IfType Present, NetLuidIndex NOT
    Present. pszPnpID= ROOT\NET\0000
    cci: NCI: Successfully deleted Connection
    Registry Key for GUID={C88CF875-4F7E-465E-BD02-DD2639E1A43A}
    cci: [NCI: END Release Externally Managed
    Resources]
    cci: NCI: INetCfg UnInstaller Interface
    Released write lock. 22:46:04.937
    cci:

    cci: [NCI END REMOVE DEVICE for ROOT\NET\0000.
    Result 0x00000000]
    dvi: Class installer: Exit
    dvi: CoInstaller 1: Enter (Post Processing)
    22:46:04.945
    dvi: CoInstaller 1: Exit (Post Processing)
    dvi: {DIF_REMOVE - exit(0x00000000)} 22:46:04.948
    cci: [NCI END INSTALL DEVICE for ROOT\NET\0000]
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:04.952
    !!! dvi: Error obtaining device ID!
    !!! dvi: Cleaning up failed installation (00000006)
    ! dvi: Failed to set Config Flags property: 0x00000020
    ! dvi: Error 0xe000020b: The device instance does not
    exist in the hardware tree.
    !!! dvi: Default installer: failed!
    !!! dvi: Error 6: The handle is invalid.
    dvi: {DIF_INSTALLDEVICE - exit(0x00000006)} 22:46:04.962
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:04.964
    dvi: CoInstaller 1: Enter 22:46:04.966
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:04.969
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:04.972
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:04.975
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 22:46:04.979
    ump: Server install process exited with code 0x00000006
    22:46:04.986
    ump: {Plug and Play Service: Device Install exit(00000006)}
    dvi: {Build Driver List} 22:46:04.990
    ! dvi: Driver list already built
    dvi: {Build Driver List - exit(0x00000000)} 22:46:04.994
    dvi: {DIF_SELECTBESTCOMPATDRV} 22:46:04.996
    dvi: CoInstaller 1: Enter 22:46:04.998
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:05.000
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:05.002
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:05.006
    dvi: Class installer: Exit
    dvi: Default installer: Enter 22:46:05.009
    dvi: {Select Best Driver}
    dvi: Selected driver installs from section
    [LbAdapter.ndi] in 'c:\program files\echobit\lan bridger\driver\netlb_x64.inf'.
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:05.014
    dvi: CoInstaller 1: Enter 22:46:05.016
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:05.019
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:05.023
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:05.026
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)}
    22:46:05.029
    dvi: Set selected driver complete.
    dvi: Selected:
    dvi: Description - [LAN Bridger Virtual Ethernet
    Adapter]
    dvi: InfFile - [c:\program files\echobit\lan
    bridger\driver\netlb_x64.inf]
    dvi: Section - [LbAdapter.ndi]
    dvi: Signer - [Echobit, LLC]
    dvi: Rank - [0x00ff0000]
    dvi: {Select Best Driver - exit(0x00000000)}
    dvi: Default installer: Exit
    dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 22:46:05.043
    dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 22:46:05.044
    dvi: Using exported function 'NetClassInstaller' in module
    'C:\Windows\system32\NetCfgx.dll'.
    dvi: Class installer == NetCfgx.dll,NetClassInstaller
    dvi: Using exported function 'NciDeviceInstall' in module
    'C:\Windows\system32\nci.dll'.
    dvi: CoInstaller 1 == nci.dll,NciDeviceInstall
    dvi: Using exported function 'WlanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wlaninst.dll'.
    dvi: CoInstaller 2 == wlaninst.dll,WlanDeviceClassCoInstaller
    dvi: Using exported function 'WwanDeviceClassCoInstaller' in
    module 'C:\Windows\system32\wwaninst.dll'.
    dvi: CoInstaller 3 == wwaninst.dll,WwanDeviceClassCoInstaller
    dvi: CoInstaller 1: Enter 22:46:05.062
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:05.065
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:05.069
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:05.072
    !!! dvi: Class installer: failed(0xe000020b)!
    !!! dvi: Error 0xe000020b: The device instance does not exist in the
    hardware tree.
    dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020b)}
    22:46:05.077
    dvi: {DIF_DESTROYPRIVATEDATA} 22:46:05.079
    dvi: CoInstaller 1: Enter 22:46:05.081
    dvi: CoInstaller 1: Exit
    dvi: CoInstaller 2: Enter 22:46:05.083
    dvi: CoInstaller 2: Exit
    dvi: CoInstaller 3: Enter 22:46:05.086
    dvi: CoInstaller 3: Exit
    dvi: Class installer: Enter 22:46:05.089
    dvi: Class installer: Exit
    dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 22:46:05.092 <<< Section end 2010/05/13 22:46:05.094 <<< [Exit status: SUCCESS]



    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer


    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer


    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
  • Jeffrey_Tippet_[MSFT]Jeffrey_Tippet_[MSFT] Member - All Emails Posts: 450
    That's good news, since it gives us something to go on. However, to fix the root cause, you wouldn't edit the IfTypes value directly. That's because IfTypes is basically a *cache* of the ifTypes of various network interfaces on the system. So the registry value does nicely summarize the problem (too many interfaces) but it can't be used to fix the problem (without making the cache inconsistent with the actual state of your system -- that would be bad).

    You should figure out why there are 1000 interfaces installed with ifType==1. Again, the following is considered an implementation detail, subject to change; but it's handy for troubleshooting. Look in this registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}
    Normally, it lists all the interfaces on the system -- e.g., my main box has ~18 interfaces in there. If you see over 1000, that explains the problem. Just start looking at a random few of them and it should become obvious which ones are the cancerous ones. Depending on what kind of interface it is, you can determine how to uninstall them all. If you are sure it's safe to remove them, you can use devcon.exe (in the WDK) to remove all of them at once.


    -----Original Message-----
    From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
    Sent: Sunday, May 16, 2010 3:27 PM
    To: Windows System Software Devs Interest List
    Subject: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when installing

    Alright, so looking at the IfType 1 in the registry indicated the problem. I see a very long binary value with all FF's, which means the bitmap is full. How do I best go about cleaning this up on the customer's computer? Ideally, he shouldn't have any IF_TYPE_OTHER devices at all, should he? If so, maybe I can just set it back to 0?

    Cheers,
    Soren

    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
  • OSR_Community_UserOSR_Community_User Member Posts: 110,218
    Hi Jeffrey,

    I had the customer take a look at the registry key you provided to see if he
    had a huge list of interfaces installed on the system, but it looked very
    normal -- he had about 20 interfaces -- so I'm still at a loss what's going
    wrong here.

    He did mention he had been running a registry cleaner recently, but I don't
    know if such apps actually would remove interfaces by modifying the
    registry; sounds like a very error-prone approach to me.

    / Soren

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Jeffrey Tippet
    Sent: Monday, May 17, 2010 11:20 AM
    To: Windows System Software Devs Interest List
    Subject: RE: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when
    installing

    That's good news, since it gives us something to go on. However, to fix the
    root cause, you wouldn't edit the IfTypes value directly. That's because
    IfTypes is basically a *cache* of the ifTypes of various network interfaces
    on the system. So the registry value does nicely summarize the problem (too
    many interfaces) but it can't be used to fix the problem (without making the
    cache inconsistent with the actual state of your system -- that would be
    bad).

    You should figure out why there are 1000 interfaces installed with
    ifType==1. Again, the following is considered an implementation detail,
    subject to change; but it's handy for troubleshooting. Look in this
    registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11C
    E-BFC1-08002BE10318}
    Normally, it lists all the interfaces on the system -- e.g., my main box has
    ~18 interfaces in there. If you see over 1000, that explains the problem.
    Just start looking at a random few of them and it should become obvious
    which ones are the cancerous ones. Depending on what kind of interface it
    is, you can determine how to uninstall them all. If you are sure it's safe
    to remove them, you can use devcon.exe (in the WDK) to remove all of them at
    once.


    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
    Sent: Sunday, May 16, 2010 3:27 PM
    To: Windows System Software Devs Interest List
    Subject: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when installing

    Alright, so looking at the IfType 1 in the registry indicated the problem. I
    see a very long binary value with all FF's, which means the bitmap is full.
    How do I best go about cleaning this up on the customer's computer? Ideally,
    he shouldn't have any IF_TYPE_OTHER devices at all, should he? If so, maybe
    I can just set it back to 0?

    Cheers,
    Soren

    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • OSR_Community_UserOSR_Community_User Member Posts: 110,218
    And a little more information:

    Our customer took a look at
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\Descriptions and
    for the "ESET Personal Firewall Miniport" key, the REG_MULTI_SZ value
    contains over 1000 lines with sequentially-numbered indices, i.e. 1, 2, 3,
    etc.

    He also looked under
    HKEY_LOCAL_MACHINE\SYSTEM\Controlset002\Control\Network\{4D36E972-E325-11CE-
    BFC1-08002BE10318} and discovered that he had over a 1000 entries there as
    well.

    I'm not exactly sure what to make of this, but it'd seem that these
    lingering interfaces have somehow been cleaned up in his CurrentControlSet,
    but the IfUsedNetLuidIndices registry key from earlier didn't get updated
    accordingly.

    / Soren

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Jeffrey Tippet
    Sent: Monday, May 17, 2010 11:20 AM
    To: Windows System Software Devs Interest List
    Subject: RE: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when
    installing

    That's good news, since it gives us something to go on. However, to fix the
    root cause, you wouldn't edit the IfTypes value directly. That's because
    IfTypes is basically a *cache* of the ifTypes of various network interfaces
    on the system. So the registry value does nicely summarize the problem (too
    many interfaces) but it can't be used to fix the problem (without making the
    cache inconsistent with the actual state of your system -- that would be
    bad).

    You should figure out why there are 1000 interfaces installed with
    ifType==1. Again, the following is considered an implementation detail,
    subject to change; but it's handy for troubleshooting. Look in this
    registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11C
    E-BFC1-08002BE10318}
    Normally, it lists all the interfaces on the system -- e.g., my main box has
    ~18 interfaces in there. If you see over 1000, that explains the problem.
    Just start looking at a random few of them and it should become obvious
    which ones are the cancerous ones. Depending on what kind of interface it
    is, you can determine how to uninstall them all. If you are sure it's safe
    to remove them, you can use devcon.exe (in the WDK) to remove all of them at
    once.


    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
    Sent: Sunday, May 16, 2010 3:27 PM
    To: Windows System Software Devs Interest List
    Subject: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when installing

    Alright, so looking at the IfType 1 in the registry indicated the problem. I
    see a very long binary value with all FF's, which means the bitmap is full.
    How do I best go about cleaning this up on the customer's computer? Ideally,
    he shouldn't have any IF_TYPE_OTHER devices at all, should he? If so, maybe
    I can just set it back to 0?

    Cheers,
    Soren

    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • Jeffrey_Tippet_[MSFT]Jeffrey_Tippet_[MSFT] Member - All Emails Posts: 450
    Interesting. I agree with your thinking. It sounds like the contents of the registry have been damaged. You can try to manually repair this, but you do run a high risk of making things worse. You might just find that the easiest and fastest route is to re-install the OS.

    -----Original Message-----
    From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Soren Dreijer
    Sent: Monday, May 17, 2010 3:05 PM
    To: Windows System Software Devs Interest List
    Subject: RE: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when installing

    And a little more information:

    Our customer took a look at
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\Descriptions and for the "ESET Personal Firewall Miniport" key, the REG_MULTI_SZ value contains over 1000 lines with sequentially-numbered indices, i.e. 1, 2, 3, etc.

    He also looked under
    HKEY_LOCAL_MACHINE\SYSTEM\Controlset002\Control\Network\{4D36E972-E325-11CE-
    BFC1-08002BE10318} and discovered that he had over a 1000 entries there as well.

    I'm not exactly sure what to make of this, but it'd seem that these lingering interfaces have somehow been cleaned up in his CurrentControlSet, but the IfUsedNetLuidIndices registry key from earlier didn't get updated accordingly.

    / Soren

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Jeffrey Tippet
    Sent: Monday, May 17, 2010 11:20 AM
    To: Windows System Software Devs Interest List
    Subject: RE: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when installing

    That's good news, since it gives us something to go on. However, to fix the root cause, you wouldn't edit the IfTypes value directly. That's because IfTypes is basically a *cache* of the ifTypes of various network interfaces on the system. So the registry value does nicely summarize the problem (too many interfaces) but it can't be used to fix the problem (without making the cache inconsistent with the actual state of your system -- that would be bad).

    You should figure out why there are 1000 interfaces installed with ifType==1. Again, the following is considered an implementation detail, subject to change; but it's handy for troubleshooting. Look in this registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11C
    E-BFC1-08002BE10318}
    Normally, it lists all the interfaces on the system -- e.g., my main box has
    ~18 interfaces in there. If you see over 1000, that explains the problem.
    Just start looking at a random few of them and it should become obvious which ones are the cancerous ones. Depending on what kind of interface it is, you can determine how to uninstall them all. If you are sure it's safe to remove them, you can use devcon.exe (in the WDK) to remove all of them at once.


    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
    Sent: Sunday, May 16, 2010 3:27 PM
    To: Windows System Software Devs Interest List
    Subject: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when installing

    Alright, so looking at the IfType 1 in the registry indicated the problem. I see a very long binary value with all FF's, which means the bitmap is full.
    How do I best go about cleaning this up on the customer's computer? Ideally, he shouldn't have any IF_TYPE_OTHER devices at all, should he? If so, maybe I can just set it back to 0?

    Cheers,
    Soren

    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer


    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer


    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
  • David_R._CattleyDavid_R._Cattley Member - All Emails Posts: 2,111
    Do you have access to the setupapi.*.log files from %windir%\inf for this
    machine?

    You may be able to see when/how the ESET IM driver was installed/removed and
    if it experienced some sort of catastrophe.

    Good Luck,
    Dave Cattley

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Jeffrey Tippet
    Sent: Tuesday, May 18, 2010 11:35 AM
    To: Windows System Software Devs Interest List
    Subject: RE: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when
    installing

    Interesting. I agree with your thinking. It sounds like the contents of
    the registry have been damaged. You can try to manually repair this, but
    you do run a high risk of making things worse. You might just find that the
    easiest and fastest route is to re-install the OS.

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Soren Dreijer
    Sent: Monday, May 17, 2010 3:05 PM
    To: Windows System Software Devs Interest List
    Subject: RE: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when
    installing

    And a little more information:

    Our customer took a look at
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\Descriptions and
    for the "ESET Personal Firewall Miniport" key, the REG_MULTI_SZ value
    contains over 1000 lines with sequentially-numbered indices, i.e. 1, 2, 3,
    etc.

    He also looked under
    HKEY_LOCAL_MACHINE\SYSTEM\Controlset002\Control\Network\{4D36E972-E325-11CE-
    BFC1-08002BE10318} and discovered that he had over a 1000 entries there as
    well.

    I'm not exactly sure what to make of this, but it'd seem that these
    lingering interfaces have somehow been cleaned up in his CurrentControlSet,
    but the IfUsedNetLuidIndices registry key from earlier didn't get updated
    accordingly.

    / Soren

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Jeffrey Tippet
    Sent: Monday, May 17, 2010 11:20 AM
    To: Windows System Software Devs Interest List
    Subject: RE: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when
    installing

    That's good news, since it gives us something to go on. However, to fix the
    root cause, you wouldn't edit the IfTypes value directly. That's because
    IfTypes is basically a *cache* of the ifTypes of various network interfaces
    on the system. So the registry value does nicely summarize the problem (too
    many interfaces) but it can't be used to fix the problem (without making the
    cache inconsistent with the actual state of your system -- that would be
    bad).

    You should figure out why there are 1000 interfaces installed with
    ifType==1. Again, the following is considered an implementation detail,
    subject to change; but it's handy for troubleshooting. Look in this
    registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11C
    E-BFC1-08002BE10318}
    Normally, it lists all the interfaces on the system -- e.g., my main box has
    ~18 interfaces in there. If you see over 1000, that explains the problem.
    Just start looking at a random few of them and it should become obvious
    which ones are the cancerous ones. Depending on what kind of interface it
    is, you can determine how to uninstall them all. If you are sure it's safe
    to remove them, you can use devcon.exe (in the WDK) to remove all of them at
    once.


    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
    Sent: Sunday, May 16, 2010 3:27 PM
    To: Windows System Software Devs Interest List
    Subject: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when installing

    Alright, so looking at the IfType 1 in the registry indicated the problem. I
    see a very long binary value with all FF's, which means the bitmap is full.
    How do I best go about cleaning this up on the customer's computer? Ideally,
    he shouldn't have any IF_TYPE_OTHER devices at all, should he? If so, maybe
    I can just set it back to 0?

    Cheers,
    Soren

    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • OSR_Community_UserOSR_Community_User Member Posts: 110,218
    Hi Dave,

    I don't know if the customer has other setupapi logs than the one he
    provided me with. I'll ask him though.

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of David R. Cattley
    Sent: Tuesday, May 18, 2010 11:14 AM
    To: Windows System Software Devs Interest List
    Subject: RE: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when
    installing

    Do you have access to the setupapi.*.log files from %windir%\inf for this
    machine?

    You may be able to see when/how the ESET IM driver was installed/removed and
    if it experienced some sort of catastrophe.

    Good Luck,
    Dave Cattley

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Jeffrey Tippet
    Sent: Tuesday, May 18, 2010 11:35 AM
    To: Windows System Software Devs Interest List
    Subject: RE: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when
    installing

    Interesting. I agree with your thinking. It sounds like the contents of
    the registry have been damaged. You can try to manually repair this, but
    you do run a high risk of making things worse. You might just find that the
    easiest and fastest route is to re-install the OS.

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Soren Dreijer
    Sent: Monday, May 17, 2010 3:05 PM
    To: Windows System Software Devs Interest List
    Subject: RE: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when
    installing

    And a little more information:

    Our customer took a look at
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\Descriptions and
    for the "ESET Personal Firewall Miniport" key, the REG_MULTI_SZ value
    contains over 1000 lines with sequentially-numbered indices, i.e. 1, 2, 3,
    etc.

    He also looked under
    HKEY_LOCAL_MACHINE\SYSTEM\Controlset002\Control\Network\{4D36E972-E325-11CE-
    BFC1-08002BE10318} and discovered that he had over a 1000 entries there as
    well.

    I'm not exactly sure what to make of this, but it'd seem that these
    lingering interfaces have somehow been cleaned up in his CurrentControlSet,
    but the IfUsedNetLuidIndices registry key from earlier didn't get updated
    accordingly.

    / Soren

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Jeffrey Tippet
    Sent: Monday, May 17, 2010 11:20 AM
    To: Windows System Software Devs Interest List
    Subject: RE: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when
    installing

    That's good news, since it gives us something to go on. However, to fix the
    root cause, you wouldn't edit the IfTypes value directly. That's because
    IfTypes is basically a *cache* of the ifTypes of various network interfaces
    on the system. So the registry value does nicely summarize the problem (too
    many interfaces) but it can't be used to fix the problem (without making the
    cache inconsistent with the actual state of your system -- that would be
    bad).

    You should figure out why there are 1000 interfaces installed with
    ifType==1. Again, the following is considered an implementation detail,
    subject to change; but it's handy for troubleshooting. Look in this
    registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11C
    E-BFC1-08002BE10318}
    Normally, it lists all the interfaces on the system -- e.g., my main box has
    ~18 interfaces in there. If you see over 1000, that explains the problem.
    Just start looking at a random few of them and it should become obvious
    which ones are the cancerous ones. Depending on what kind of interface it
    is, you can determine how to uninstall them all. If you are sure it's safe
    to remove them, you can use devcon.exe (in the WDK) to remove all of them at
    once.


    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
    Sent: Sunday, May 16, 2010 3:27 PM
    To: Windows System Software Devs Interest List
    Subject: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when installing

    Alright, so looking at the IfType 1 in the registry indicated the problem. I
    see a very long binary value with all FF's, which means the bitmap is full.
    How do I best go about cleaning this up on the customer's computer? Ideally,
    he shouldn't have any IF_TYPE_OTHER devices at all, should he? If so, maybe
    I can just set it back to 0?

    Cheers,
    Soren

    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • OSR_Community_UserOSR_Community_User Member Posts: 110,218
    Yeah, that's pretty unfortunate. I guess that's what you get for running
    "cleaning" applications :) Thanks for your help!

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Jeffrey Tippet
    Sent: Tuesday, May 18, 2010 10:35 AM
    To: Windows System Software Devs Interest List
    Subject: RE: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when
    installing

    Interesting. I agree with your thinking. It sounds like the contents of
    the registry have been damaged. You can try to manually repair this, but
    you do run a high risk of making things worse. You might just find that the
    easiest and fastest route is to re-install the OS.

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Soren Dreijer
    Sent: Monday, May 17, 2010 3:05 PM
    To: Windows System Software Devs Interest List
    Subject: RE: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when
    installing

    And a little more information:

    Our customer took a look at
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\Descriptions and
    for the "ESET Personal Firewall Miniport" key, the REG_MULTI_SZ value
    contains over 1000 lines with sequentially-numbered indices, i.e. 1, 2, 3,
    etc.

    He also looked under
    HKEY_LOCAL_MACHINE\SYSTEM\Controlset002\Control\Network\{4D36E972-E325-11CE-
    BFC1-08002BE10318} and discovered that he had over a 1000 entries there as
    well.

    I'm not exactly sure what to make of this, but it'd seem that these
    lingering interfaces have somehow been cleaned up in his CurrentControlSet,
    but the IfUsedNetLuidIndices registry key from earlier didn't get updated
    accordingly.

    / Soren

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Jeffrey Tippet
    Sent: Monday, May 17, 2010 11:20 AM
    To: Windows System Software Devs Interest List
    Subject: RE: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when
    installing

    That's good news, since it gives us something to go on. However, to fix the
    root cause, you wouldn't edit the IfTypes value directly. That's because
    IfTypes is basically a *cache* of the ifTypes of various network interfaces
    on the system. So the registry value does nicely summarize the problem (too
    many interfaces) but it can't be used to fix the problem (without making the
    cache inconsistent with the actual state of your system -- that would be
    bad).

    You should figure out why there are 1000 interfaces installed with
    ifType==1. Again, the following is considered an implementation detail,
    subject to change; but it's handy for troubleshooting. Look in this
    registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11C
    E-BFC1-08002BE10318}
    Normally, it lists all the interfaces on the system -- e.g., my main box has
    ~18 interfaces in there. If you see over 1000, that explains the problem.
    Just start looking at a random few of them and it should become obvious
    which ones are the cancerous ones. Depending on what kind of interface it
    is, you can determine how to uninstall them all. If you are sure it's safe
    to remove them, you can use devcon.exe (in the WDK) to remove all of them at
    once.


    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
    Sent: Sunday, May 16, 2010 3:27 PM
    To: Windows System Software Devs Interest List
    Subject: RE:[ntdev] NDIS miniport: ERROR_NO_SYSTEM_RESOURCES when installing

    Alright, so looking at the IfType 1 in the registry indicated the problem. I
    see a very long binary value with all FF's, which means the bitmap is full.
    How do I best go about cleaning this up on the customer's computer? Ideally,
    he shouldn't have any IF_TYPE_OTHER devices at all, should he? If so, maybe
    I can just set it back to 0?

    Cheers,
    Soren

    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    NTDEV is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!