Symptoms
On a Unified Extensible Firmware Interface (UEFI) computer that's running Windows 8.1 or Windows Server 2012 R2, you discover that PXE boot performance is slower than expected.
Cause
This problem occurs because during the PXE boot, the boot image takes a long time to download.
Resolution
To resolve this problem, apply the following hotfix.
Hotfix information
A supported hotfix is available from Microsoft Support. 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
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, contact 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.
Installation information
To apply this hotfix, follow these steps:
-
Export the Windows 8.1 or Windows Server 2012 R2 boot image from the Windows Deployment Services (WDS) server. To do this, follow these steps:
-
Run the WDS Microsoft Management Console (MMC) snap-in or the Windows Deployment Services command-line tool (Wdsutil.exe).
-
Locate the boot image that you plan to use.
-
Right-click that image, and then export it to a known location. For example, you might create a folder on the root of drive C, such as C:\bin.
-
-
Mount the exported boot image by using the index number. For example, mount index 2 of the boot image. To do this, follow these steps:
-
Open an administrative Command Prompt window. For example, right-click in the lower-left corner of your desktop, and then click Command prompt (admin).
-
Type the following command, and then press Enter:
cd \bin
-
Type the following command, and then press Enter to obtain information about the Wim:
dism.exe /get-wiminfo /wimfile:c:\bin\exportedwim.wimNote This is to determine whether you have one or two indexes in this .wim file.
-
Create a new mount folder where the .wim file will be mounted for file injection. To do this, type the following command, and then press Enter:
md c:\bin\mount
-
Type the following command to mount the .wim file:
dism /mount-wim /wimfile:c:\bin\exportedwim.wim /index:2 /mountdir:c:\bin\mountNote If there are two indexes, such as when you use the default boot.wim file to create boot.wim for WDS, use the second index.
-
-
Install the .msu package to the Windows 8.1 or Windows Server 2012 R2 boot.wim file to add this update to the boot image. Note Although the referenced article is for Windows 7, the commands to add this update to the boot image still apply. Specifically, follow these steps to add this update to the boot image:
-
To add this update to the boot image, run the following command:
dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:Path_to_package
-
To commit the changes after the update package is successfully installed, run the following command:
dism.exe /unmounts-wim /mountdir:c:\bin\mount /commit
-
-
Replace the boot image on the WDS server by using the updated boot image. To add the updated Boot.wim file back to the WDS server, follow these steps or use the Wdsutil.exe utility:
-
Open the WDS MMC snap-in.
-
Right-click Boot Images, click Add Boot Image, and then specify the path of the updated Boot.wim file.
-
After the updated boot image is added back to the WDS server, right-click the boot image to make sure that it's enabled.
-
Prerequisites
To apply this update in Windows 8.1 or Windows Server 2012 R2, you must first have update 2919355 installed.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any previously released hotfix.
The English (United States) 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.1 and Windows Server 2012 R2 file information and notesImportant Windows 8.1 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" 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.1" 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.3.960 0.20 xxx
Windows 8.1 and Windows Server 2012 R2
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 8.1 and Windows Server 2012 R2" 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.1
File name |
File version |
File size |
Date |
Time |
Platform |
---|---|---|---|---|---|
Bootmgfw.efi |
6.3.9600.20719 |
1,358,144 |
16-Jul-2014 |
07:44 |
Not Applicable |
For all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File name |
File version |
File size |
Date |
Time |
Platform |
---|---|---|---|---|---|
Bootmgfw.efi |
6.3.9600.20719 |
1,617,216 |
16-Jul-2014 |
09:28 |
Not Applicable |
Abortpxe.com |
Not Applicable |
79 |
18-Jun-2013 |
12:18 |
Not Applicable |
Hdlscom1.com |
Not Applicable |
25,662 |
18-Jun-2013 |
12:18 |
Not Applicable |
Hdlscom1.n12 |
Not Applicable |
25,646 |
18-Jun-2013 |
12:18 |
Not Applicable |
Hdlscom2.com |
Not Applicable |
25,662 |
18-Jun-2013 |
12:18 |
Not Applicable |
Hdlscom2.n12 |
Not Applicable |
25,646 |
18-Jun-2013 |
12:18 |
Not Applicable |
Pxeboot.com |
Not Applicable |
25,358 |
18-Jun-2013 |
12:18 |
Not Applicable |
Pxeboot.n12 |
Not Applicable |
25,358 |
18-Jun-2013 |
12:18 |
Not Applicable |
Wdsnbp.com |
Not Applicable |
30,832 |
18-Jun-2013 |
12:18 |
Not Applicable |
Abortpxe.com |
Not Applicable |
79 |
18-Jun-2013 |
12:18 |
Not Applicable |
Hdlscom1.com |
Not Applicable |
25,662 |
18-Jun-2013 |
12:18 |
Not Applicable |
Hdlscom1.n12 |
Not Applicable |
25,646 |
18-Jun-2013 |
12:18 |
Not Applicable |
Hdlscom2.com |
Not Applicable |
25,662 |
18-Jun-2013 |
12:18 |
Not Applicable |
Hdlscom2.n12 |
Not Applicable |
25,646 |
18-Jun-2013 |
12:18 |
Not Applicable |
Pxeboot.com |
Not Applicable |
25,358 |
18-Jun-2013 |
12:18 |
Not Applicable |
Pxeboot.n12 |
Not Applicable |
25,358 |
18-Jun-2013 |
12:18 |
Not Applicable |
Wdsnbp.com |
Not Applicable |
30,832 |
18-Jun-2013 |
12:18 |
Not Applicable |
Additional file information for Windows 8.1 and for Windows Server 2012 R2
Additional files for all supported x86-based versions of Windows 8.1
File name |
Package_1_for_kb2974735~31bf3856ad364e35~x86~~6.3.1.0.mum |
File version |
Not Applicable |
File size |
1,842 |
Date (UTC) |
21-Jul-2014 |
Time (UTC) |
17:27 |
Platform |
Not Applicable |
File name |
Package_2_for_kb2974735~31bf3856ad364e35~x86~~6.3.1.0.mum |
File version |
Not Applicable |
File size |
2,062 |
Date (UTC) |
21-Jul-2014 |
Time (UTC) |
17:27 |
Platform |
Not Applicable |
File name |
Package_for_kb2974735_rtm_gm~31bf3856ad364e35~x86~~6.3.1.0.mum |
File version |
Not Applicable |
File size |
1,681 |
Date (UTC) |
21-Jul-2014 |
Time (UTC) |
17:27 |
Platform |
Not Applicable |
File name |
Package_for_kb2974735_rtm~31bf3856ad364e35~x86~~6.3.1.0.mum |
File version |
Not Applicable |
File size |
1,889 |
Date (UTC) |
21-Jul-2014 |
Time (UTC) |
17:27 |
Platform |
Not Applicable |
File name |
X86_4c057edb0c71359f9faaaeeb30ed09b4_31bf3856ad364e35_6.3.9600.20719_none_e721c0388cec07e1.manifest |
File version |
Not Applicable |
File size |
724 |
Date (UTC) |
21-Jul-2014 |
Time (UTC) |
17:27 |
Platform |
Not Applicable |
File name |
X86_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_6.3.9600.20719_none_1cfb00c1d0d9c2b1.manifest |
File version |
Not Applicable |
File size |
4,077 |
Date (UTC) |
16-Jul-2014 |
Time (UTC) |
08:09 |
Platform |
Not Applicable |
Additional files for all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File name |
Amd64_3f7760b4796dadeb75b7b604cd66dc7c_31bf3856ad364e35_6.3.9600.20719_none_fdd8e7aea2bb2d92.manifest |
File version |
Not Applicable |
File size |
734 |
Date (UTC) |
21-Jul-2014 |
Time (UTC) |
17:29 |
Platform |
Not Applicable |
File name |
Amd64_60ff6c5ad8e4ccb65d00f5f82b72fec0_31bf3856ad364e35_6.3.9600.20719_none_0cee098afb556a9d.manifest |
File version |
Not Applicable |
File size |
728 |
Date (UTC) |
21-Jul-2014 |
Time (UTC) |
17:29 |
Platform |
Not Applicable |
File name |
Amd64_c0759fc4a16bba8ad849b3007b9be6a4_31bf3856ad364e35_6.3.9600.20719_none_3a66a20d46fd3909.manifest |
File version |
Not Applicable |
File size |
1,112 |
Date (UTC) |
21-Jul-2014 |
Time (UTC) |
17:29 |
Platform |
Not Applicable |
File name |
Amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_6.3.9600.20719_none_79199c45893733e7.manifest |
File version |
Not Applicable |
File size |
4,083 |
Date (UTC) |
16-Jul-2014 |
Time (UTC) |
10:10 |
Platform |
Not Applicable |
File name |
Amd64_microsoft-windows-d..files-x64-minkernel_31bf3856ad364e35_6.3.9600.20719_none_fd2471c439107eed.manifest |
File version |
Not Applicable |
File size |
3,746 |
Date (UTC) |
16-Jul-2014 |
Time (UTC) |
10:10 |
Platform |
Not Applicable |
File name |
Package_1_for_kb2974735~31bf3856ad364e35~amd64~~6.3.1.0.mum |
File version |
Not Applicable |
File size |
1,852 |
Date (UTC) |
21-Jul-2014 |
Time (UTC) |
17:29 |
Platform |
Not Applicable |
File name |
Package_2_for_kb2974735~31bf3856ad364e35~amd64~~6.3.1.0.mum |
File version |
Not Applicable |
File size |
2,525 |
Date (UTC) |
21-Jul-2014 |
Time (UTC) |
17:29 |
Platform |
Not Applicable |
File name |
Package_3_for_kb2974735~31bf3856ad364e35~amd64~~6.3.1.0.mum |
File version |
Not Applicable |
File size |
2,824 |
Date (UTC) |
21-Jul-2014 |
Time (UTC) |
17:29 |
Platform |
Not Applicable |
File name |
Package_for_kb2974735_rtm_gm~31bf3856ad364e35~amd64~~6.3.1.0.mum |
File version |
Not Applicable |
File size |
1,969 |
Date (UTC) |
21-Jul-2014 |
Time (UTC) |
17:29 |
Platform |
Not Applicable |
File name |
Package_for_kb2974735_rtm~31bf3856ad364e35~amd64~~6.3.1.0.mum |
File version |
Not Applicable |
File size |
2,571 |
Date (UTC) |
21-Jul-2014 |
Time (UTC) |
17:29 |
Platform |
Not Applicable |
File name |
X86_microsoft-windows-d..files-x64-minkernel_31bf3856ad364e35_6.3.9600.20719_none_a105d64080b30db7.manifest |
File version |
Not Applicable |
File size |
9,946 |
Date (UTC) |
16-Jul-2014 |
Time (UTC) |
08:09 |
Platform |
Not Applicable |
File name |
X86_microsoft-windows-d..files-x86-minkernel_31bf3856ad364e35_6.3.9600.20719_none_9946667a93fd7ba7.manifest |
File version |
Not Applicable |
File size |
10,723 |
Date (UTC) |
16-Jul-2014 |
Time (UTC) |
08:09 |
Platform |
Not Applicable |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology that Microsoft uses to describe software updates.