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.

Slow PXE boot performance on a UEFI computer that's running Windows 8.1 or Windows Server 2012 R2


View products that this article applies to.

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.

↑ Back to the top


Cause

This problem occurs because during the PXE boot, the boot image takes a long time to download.

↑ Back to the top


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: 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.

Installation information

To apply this hotfix, follow these steps:
  1. 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:
    1. Run the WDS Microsoft Management Console (MMC) snap-in or the Windows Deployment Services command-line tool (Wdsutil.exe).
    2. Locate the boot image that you plan to use.
    3. 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.
  2. 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:
    1. Open an administrative Command Prompt window. For example, right-click in the lower-left corner of your desktop, and then click Command prompt (admin).
    2. Type the following command, and then press Enter:

      cd \bin
    3. Type the following command, and then press Enter to obtain information about the Wim:

      dism.exe /get-wiminfo /wimfile:c:\bin\exportedwim.wim
      Note This is to determine whether you have one or two indexes in this .wim file.
    4. 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
    5. Type the following command to mount the .wim file:

      dism /mount-wim /wimfile:c:\bin\exportedwim.wim /index:2 /mountdir:c:\bin\mount
      Note 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.
  3. 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:
    1. To add this update to the boot image, run the following command:

      dism /image:C:\winpe_x86\mount /Add-Package /PackagePath:Path_to_package

    2. To commit the changes after the update package is successfully installed, run the following command:

      dism.exe /unmounts-wim /mountdir:c:\bin\mount /commit
  4. 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:
    1. Open the WDS MMC snap-in.
    2. Right-click Boot Images, click Add Boot Image, and then specify the path of the updated Boot.wim file.
    3. 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.

↑ Back to the top


File information
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 notes

Important 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.

    VersionProductMilestoneService branch
    6.3.960 0.20 xxxWindows 8.1 and Windows Server 2012 R2RTMLDR
  • 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 nameFile versionFile sizeDateTimePlatform
Bootmgfw.efi6.3.9600.207191,358,14416-Jul-201407:44Not Applicable
For all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Bootmgfw.efi6.3.9600.207191,617,21616-Jul-201409:28Not Applicable
Abortpxe.comNot Applicable7918-Jun-201312:18Not Applicable
Hdlscom1.comNot Applicable25,66218-Jun-201312:18Not Applicable
Hdlscom1.n12Not Applicable25,64618-Jun-201312:18Not Applicable
Hdlscom2.comNot Applicable25,66218-Jun-201312:18Not Applicable
Hdlscom2.n12Not Applicable25,64618-Jun-201312:18Not Applicable
Pxeboot.comNot Applicable25,35818-Jun-201312:18Not Applicable
Pxeboot.n12Not Applicable25,35818-Jun-201312:18Not Applicable
Wdsnbp.comNot Applicable30,83218-Jun-201312:18Not Applicable
Abortpxe.comNot Applicable7918-Jun-201312:18Not Applicable
Hdlscom1.comNot Applicable25,66218-Jun-201312:18Not Applicable
Hdlscom1.n12Not Applicable25,64618-Jun-201312:18Not Applicable
Hdlscom2.comNot Applicable25,66218-Jun-201312:18Not Applicable
Hdlscom2.n12Not Applicable25,64618-Jun-201312:18Not Applicable
Pxeboot.comNot Applicable25,35818-Jun-201312:18Not Applicable
Pxeboot.n12Not Applicable25,35818-Jun-201312:18Not Applicable
Wdsnbp.comNot Applicable30,83218-Jun-201312:18Not 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 namePackage_1_for_kb2974735~31bf3856ad364e35~x86~~6.3.1.0.mum
File versionNot Applicable
File size1,842
Date (UTC)21-Jul-2014
Time (UTC)17:27
PlatformNot Applicable
File namePackage_2_for_kb2974735~31bf3856ad364e35~x86~~6.3.1.0.mum
File versionNot Applicable
File size2,062
Date (UTC)21-Jul-2014
Time (UTC)17:27
PlatformNot Applicable
File namePackage_for_kb2974735_rtm_gm~31bf3856ad364e35~x86~~6.3.1.0.mum
File versionNot Applicable
File size1,681
Date (UTC)21-Jul-2014
Time (UTC)17:27
PlatformNot Applicable
File namePackage_for_kb2974735_rtm~31bf3856ad364e35~x86~~6.3.1.0.mum
File versionNot Applicable
File size1,889
Date (UTC)21-Jul-2014
Time (UTC)17:27
PlatformNot Applicable
File nameX86_4c057edb0c71359f9faaaeeb30ed09b4_31bf3856ad364e35_6.3.9600.20719_none_e721c0388cec07e1.manifest
File versionNot Applicable
File size724
Date (UTC)21-Jul-2014
Time (UTC)17:27
PlatformNot Applicable
File nameX86_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_6.3.9600.20719_none_1cfb00c1d0d9c2b1.manifest
File versionNot Applicable
File size4,077
Date (UTC)16-Jul-2014
Time (UTC)08:09
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File nameAmd64_3f7760b4796dadeb75b7b604cd66dc7c_31bf3856ad364e35_6.3.9600.20719_none_fdd8e7aea2bb2d92.manifest
File versionNot Applicable
File size734
Date (UTC)21-Jul-2014
Time (UTC)17:29
PlatformNot Applicable
File nameAmd64_60ff6c5ad8e4ccb65d00f5f82b72fec0_31bf3856ad364e35_6.3.9600.20719_none_0cee098afb556a9d.manifest
File versionNot Applicable
File size728
Date (UTC)21-Jul-2014
Time (UTC)17:29
PlatformNot Applicable
File nameAmd64_c0759fc4a16bba8ad849b3007b9be6a4_31bf3856ad364e35_6.3.9600.20719_none_3a66a20d46fd3909.manifest
File versionNot Applicable
File size1,112
Date (UTC)21-Jul-2014
Time (UTC)17:29
PlatformNot Applicable
File nameAmd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_6.3.9600.20719_none_79199c45893733e7.manifest
File versionNot Applicable
File size4,083
Date (UTC)16-Jul-2014
Time (UTC)10:10
PlatformNot Applicable
File nameAmd64_microsoft-windows-d..files-x64-minkernel_31bf3856ad364e35_6.3.9600.20719_none_fd2471c439107eed.manifest
File versionNot Applicable
File size3,746
Date (UTC)16-Jul-2014
Time (UTC)10:10
PlatformNot Applicable
File namePackage_1_for_kb2974735~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size1,852
Date (UTC)21-Jul-2014
Time (UTC)17:29
PlatformNot Applicable
File namePackage_2_for_kb2974735~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,525
Date (UTC)21-Jul-2014
Time (UTC)17:29
PlatformNot Applicable
File namePackage_3_for_kb2974735~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,824
Date (UTC)21-Jul-2014
Time (UTC)17:29
PlatformNot Applicable
File namePackage_for_kb2974735_rtm_gm~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size1,969
Date (UTC)21-Jul-2014
Time (UTC)17:29
PlatformNot Applicable
File namePackage_for_kb2974735_rtm~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,571
Date (UTC)21-Jul-2014
Time (UTC)17:29
PlatformNot Applicable
File nameX86_microsoft-windows-d..files-x64-minkernel_31bf3856ad364e35_6.3.9600.20719_none_a105d64080b30db7.manifest
File versionNot Applicable
File size9,946
Date (UTC)16-Jul-2014
Time (UTC)08:09
PlatformNot Applicable
File nameX86_microsoft-windows-d..files-x86-minkernel_31bf3856ad364e35_6.3.9600.20719_none_9946667a93fd7ba7.manifest
File versionNot Applicable
File size10,723
Date (UTC)16-Jul-2014
Time (UTC)08:09
PlatformNot Applicable

↑ 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


References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbsurveynew, kbbug

↑ Back to the top

Article Info
Article ID : 2974735
Revision : 1
Created on : 1/7/2017
Published on : 9/9/2014
Exists online : False
Views : 233