You cannot deploy Windows by using Windows PE 4.0 and a third-party out-of-box storage controller driver

Applies to: Windows 8Windows 8 EnterpriseWindows 8 Pro

Symptoms


Assume that you use Microsoft Windows Preinstall Environment (PE) 4.0 to deploy a version of Windows that is earlier than Windows 8 or Windows Server 2012. When you try to offline inject a third-party out-of-box storage controller driver during the installation process, Windows is not deployed.

For example, consider the following scenario:
  • You have a Windows Server 2008 R2-based ISO image and a Windows Server 2012-based ISO image.
  • You replace the Install.wim file in the source folder of the Windows Server 2012-based ISO image with the Install.wim file in the source folder of the Windows Server 2008 R2-based ISO image.
  • You save the updated Windows Server 2012-based ISO image, and then you burn the ISO image onto a DVD disc.
  • You run the Setup.exe file from the DVD disc to deploy Windows Server 2008 R2.
  • You try to offline inject a third-party out-of-box storage controller driver during the installation process.
In this scenario, Windows Server 2008 R2 is not deployed.

Notes

Resolution


Hotfix information

To resolve this issue, download this hotfix, and then run the executable file to extract the Windows8-RT-KB2871318-x86.msu file or Windows8-RT-KB2871318-x64.msu file from the hotfix package. Then, use one of the following methods for using Windows PE 4.0 to deploy a version of Windows that is earlier than Windows 8 or Windows Server 2012: 

Method 1
Deploy Windows by using a DVD or bootable USB flash drive. To do this, follow these steps:
  1. Replace the Install.wim file in the source folder of the Windows Server 2012-based ISO image with the Install.wim file in the source folder of the Windows Server 2008 R2-based ISO image.
  2. Use the expand command to obtain the Winsetup.dll file that is contained in the Windows8-RT-KB2871318-x86.msu file or the Windows8-RT-KB2871318-x64.msu file. For example, if the Windows8-RT-KB2871318-x86.msu file is contained in a folder that is named 2871318 on drive C, follow these steps to obtain the Winsetup.dll file:
    1. Run the following command to expand the Windows8-RT-KB2871318-x86.msu file in the C:\2871318 folder:
      expand -f:* C:\2871318\Windows6.0-KB934307-x86.msu C:\2871318 
    2. Run the following command to expand the Windows8-RT-KB2871318-x86.cab file in the C:\2871318 folder:
      expand –f:* C:\2871318\Windows8-RT-KB2871318-x86.cab C:\2871318 
      Notes
      • The Winsetup.dll file is located in the following folder:
        C:\2871318\x86_microsoft-windows-setup-component_31bf3856ad364e35_6.2.9200.20773_none_2f6afc4e97bf6f4f
      • When you follow these steps for the Windows8-RT-KB2871318-x64.msu file, the Winsetup.dll file is located in the amd64_microsoft-windows-setup-component_31bf3856ad364e35_6.2.9200.20773_none_8b8997d2501ce085 folder.
  3. Replace the Winsetup.dll file in the source folder of the Windows Server 2012-based ISO image with the Winsetup.dll file that is contained the Windows8-RT-KB2871318-x86.msu file or the Windows8-RT-KB2871318-x64.msu file.
  4. Save the updated Windows Server 2012-based ISO image, and then burn the ISO image onto a DVD disc. Or, use the ISO image to create a bootable USB flash drive.
  5. Run the Setup.exe file from the DVD disc or the bootable USB flash drive to deploy Windows Server 2008 R2.
  6. During the installation process, offline inject a third-party out-of-box storage controller driver.
Method 2
Deploy Windows by using Windows Deployment Services (WDS). To do this, follow these steps:
  1. Add a new 64-bit Windows image (Windows PE 4.0) to a WDS server.
  2. Add the Install.wim file from Windows Server 2008 R2 to the WDS server.
  3. Mount index 2 of the image, and then create a temporary folder on the WDS server by running the following command:
    md C:\mount 
  4. Mount the Boot.wim file by running the following command:
    dism /mount-wim /wimfile:boot.wim /index:2 /mountdir:C:\mount 
  5. Install the hotfix into the image by running the following command:
    dism /image:C:\mount /add-package /packagepath: path to hotfix .msu file 
  6. Unmount the image, and then commit the changes by running the following command:
    dism /unmount-wim /mountdir:C:\mount /commit 
  7. Start a WDS client computer from the WDS server. In the list of start options, select the image that you added in step 1.
  8. Provide credentials when you are prompted to do this. Then, select the image that you added in step 1 when you are prompted to select an image.
  9. During the installation process, offline inject a third-party out-of-box storage controller driver.
Note To check the system status and configuration during the installation process, open a command prompt by pressing Shift+F10, and then run a command.

For more information about the .msu file, click the following article number to view the article in the Microsoft Knowledge Base:
934307 Description of the Windows Update Standalone Installer in Windows


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, visit the following Microsoft website: Note 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.

Prerequisites

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

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.