Symptoms

Consider the following scenario:

  • Windows Server 2012 setup is initiated from DVD media.

  • The installation destination disk is presented through iSCSI.

  • The computer contains one or more network adapters that are of the same make and model as the network adapter that is used for iSCSI.

In this scenario, when the Windows Server 2012 Setup program is finished, the network adapter that is used for the iSCSI disk is started, but some other network adapters may not be started. This can include any other network interface cards (NICs) in the system and such adapters as the WAN Miniport (IP) and WAN Miniport (IPV6). In Device Manager, the listed adapters that did not start are displayed together with a yellow exclamation mark. Additionally, the details for these devices include error code 31, as follows:

The device is not working properly because Windows cannot load the drivers required for this device. (Code 31)

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prepare the files for hotfix installation

Before you run the Windows Server 2012 setup, you must inject the hotfix into the installation media. To do this, use one of the following methods.

Method 1a: Preinstall the hotfix into custom installation media on USB

Consider the following scenario:

  • You plan to install a Windows operating system from a USB device.

  • You have a Windows 8 or Windows Server 2012 operating system available on a different computer.

  • You can use that computer to manipulate files on the USB device.

  • You have Windows Server 2012 source files available.

To inject the hotfix into the installation media on USB, follow these steps:

  1. Create the folder C:\Bin.

  2. Create the folder C:\Bin\2782676.

  3. Download the hotfix to C:\Bin\2782676.

  4. Create the folder C:\Bin\Mount.

  5. Create the folder C:\Bin\Scratch.

  6. From the Windows Server 2012 installation media, locate the following file, and then copy the file to C:\Bin:

    \Sources\Install.wim

  7. For Windows 8 and Windows Server 2012, right-click in the lower-left corner of the screen, and then select Command prompt (Admin).

  8. Type CD \bin, and then press Enter.

  9. Type dism /get-wiminfo /wimfile=install.wim, and then press Enter. A list of wim indexes is displayed.

    Note You will have to mount and inject the hotfix into the indexes that you plan to use. If you use more than one index, you will have to inject the hotfix into multiple indexes.

  10. Mount the index into which you have to inject the hotfix by using the following dism command, and then press Enter. It will take several moments to complete:

    dism /mount-wim /wimfile=install.wim /index:2 /mountdir=Mount

  11. If the hotfix is an executable file (.exe), you will have to run this to extract the files. Make sure that the files extract to C:\Bin\278676.

  12. Rename Windows8-RT-KB2782676-x64.msu to Windows8-RT-KB2782676-x64.msu.cab.

  13. Double-click Windows8-RT-KB2782676-x64.msu.cab, and then extract the file Windows8-RT-KB2782676-x64.cab to the C:\Bin\278676 folder. This is the file that we will inject.

  14. Inject the hotfix into the mounted wim by using the following dism command, and then press Enter. It will take several moments to complete:

    dism /image:.\Mount /add-package /packagepath:c:\Bin\278676\Windows8-RT-KB2782676-x64.cab /scratchdir=scratch

  15. You can confirm that the package is added by running the following dism commandand then looking at the output for the hotfix number that you just injected:

    dism /image=mount /get-packages

  16. Unmount and commit the changes to the currently mounted WIM by running the following dism command, and then press Enter. It will take several moments to complete:

    dism /unmount-wim /mountdir=Mount /commit

  17. Copy the updated Install.wim file to the USB drive that is currently being used for source media, and replace the existing Install.wim file in the \Sources folder.

Method 1b: Preinstall the hotfix into custom installation media on an ISO

Consider the following scenario:

  • You plan to install a Windows operating system from a custom ISO or DVD.

  • You have a Windows 8 or Windows Server 2012 operating system available on a different computer.

  • You can use that computer to manipulate files.

  • You have Windows Server 2012 source files available.

To inject the hotfix into the installation media on an ISO, follow these steps:

  1. Locate, download, and install the Windows Assessment and Deployment Kit (ADK) for Windows® 8. This will provide the tools to create an ISO that you can use to put install files on a DVD.

  2. Follow steps 1-16 in the previous section. However, instead of copying the files to a USB device, copy the files to a single folder, C:\Bin\Media.

    Note This tool will be looking for the \Media folder.

  3. Locate the following file:

    C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Deployment Tools\amd64\Oscdimg.exe

  4. Use the "Deployment and imaging tools command prompt" that is installed together with the ADK installation, and run as an administrator.

  5. For syntax for creating an ISO that will start on an amd64 (uEFI) computer and also legacy MBR computers, click the following article number to view the article in the Microsoft Knowledge Base:

    947024 How to create an ISO image for UEFI platforms for a Windows PE CD-ROM for Windows Server 2008

  6. For more information, go to the following Microsoft TechNet website:

    Oscdimg Command-Line Options

Method 2: Include files through an answer file "unattend" script by using noncustomized media

Consider the following scenario:

  • You plan to install a Windows operating system from a Microsoft-provided (unmodified) installation DVD.

  • You have a Windows 8 or Windows Server 2012 operating system available on another computer.

  • You can use that computer to manipulate files.

  • You have a USB thumb drive available to which you can copy files.

To include files through an answer file "unattend" script by using noncustomized media, follow these steps:

  1. On a USB thumb drive, create the following folder structure:

    \$OEM$\$$\System32\OEM\2782676
    \$OEM$\$$\System32\OEM\Drivers

  2. Download or obtain Windows hotfix KB2782676. If the hotfix is an executable file (.exe), you will have to run this to extract the files.

  3. Rename "Windows8-RT-KB2782676-x64.msu" to "Windows8-RT-KB2782676-x64.msu.CAB."

    1. Double-click Windows8-RT-KB2782676-x64.msu.CAB to open it.

    2. In Windows8-RT-KB2782676-x64.msu.CAB, locate the Windows8-RT-KB2782676-x64.cab file, and then extract or copy this file to the \$OEM$\$$\System32\OEM\2782676\ folder on the USB.

  4. In Notepad, copy the following code to a text document, and then save the document as <USBdriveletter>:\Autounattend.xml. This will include the hotfix in the installing operating system with few or no modifications. However, if you have to create your own Autounattend.xml file or include additional steps (to automate installation), include these steps in your process: To create a new Unattend.xml file, follow these steps:

    1. Install the Windows Assessment and Deployment Kit (ADK) for Windows® 8.

    2. Open the Windows System Image Manager tool (WSIM) as an administrator.

    3. Make sure that the operating system is copied to read/write accessible media. (Typically, you should copy the Install.wim to a folder for identification.) For this example, copy Install.wim to C:\Win2012.

    4. On the File menu, click Select Windows Image to locate the C:\Win2012\Install.wim.

    5. Select an image in the Windows image file. For this example select Windows Server 2012 SERVERDATACENTER.

    6. If Create the catalog (.CLG) file if you are prompted do this..

    7. In the lower-left window of the WSIM tool, expand Components.

    8. Locate <architecture>_Microsoft-Windows-PnpCustomizationsNonWinPE_neutral. (In this example, you would locate amd64_Microsoft-Windows-PnpCustomizationsNonWinPE _6.2.9200.16384_neutral.

    9. Download and prepare the hotfix to be included in the installed image. To do this, follow these steps:

      1. If the hotfix is an executable (.exe), you have to run the executable to extract the files. Have the files extract to C:\Bin\278676.

      2. Rename Windows8-RT-KB2782676-x64.msu to Windows8-RT-KB2782676-x64.msu.cab," double-click Windows8-RT-KB2782676-x64.msu.cab, and then extract Windows8-RT-KB2782676-x64.cab to C:\Bin\278676. (This is the file that we will use.)

    10. In the Answer file window on the upper right, locate the Packages component, right-click Packages, and then select Insert Package(s).

    11. Locate the Windows8-RT-KB2782676-x64.cab file that was previously copied/extracted from Windows8-RT-KB2782676-x64.msu.cab, and then click to open the file. You should see this added under \Packages\Update\Windows8-RT-KB2782676-x64.cab.

    12. Click Tools, and then click Create configuration set.

    13. In the Select the target folder for the configuration set section, type the drive letter for the USB thumb drive, and then click OK. Files will be copied to the USB thumb drive, and Autounattend.xml will be created.

    14. Plug in the USB thumb drive along together with the Windows 2012 installation DVD, and then restart to the DVD. Or, copy the DVD files to root of the Fat32 active partition USB thumb drive that has these files.

The final product will resemble the following:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<servicing>
<package action="install">
<assemblyIdentity name="Package_for_KB2782676" version="6.2.1.0" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" />
<source location="%configsetroot%\AutoUnattend_Files\2782676\Windows8-RT-KB2782676-x64.cab" />
</package>
</servicing>
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<UseConfigurationSet>true</UseConfigurationSet>
</component>
</settings>
<cpi:offlineImage cpi:source="catalog:C:/bin/win2012x64en/install_windows server 2012 serverdatacenter.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

Note Any data files or folders that are located at the same level as the Autounattend.xml file will be copied to the target operating system in the <driveletter>:\Windows\Configsetroot folder.

Prerequisites

To apply this hotfix, you must be running Windows RT, Windows 8, or Windows Server 2012.

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows RT, Windows 8, and Windows Server 2012 file information notesImportant Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.2.920 0.20 xxx

    Windows RT, Windows 8, and Windows Server 2012

    RTM

    LDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows RT, Windows 8, and Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For Windows RT

File name

File version

File size

Date

Time

Platform

Netcfgx.dll

6.2.9200.16547

346,624

02-Mar-2013

02:27

Not applicable

For all supported x86-based versions of Windows 8

File name

File version

File size

Date

Time

Platform

Netcfgx.dll

6.2.9200.16548

357,888

02-Mar-2013

08:22

x86

Netcfgx.dll

6.2.9200.20652

350,720

02-Mar-2013

08:28

x86

For all supported x64-based versions of Windows 8 and Windows Server 2012

File name

File version

File size

Date

Time

Platform

Netcfgx.dll

6.2.9200.16547

455,168

02-Mar-2013

02:44

x64

Netcfgx.dll

6.2.9200.20651

455,168

02-Mar-2013

02:39

x64

Netcfgx.dll

6.2.9200.16548

357,888

02-Mar-2013

08:22

x86

Netcfgx.dll

6.2.9200.20652

350,720

02-Mar-2013

08:28

x86


Workaround

To work around this issue, use one of the following methods.

Method 1After the Windows Setup program finishes, use Device Manager to reinstall the network adapters that did not start. To do this, follow these steps:

  1. Open Device Manager.

  2. Locate the Network Adapters branch in the right pane.

  3. Right-click the affected network adapter, and then click Uninstall.

    Note Do not select the Delete the driver software for this device option on the Confirm Device Uninstall dialog box.

  4. In the Confirm Device Uninstall dialog box, click OK.

  5. From the Action menu in Device Manager, select Scan for hardware changes.

  6. Repeat steps 1-6 for all affected network adapters.

Method 2If it is supported by the hardware, enable HBA mode on the network adapter that is being used for iSCSI before you run the Windows Setup program. After the Windows Setup program is finished, you can set HBA mode back to disabled.

Note Refer to the hardware vendor's documentation for information about how to enable and disable HBA mode and also for recommendations about how to enable or disable HBA mode in iSCSI start scenarios.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows RT, Windows 8, and Windows Server 2012

Additional files for Windows RT

File name

Arm_679f39475482827c4c32ffea3f3dee0f_31bf3856ad364e35_6.2.9200.16548_none_c95c85313b989408.manifest

File version

Not applicable

File size

710

Date (UTC)

10-May-2013

Time (UTC)

17:26

Platform

Not applicable

File name

Arm_microsoft-windows-ndis-tdi-bindingengine_31bf3856ad364e35_6.2.9200.16548_none_3af1aa40f6c799fb.manifest

File version

Not applicable

File size

13,190

Date (UTC)

02-Mar-2013

Time (UTC)

11:07

Platform

Not applicable

File name

Package_1_for_kb2782676~31bf3856ad364e35~arm~~6.2.1.0.mum

File version

Not applicable

File size

1,818

Date (UTC)

10-May-2013

Time (UTC)

17:26

Platform

Not applicable

File name

Package_2_for_kb2782676~31bf3856ad364e35~arm~~6.2.1.0.mum

File version

Not applicable

File size

1,820

Date (UTC)

10-May-2013

Time (UTC)

17:26

Platform

Not applicable

File name

Package_for_kb2782676_rtm~31bf3856ad364e35~arm~~6.2.1.0.mum

File version

Not applicable

File size

1,930

Date (UTC)

10-May-2013

Time (UTC)

17:26

Platform

Not applicable

Additional files for all supported x86-based versions of Windows 8

File name

Package_1_for_kb2782676_bf~31bf3856ad364e35~x86~~6.2.1.0.mum

File version

Not applicable

File size

1,780

Date (UTC)

10-May-2013

Time (UTC)

17:24

Platform

Not applicable

File name

Package_1_for_kb2782676~31bf3856ad364e35~x86~~6.2.1.0.mum

File version

Not applicable

File size

2,497

Date (UTC)

10-May-2013

Time (UTC)

17:24

Platform

Not applicable

File name

Package_2_for_kb2782676_bf~31bf3856ad364e35~x86~~6.2.1.0.mum

File version

Not applicable

File size

1,782

Date (UTC)

10-May-2013

Time (UTC)

17:24

Platform

Not applicable

File name

Package_2_for_kb2782676~31bf3856ad364e35~x86~~6.2.1.0.mum

File version

Not applicable

File size

2,499

Date (UTC)

10-May-2013

Time (UTC)

17:24

Platform

Not applicable

File name

Package_3_for_kb2782676_bf~31bf3856ad364e35~x86~~6.2.1.0.mum

File version

Not applicable

File size

1,791

Date (UTC)

10-May-2013

Time (UTC)

17:24

Platform

Not applicable

File name

Package_3_for_kb2782676~31bf3856ad364e35~x86~~6.2.1.0.mum

File version

Not applicable

File size

2,508

Date (UTC)

10-May-2013

Time (UTC)

17:24

Platform

Not applicable

File name

Package_for_kb2782676_rtm_bf~31bf3856ad364e35~x86~~6.2.1.0.mum

File version

Not applicable

File size

2,370

Date (UTC)

10-May-2013

Time (UTC)

17:24

Platform

Not applicable

File name

Package_for_kb2782676_rtm~31bf3856ad364e35~x86~~6.2.1.0.mum

File version

Not applicable

File size

2,421

Date (UTC)

10-May-2013

Time (UTC)

17:24

Platform

Not applicable

File name

Update-bf.mum

File version

Not applicable

File size

1,965

Date (UTC)

10-May-2013

Time (UTC)

17:24

Platform

Not applicable

File name

X86_2bd524b460fa86761fafe65d77d7100f_31bf3856ad364e35_6.2.9200.16548_none_53e0eace92a5d85d.manifest

File version

Not applicable

File size

710

Date (UTC)

10-May-2013

Time (UTC)

17:24

Platform

Not applicable

File name

X86_5c762e428023966dfd966b80092cad1e_31bf3856ad364e35_6.2.9200.20652_none_81072b12500c64df.manifest

File version

Not applicable

File size

710

Date (UTC)

10-May-2013

Time (UTC)

17:24

Platform

Not applicable

File name

X86_microsoft-windows-ndis-tdi-bindingengine_31bf3856ad364e35_6.2.9200.16548_none_3aef37e8f6ca7b35.manifest

File version

Not applicable

File size

13,190

Date (UTC)

02-Mar-2013

Time (UTC)

09:11

Platform

Not applicable

File name

X86_microsoft-windows-ndis-tdi-bindingengine_31bf3856ad364e35_6.2.9200.20652_none_3b68030c0ff59ee6.manifest

File version

Not applicable

File size

13,190

Date (UTC)

02-Mar-2013

Time (UTC)

09:16

Platform

Not applicable

Additional files for all supported x64-based versions of Windows 8 and Windows Server 2012

File name

Amd64_5102eb6354a2d3cb368658c40c8a7d82_31bf3856ad364e35_6.2.9200.20652_none_e0f18daf559bdd39.manifest

File version

Not applicable

File size

714

Date (UTC)

10-May-2013

Time (UTC)

17:05

Platform

Not applicable

File name

Amd64_91d468944577a397dcff6a40583706a8_31bf3856ad364e35_6.2.9200.20652_none_b2b5d668c99c459b.manifest

File version

Not applicable

File size

1,068

Date (UTC)

10-May-2013

Time (UTC)

17:05

Platform

Not applicable

File name

Amd64_9435269bafba5e6cf507b4fc80c7f59d_31bf3856ad364e35_6.2.9200.16548_none_ff1c520ca7b99900.manifest

File version

Not applicable

File size

714

Date (UTC)

10-May-2013

Time (UTC)

17:05

Platform

Not applicable

File name

Amd64_ea5e1e3ce16ec9c3ca16c61a81731182_31bf3856ad364e35_6.2.9200.16548_none_d0a545563c2a8928.manifest

File version

Not applicable

File size

1,068

Date (UTC)

10-May-2013

Time (UTC)

17:05

Platform

Not applicable

File name

Amd64_microsoft-windows-ndis-tdi-bindingengine_31bf3856ad364e35_6.2.9200.16548_none_970dd36caf27ec6b.manifest

File version

Not applicable

File size

13,196

Date (UTC)

02-Mar-2013

Time (UTC)

10:59

Platform

Not applicable

File name

Amd64_microsoft-windows-ndis-tdi-bindingengine_31bf3856ad364e35_6.2.9200.20652_none_97869e8fc853101c.manifest

File version

Not applicable

File size

13,196

Date (UTC)

02-Mar-2013

Time (UTC)

11:35

Platform

Not applicable

File name

Package_1_for_kb2782676_bf~31bf3856ad364e35~amd64~~6.2.1.0.mum

File version

Not applicable

File size

1,790

Date (UTC)

10-May-2013

Time (UTC)

17:05

Platform

Not applicable

File name

Package_1_for_kb2782676~31bf3856ad364e35~amd64~~6.2.1.0.mum

File version

Not applicable

File size

2,511

Date (UTC)

10-May-2013

Time (UTC)

17:05

Platform

Not applicable

File name

Package_2_for_kb2782676_bf~31bf3856ad364e35~amd64~~6.2.1.0.mum

File version

Not applicable

File size

2,456

Date (UTC)

10-May-2013

Time (UTC)

17:05

Platform

Not applicable

File name

Package_2_for_kb2782676~31bf3856ad364e35~amd64~~6.2.1.0.mum

File version

Not applicable

File size

3,419

Date (UTC)

10-May-2013

Time (UTC)

17:05

Platform

Not applicable

File name

Package_3_for_kb2782676_bf~31bf3856ad364e35~amd64~~6.2.1.0.mum

File version

Not applicable

File size

2,023

Date (UTC)

10-May-2013

Time (UTC)

17:05

Platform

Not applicable

File name

Package_3_for_kb2782676~31bf3856ad364e35~amd64~~6.2.1.0.mum

File version

Not applicable

File size

2,978

Date (UTC)

10-May-2013

Time (UTC)

17:05

Platform

Not applicable

File name

Package_for_kb2782676_rtm_bf~31bf3856ad364e35~amd64~~6.2.1.0.mum

File version

Not applicable

File size

2,828

Date (UTC)

10-May-2013

Time (UTC)

17:05

Platform

Not applicable

File name

Package_for_kb2782676_rtm~31bf3856ad364e35~amd64~~6.2.1.0.mum

File version

Not applicable

File size

2,887

Date (UTC)

10-May-2013

Time (UTC)

17:05

Platform

Not applicable

File name

Update-bf.mum

File version

Not applicable

File size

2,419

Date (UTC)

10-May-2013

Time (UTC)

17:05

Platform

Not applicable

File name

X86_microsoft-windows-ndis-tdi-bindingengine_31bf3856ad364e35_6.2.9200.16548_none_3aef37e8f6ca7b35.manifest

File version

Not applicable

File size

13,190

Date (UTC)

02-Mar-2013

Time (UTC)

09:11

Platform

Not applicable

File name

X86_microsoft-windows-ndis-tdi-bindingengine_31bf3856ad364e35_6.2.9200.20652_none_3b68030c0ff59ee6.manifest

File version

Not applicable

File size

13,190

Date (UTC)

02-Mar-2013

Time (UTC)

09:16

Platform

Not applicable


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×