Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


View products that this article applies to.

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

↑ Back to the top


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.
File information
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 8 and Windows Server 2012 file information notes
Important 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:

    VersionProductMilestoneService branch
    6.2.920 0.16 xxxWindows 8 and Windows Server 2012RTMGDR
    6.2.920 0.20 xxxWindows 8 and Windows Server 2012RTMLDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • 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 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 all supported x86-based versions of Windows 8
File nameFile versionFile sizeDateTimePlatform
Alert.gifNot applicable1,04606-Jul-201220:18Not applicable
Appcompat.xslNot applicable11,67306-Jul-201220:18Not applicable
Appcompat_bidi.xslNot applicable12,49806-Jul-201220:18Not applicable
Appcompat_detailed_bidi_txt.xslNot applicable13,37106-Jul-201220:18Not applicable
Appcompat_detailed_txt.xslNot applicable13,32606-Jul-201220:18Not applicable
Arunres.dll6.2.9200.205344,09611-Oct-201204:49x86
Autorun.dll6.2.9200.20534121,85611-Oct-201203:48x86
Cmisetup.dll6.2.9200.20773559,61612-Jul-201306:34x86
Compatprovider.dll6.2.9200.20534137,21611-Oct-201204:18x86
Diager.dll6.2.9200.2053431,74411-Oct-201205:12x86
Diagnostic.dll6.2.9200.20534130,04811-Oct-201205:12x86
Dism.exe6.2.9200.20534200,70411-Oct-201204:18x86
Dismcore.dll6.2.9200.20534310,78411-Oct-201204:17x86
Dismcoreps.dll6.2.9200.2053458,36811-Oct-201204:18x86
Dismhost.exe6.2.9200.20534135,68011-Oct-201203:58x86
Dismprov.dll6.2.9200.20773199,68012-Jul-201305:07x86
Drvmgrtn.dll1.0.0.079,36011-Oct-201203:43x86
Du.dll6.2.9200.2053456,32011-Oct-201204:26x86
Folderprovider.dll6.2.9200.2053447,10411-Oct-201204:20x86
Hwcompat.dll6.2.9200.20534148,48011-Oct-201204:31x86
Locale.nlsNot applicable478,42411-Oct-201200:46Not applicable
Logprovider.dll6.2.9200.20534141,82411-Oct-201204:18x86
Nlsbres.dll6.2.9200.2053456,83211-Oct-201204:49x86
Offline.xmlNot applicable33,64411-Oct-201200:46Not applicable
Pnpibs.dll6.2.9200.2053467,07211-Oct-201205:12x86
Rollback.exe6.2.9200.20773121,94412-Jul-201307:13x86
Sdbapiu.dll3.1.0.1121,85611-Oct-201204:25x86
Segoeui.ttfNot applicable412,57206-Jul-201220:15Not applicable
Setup.exe6.2.9200.20534262,65611-Oct-201205:50x86
Smiengine.dll6.2.9200.20773700,92812-Jul-201306:34x86
Spflvrnt.dll6.2.9200.2053423,55211-Oct-201204:24x86
Spprgrss.dll6.2.9200.2053451,71211-Oct-201205:12x86
Spwizeng.dll6.2.9200.20773364,88812-Jul-201307:04x86
Spwizres.dll6.2.9200.205347,68011-Oct-201204:49x86
Ssshim.dll6.2.9200.20773105,98412-Jul-201305:34x86
Testplugin.dll6.2.9200.2053448,12811-Oct-201205:12x86
Unattend.dll6.2.9200.20773214,36012-Jul-201307:04x86
Unbcl.dll6.2.9200.20534757,24811-Oct-201205:12x86
Upgloader.dll6.2.9200.20773590,33612-Jul-201304:22x86
Upgrade_frmwrk.xmlNot applicable12,71111-Oct-201200:46Not applicable
Upgreport.dll6.2.9200.20773380,92812-Jul-201304:36x86
Uxlib.dll6.2.9200.20534134,65611-Oct-201204:03x86
Uxlibres.dll6.2.9200.205342,56011-Oct-201204:49x86
W32uiimg.dll6.2.9200.205342,888,70411-Oct-201204:49x86
W32uires.dll6.2.9200.20773204,63212-Jul-201307:04x86
Warning.gifNot applicable59706-Jul-201220:18Not applicable
Wdsclient.dll6.2.9200.20773717,31212-Jul-201304:05x86
Wdsclientapi.dll6.2.9200.20534228,35211-Oct-201203:19x86
Wdscore.dll6.2.9200.20534225,79211-Oct-201203:51x86
Wdscsl.dll6.2.9200.2053457,34411-Oct-201203:28x86
Wdsimage.dll6.2.9200.20773705,02412-Jul-201304:09x86
Wdstptc.dll6.2.9200.20773509,44012-Jul-201304:08x86
Wdsutil.dll6.2.9200.2053449,66411-Oct-201205:12x86
Win32ui.dll6.2.9200.20773487,76812-Jul-201307:04x86
Winsetup.dll6.2.9200.207732,141,52812-Jul-201307:04x86
Actionqueue.dll6.2.9200.20773180,73612-Jul-201306:33x86
Audit.exe6.2.9200.1638469,12026-Jul-201203:20x86
Auditshd.exe6.2.9200.1638429,18426-Jul-201203:20x86
Diager.dll6.2.9200.1638431,74426-Jul-201203:19x86
Diagnostic.dll6.2.9200.16384130,04826-Jul-201203:19x86
Du.dll6.2.9200.1638456,32026-Jul-201203:18x86
Installeventres.dll6.2.9200.163847,68026-Jul-201202:44x86
Oobeldr.exe6.2.9200.1638457,85626-Jul-201203:20x86
Setup.exe6.2.9200.16384262,60026-Jul-201203:49x86
Setupsqm.exe6.2.9200.1638420,48026-Jul-201203:20x86
Setup_malgun_n.ttfNot applicable4,516,92402-Jun-201214:51Not applicable
Setup_meiryoui_n.ttfNot applicable5,649,60802-Jun-201214:51Not applicable
Setup_msjhui_n.ttfNot applicable8,276,90002-Jun-201214:51Not applicable
Setup_msyhui_n.ttfNot applicable8,351,68802-Jun-201214:51Not applicable
Setup_segoeuisl_n.ttfNot applicable307,56402-Jun-201214:51Not applicable
Spprgrss.dll6.2.9200.1638451,71226-Jul-201203:19x86
Unbcl.dll6.2.9200.20773757,24812-Jul-201306:34x86
W32uiimg.dll6.2.9200.163842,888,70426-Jul-201202:45x86
W32uires.dll6.2.9200.20773204,63212-Jul-201307:04x86
Wdsutil.dll6.2.9200.1638449,66426-Jul-201203:19x86
Win32ui.dll6.2.9200.20773487,76812-Jul-201307:04x86
Windeploy.exe6.2.9200.20773162,81612-Jul-201306:35x86
Winlgdep.dll6.2.9200.16384666,62426-Jul-201203:20x86
Winsetup.dll6.2.9200.207732,141,52812-Jul-201307:04x86
For all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Alert.gifNot applicable1,04606-Jul-201220:18Not applicable
Appcompat.xslNot applicable11,67306-Jul-201220:18Not applicable
Appcompat_bidi.xslNot applicable12,49806-Jul-201220:18Not applicable
Appcompat_detailed_bidi_txt.xslNot applicable13,37106-Jul-201220:18Not applicable
Appcompat_detailed_txt.xslNot applicable13,32606-Jul-201220:18Not applicable
Arunres.dll6.2.9200.205344,09611-Oct-201205:22x64
Autorun.dll6.2.9200.20773170,32812-Jul-201310:01x64
Cmisetup.dll6.2.9200.20773673,28012-Jul-201309:41x64
Compatprovider.dll6.2.9200.20534182,27211-Oct-201204:49x64
Diager.dll6.2.9200.2053438,91211-Oct-201205:44x64
Diagnostic.dll6.2.9200.20534156,67211-Oct-201205:44x64
Dism.exe6.2.9200.20773267,26412-Jul-201307:37x64
Dismcore.dll6.2.9200.20534385,02411-Oct-201204:48x64
Dismcoreps.dll6.2.9200.20534134,65611-Oct-201204:49x64
Dismhost.exe6.2.9200.20773172,03212-Jul-201307:05x64
Dismprov.dll6.2.9200.20773260,09612-Jul-201307:36x64
Drvmgrtn.dll1.0.0.0146,94411-Oct-201204:06x64
Du.dll6.2.9200.2077372,70412-Jul-201307:48x64
Folderprovider.dll6.2.9200.2053455,80811-Oct-201204:52x64
Hwcompat.dll6.2.9200.20773192,00012-Jul-201307:55x64
Locale.nlsNot applicable478,42411-Oct-201200:45Not applicable
Logprovider.dll6.2.9200.20773180,22412-Jul-201307:36x64
Nlsbres.dll6.2.9200.2053456,83211-Oct-201205:22x64
Offline.xmlNot applicable33,64411-Oct-201200:44Not applicable
Pnpibs.dll6.2.9200.2053482,43211-Oct-201205:44x64
Rollback.exe6.2.9200.20773130,65612-Jul-201310:27x64
Sdbapiu.dll3.1.0.1139,26411-Oct-201204:57x64
Segoeui.ttfNot applicable412,57206-Jul-201220:15Not applicable
Setup.exe6.2.9200.20773285,28012-Jul-201310:27x64
Smiengine.dll6.2.9200.20773894,46412-Jul-201309:41x64
Spflvrnt.dll6.2.9200.2053426,11211-Oct-201204:56x64
Spprgrss.dll6.2.9200.2077365,88012-Jul-201310:01x64
Spwizeng.dll6.2.9200.20773459,60812-Jul-201310:01x64
Spwizres.dll6.2.9200.205347,68011-Oct-201205:22x64
Ssshim.dll6.2.9200.20773118,27212-Jul-201308:15x64
Testplugin.dll6.2.9200.2077357,85612-Jul-201309:42x64
Unattend.dll6.2.9200.20773256,34412-Jul-201310:01x64
Unbcl.dll6.2.9200.20773970,24012-Jul-201309:41x64
Upgloader.dll6.2.9200.20773716,80012-Jul-201306:23x64
Upgrade_frmwrk.xmlNot applicable12,71111-Oct-201200:44Not applicable
Upgreport.dll6.2.9200.20773546,81612-Jul-201306:47x64
Uxlib.dll6.2.9200.20773183,12812-Jul-201310:01x64
Uxlibres.dll6.2.9200.205342,56011-Oct-201205:22x64
W32uiimg.dll6.2.9200.205342,888,70411-Oct-201205:22x64
W32uires.dll6.2.9200.20773204,63212-Jul-201310:01x64
Warning.gifNot applicable59706-Jul-201220:18Not applicable
Wdsclient.dll6.2.9200.20534843,26411-Oct-201203:29x64
Wdsclientapi.dll6.2.9200.20534285,18411-Oct-201203:34x64
Wdscore.dll6.2.9200.20773272,38412-Jul-201306:55x64
Wdscsl.dll6.2.9200.2053472,70411-Oct-201203:46x64
Wdsimage.dll6.2.9200.20773850,43212-Jul-201306:03x64
Wdstptc.dll6.2.9200.20534610,81611-Oct-201203:32x64
Wdsutil.dll6.2.9200.2053457,34411-Oct-201205:44x64
Win32ui.dll6.2.9200.20773605,52812-Jul-201310:01x64
Winsetup.dll6.2.9200.207732,582,87212-Jul-201310:01x64
Actionqueue.dll6.2.9200.20773210,94412-Jul-201309:39x64
Audit.exe6.2.9200.1638476,80026-Jul-201203:08x64
Auditshd.exe6.2.9200.1638431,23226-Jul-201203:08x64
Diager.dll6.2.9200.1638438,91226-Jul-201203:07x64
Diagnostic.dll6.2.9200.16384156,67226-Jul-201203:07x64
Du.dll6.2.9200.2077372,70412-Jul-201309:40x64
Installeventres.dll6.2.9200.163847,68026-Jul-201202:34x64
Oobeldr.exe6.2.9200.1638461,95226-Jul-201203:08x64
Setup.exe6.2.9200.20773285,28012-Jul-201310:27x64
Setupsqm.exe6.2.9200.1638424,06426-Jul-201203:08x64
Setup_malgun_n.ttfNot applicable4,516,92402-Jun-201214:51Not applicable
Setup_meiryoui_n.ttfNot applicable5,649,60802-Jun-201214:51Not applicable
Setup_msjhui_n.ttfNot applicable8,276,90002-Jun-201214:51Not applicable
Setup_msyhui_n.ttfNot applicable8,351,68802-Jun-201214:51Not applicable
Setup_segoeuisl_n.ttfNot applicable307,56402-Jun-201214:51Not applicable
Spprgrss.dll6.2.9200.2077365,88012-Jul-201310:01x64
Unbcl.dll6.2.9200.20773970,24012-Jul-201309:41x64
W32uiimg.dll6.2.9200.163842,888,70426-Jul-201202:35x64
W32uires.dll6.2.9200.20773204,63212-Jul-201310:01x64
Wdsutil.dll6.2.9200.1638457,34426-Jul-201203:07x64
Win32ui.dll6.2.9200.20773605,52812-Jul-201310:01x64
Windeploy.exe6.2.9200.20773196,60812-Jul-201309:43x64
Winlgdep.dll6.2.9200.16384680,44826-Jul-201203:07x64
Winsetup.dll6.2.9200.207732,582,87212-Jul-201310:01x64


↑ Back to the top


Status

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

↑ Back to the top


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.
Additional file information

Additional file information for Windows 8 and Windows Server 2012

Additional files for all supported x86-based versions of Windows 8
File nameX86_microsoft-windows-i..sedsetup-media-base_31bf3856ad364e35_6.2.9200.20773_none_9399bf4e137ea58e.manifest
File versionNot applicable
File size43,815
Date (UTC)12-Jul-2013
Time (UTC)20:37
PlatformNot applicable
File nameX86_microsoft-windows-setup-component_31bf3856ad364e35_6.2.9200.20773_none_2f6afc4e97bf6f4f.manifest
File versionNot applicable
File size24,741
Date (UTC)12-Jul-2013
Time (UTC)20:37
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameAmd64_microsoft-windows-i..sedsetup-media-base_31bf3856ad364e35_6.2.9200.20773_none_efb85ad1cbdc16c4.manifest
File versionNot applicable
File size43,819
Date (UTC)12-Jul-2013
Time (UTC)20:37
PlatformNot applicable
File nameAmd64_microsoft-windows-setup-component_31bf3856ad364e35_6.2.9200.20773_none_8b8997d2501ce085.manifest
File versionNot applicable
File size24,745
Date (UTC)12-Jul-2013
Time (UTC)20:37
PlatformNot applicable

↑ Back to the top


Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced, kb

↑ Back to the top

Article Info
Article ID : 2871318
Revision : 1
Created on : 1/7/2017
Published on : 10/9/2013
Exists online : False
Views : 227