"TFTP download failed" error message during a PXE boot on a client computer that connects to a Windows Server 2008 R2-based Windows Deployment Services server

Article translations Article translations
Article ID: 2673007 - View products that this article applies to.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario. You perform a Pre-Boot Execution Environment (PXE) boot on a client computer that connects to a Windows Deployment Services server that is running Windows Server 2008 R2. The client computer downloads the Pxeboot.com binary file. In this scenario, you receive an error message that resembles the following:
TFTP download failed

Cause

This issue occurs because of an uninitialized UINT16 variable in the FindVendorOption function.

Resolution

Hotfix information

To resolve this issue, apply the following hotfix on the Windows Deployment Services server that is running Windows Server 2008 R2.
 
You must update the binary files on the Windows Deployment Services server after you install this hotfix. To do this, follow these steps:
  1. Run the following command to uninitialize the Windows Deployment Services server:
    Wdsutil /uninitialize-server
  2. Run the following command to reinitialize the Windows Deployment Services server:
    Wdsutil /initialize-server /reminst:<Reminst folder>
    For example, if the Reminst folder is named "RemoteInstall" and is located on drive C, run the following command to reinitialize the Windows Deployment Services server:
    dsutil /initialize-server /reminst:C:\RemoteInstall
  3. Run the following command to change the response policy to respond to all clients:
    WDSUTIL /set-Server /AnswerClients:[All|Known]
     
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 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, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
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 Server 2008 R2 or Windows Server 2008 R2 Service Pack 1 (SP1). For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply this hotfix, 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 Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" 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:
    Collapse this tableExpand this table
    VersionProductMilestoneService branch
    6.1.760 0.20xxxWindows Server 2008 R2RTMLDR
    6.1.760 1.21xxxWindows Server 2008 R2SP1LDR
  • 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 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Wdsmgfw.efi6.1.7600.21166531,96809-Mar-201212:31Not applicable
Wdsmgfw.efi6.1.7601.21939532,48009-Mar-201212:22Not applicable
Bootmgfw.efi6.1.7600.21166672,62409-Mar-201215:09Not applicable
Wdsmgfw.efi6.1.7600.21166531,96809-Mar-201212:31Not applicable
Bootmgfw.efi6.1.7601.21939673,13609-Mar-201215:37Not applicable
Wdsmgfw.efi6.1.7601.21939532,48009-Mar-201212:22Not applicable
Abortpxe.comNot applicable7910-Jun-200921:44Not applicable
Bootmgr.exe6.1.7600.21166523,12009-Mar-201214:14x86
Hdlscom1.comNot applicable24,78009-Mar-201208:06Not applicable
Hdlscom1.n12Not applicable24,76409-Mar-201208:06Not applicable
Hdlscom2.comNot applicable24,78009-Mar-201208:06Not applicable
Hdlscom2.n12Not applicable24,76409-Mar-201208:06Not applicable
Pxeboot.comNot applicable24,47609-Mar-201208:06Not applicable
Pxeboot.n12Not applicable24,47609-Mar-201208:06Not applicable
Wdsnbp.comNot applicable31,14009-Mar-201208:06Not applicable
Abortpxe.comNot applicable7910-Jun-200921:44Not applicable
Bootmgr.exe6.1.7601.21939523,63209-Mar-201213:57x86
Hdlscom1.comNot applicable24,78009-Mar-201208:07Not applicable
Hdlscom1.n12Not applicable24,76409-Mar-201208:07Not applicable
Hdlscom2.comNot applicable24,78009-Mar-201208:07Not applicable
Hdlscom2.n12Not applicable24,76409-Mar-201208:07Not applicable
Pxeboot.comNot applicable24,47609-Mar-201208:07Not applicable
Pxeboot.n12Not applicable24,47609-Mar-201208:07Not applicable
Wdsnbp.comNot applicable31,14009-Mar-201208:07Not applicable
Abortpxe.comNot applicable7910-Jun-200921:44Not applicable
Bootmgr.exe6.1.7600.21166523,12009-Mar-201214:14x86
Hdlscom1.comNot applicable24,78009-Mar-201208:06Not applicable
Hdlscom1.n12Not applicable24,76409-Mar-201208:06Not applicable
Hdlscom2.comNot applicable24,78009-Mar-201208:06Not applicable
Hdlscom2.n12Not applicable24,76409-Mar-201208:06Not applicable
Pxeboot.comNot applicable24,47609-Mar-201208:06Not applicable
Pxeboot.n12Not applicable24,47609-Mar-201208:06Not applicable
Wdsnbp.comNot applicable31,14009-Mar-201208:06Not applicable
Abortpxe.comNot applicable7905-Nov-201002:18Not applicable
Bootmgr.exe6.1.7601.21939523,63209-Mar-201213:57x86
Hdlscom1.comNot applicable24,78009-Mar-201208:07Not applicable
Hdlscom1.n12Not applicable24,76409-Mar-201208:07Not applicable
Hdlscom2.comNot applicable24,78009-Mar-201208:07Not applicable
Hdlscom2.n12Not applicable24,76409-Mar-201208:07Not applicable
Pxeboot.comNot applicable24,47609-Mar-201208:07Not applicable
Pxeboot.n12Not applicable24,47609-Mar-201208:07Not applicable
Wdsnbp.comNot applicable31,14009-Mar-201208:07Not applicable
Abortpxe.comNot applicable7910-Jun-200921:44Not applicable
Bootmgr.exe6.1.7600.21166523,12009-Mar-201214:14x86
Hdlscom1.comNot applicable24,78009-Mar-201208:06Not applicable
Hdlscom1.n12Not applicable24,76409-Mar-201208:06Not applicable
Hdlscom2.comNot applicable24,78009-Mar-201208:06Not applicable
Hdlscom2.n12Not applicable24,76409-Mar-201208:06Not applicable
Pxeboot.comNot applicable24,47609-Mar-201208:06Not applicable
Pxeboot.n12Not applicable24,47609-Mar-201208:06Not applicable
Wdsnbp.comNot applicable31,14009-Mar-201208:06Not applicable
Abortpxe.comNot applicable7905-Nov-201002:18Not applicable
Bootmgr.exe6.1.7601.21939523,63209-Mar-201213:57x86
Hdlscom1.comNot applicable24,78009-Mar-201208:07Not applicable
Hdlscom1.n12Not applicable24,76409-Mar-201208:07Not applicable
Hdlscom2.comNot applicable24,78009-Mar-201208:07Not applicable
Hdlscom2.n12Not applicable24,76409-Mar-201208:07Not applicable
Pxeboot.comNot applicable24,47609-Mar-201208:07Not applicable
Pxeboot.n12Not applicable24,47609-Mar-201208:07Not applicable
Wdsnbp.comNot applicable31,14009-Mar-201208:07Not applicable

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 the PXE boot process, visit the following Microsoft websites:
General information about the PXE boot process
How to deploy an image by using PXE
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

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_044e036ea487194c86d58fc7c9999caa_31bf3856ad364e35_6.1.7601.21939_none_c64149ada98ea201.manifest
File versionNot applicable
File size1,092
Date (UTC)10-Mar-2012
Time (UTC)00:14
PlatformNot applicable
File nameAmd64_211b439e35badf6899bd87a03876e6d0_31bf3856ad364e35_6.1.7601.21939_none_3b9b9ea8491c08e3.manifest
File versionNot applicable
File size724
Date (UTC)10-Mar-2012
Time (UTC)00:14
PlatformNot applicable
File nameAmd64_4a3e0be041af33eed73a1ee8fc173646_31bf3856ad364e35_6.1.7600.21166_none_1c1e8b33265edde1.manifest
File versionNot applicable
File size1,092
Date (UTC)10-Mar-2012
Time (UTC)00:14
PlatformNot applicable
File nameAmd64_50bd526c8ce17ff1cf3d996ab27aa8d8_31bf3856ad364e35_6.1.7601.21939_none_9afd7825c9105300.manifest
File versionNot applicable
File size1,062
Date (UTC)10-Mar-2012
Time (UTC)00:14
PlatformNot applicable
File nameAmd64_8a3c7e5a501ffe4a21b602eb74332d33_31bf3856ad364e35_6.1.7600.21166_none_7b9edce3db63db73.manifest
File versionNot applicable
File size724
Date (UTC)10-Mar-2012
Time (UTC)00:14
PlatformNot applicable
File nameAmd64_cb0d740085502bb76d9fb06de6b9d276_31bf3856ad364e35_6.1.7600.21166_none_59075963c69c5c2a.manifest
File versionNot applicable
File size1,062
Date (UTC)10-Mar-2012
Time (UTC)00:14
PlatformNot applicable
File nameAmd64_microsoft-windows-bootenvironment-pxe_31bf3856ad364e35_6.1.7600.21166_none_49e7e627c4880ed7.manifest
File versionNot applicable
File size3,837
Date (UTC)09-Mar-2012
Time (UTC)15:41
PlatformNot applicable
File nameAmd64_microsoft-windows-bootenvironment-pxe_31bf3856ad364e35_6.1.7601.21939_none_4bf1dd93c1933cda.manifest
File versionNot applicable
File size3,837
Date (UTC)09-Mar-2012
Time (UTC)16:06
PlatformNot applicable
File nameAmd64_microsoft-windows-d..ices-boot-files-x64_31bf3856ad364e35_6.1.7600.21166_none_18bc8202f10298ce.manifest
File versionNot applicable
File size4,402
Date (UTC)09-Mar-2012
Time (UTC)15:36
PlatformNot applicable
File nameAmd64_microsoft-windows-d..ices-boot-files-x64_31bf3856ad364e35_6.1.7601.21939_none_1ac6796eee0dc6d1.manifest
File versionNot applicable
File size4,402
Date (UTC)09-Mar-2012
Time (UTC)16:02
PlatformNot applicable
File nameX86_microsoft-windows-bootenvironment-pxe_31bf3856ad364e35_6.1.7600.21166_none_edc94aa40c2a9da1.manifest
File versionNot applicable
File size9,879
Date (UTC)09-Mar-2012
Time (UTC)14:41
PlatformNot applicable
File nameX86_microsoft-windows-bootenvironment-pxe_31bf3856ad364e35_6.1.7601.21939_none_efd342100935cba4.manifest
File versionNot applicable
File size9,879
Date (UTC)09-Mar-2012
Time (UTC)14:25
PlatformNot applicable
File nameX86_microsoft-windows-d..ices-boot-files-x64_31bf3856ad364e35_6.1.7600.21166_none_bc9de67f38a52798.manifest
File versionNot applicable
File size9,827
Date (UTC)09-Mar-2012
Time (UTC)14:39
PlatformNot applicable
File nameX86_microsoft-windows-d..ices-boot-files-x64_31bf3856ad364e35_6.1.7601.21939_none_bea7ddeb35b0559b.manifest
File versionNot applicable
File size9,827
Date (UTC)09-Mar-2012
Time (UTC)14:22
PlatformNot applicable
File nameX86_microsoft-windows-d..ices-boot-files-x86_31bf3856ad364e35_6.1.7600.21166_none_bc9fb98338a38d88.manifest
File versionNot applicable
File size9,827
Date (UTC)09-Mar-2012
Time (UTC)14:42
PlatformNot applicable
File nameX86_microsoft-windows-d..ices-boot-files-x86_31bf3856ad364e35_6.1.7601.21939_none_bea9b0ef35aebb8b.manifest
File versionNot applicable
File size9,827
Date (UTC)09-Mar-2012
Time (UTC)14:28
PlatformNot applicable

Properties

Article ID: 2673007 - Last Review: December 20, 2012 - Revision: 2.0
Applies to
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Foundation
  • Windows Server 2008 R2 Standard
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbexpertiseinter kbsurveynew KB2673007

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com