Article ID: 2460786 - Last Review: May 25, 2011 - Revision: 3.0

Unable to Initialize NICs on Windows Server 2008 R2 CORE edition

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
Expand all | Collapse all

SYMPTOMS

Microsoft has seen under certain conditions Windows 2008 R2 Core Server may not be able to detect new network cards or is not using both interfaces on a dual interface NIC on a machine with multiple NICs.
 
The problem has been found when a user replaces the motherboard and another known issue seems when you add a dual port network card. It fails with an “Error 31 - A device attached to the system is not functioning

CAUSE

The bold error code(REGDB_E_CLASSNOTREG) indicates that net class installer failed to instantiate CLSID_InstallQueue COM object (handles pending install work items) because this class object is not registered with the system.
The failing function is net\config\netcfg\engine\dihook.cpp:netcfgx!HrInsertItemIntoInstallQueue.

NCI: INetCfg Installer Interface asking for write lock. 11:40:19.146

cci: ! NCI: Binding engine busy [0x8004A024]. Adding device to queue

cci: [NCI END BINDINGS UPDATE for B06BDRV\L2ND&PCI_163914E4&SUBSYS_02351028&REV_20\5&38E0A078&0&20050100. Result 0x80040154]

cci: [NCI END INSTALL DEVICE for B06BDRV\L2ND&PCI_163914E4&SUBSYS_02351028&REV_20\5&38E0A078&0&20050100]

WORKAROUND

1. A possible workaround to use would be to use KB929852 (http://support.microsoft.com/kb/929852) to disable IPV6 by setting [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents] to 0xffffffff.

2. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\
3. Double-click DisabledComponents to modify the DisabledComponents entry.
4. Type any one of the following values to configure the IPv6 protocol, and then click OK:

a. Type 0 to enable all IPv6 components. (this is the default setting)
b. Type 0xffffffff to disable all IPv6 components, except the IPv6 loopback interface. This value also configures Windows Vista to use Internet Protocol version 4 (IPv4) instead of IPv6 in prefix policies.
c. Type 0x20 to use IPv4 instead of IPv6 in prefix policies.
d. Type 0x10 to disable native IPv6 interfaces.
e. Type 0x01 to disable all tunnels IPv6 interfaces.
f. Type 0x11 to disable all IPv6 interfaces except for the IPv6 loopback interface.

5. After a reboot use the command devcon.exe remove NICVendor_DRV\L2ND&PCI_*
6. devcon.exe rescan

MORE INFORMATION

Customers facing this problem will need to download Devcon.exe from this link to fix this issue.
http://social.technet.microsoft.com/wiki/contents/articles/how-to-obtain-the-current-version-of-device-console-utility-devcon-exe.aspx (http://social.technet.microsoft.com/wiki/contents/articles/how-to-obtain-the-current-version-of-device-console-utility-devcon-exe.aspx)
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.

APPLIES TO
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
Keywords: 
KB2460786