Error message when Windows Deployment Service clients cannot obtain the boot image from a Windows Server 2008 R2-based WDS server: "PXE-E78: Could not locate boot server"

Symptoms

Consider the following scenario:

  • You install the Windows Deployment Services server role on a computer that is running Windows Server 2008 R2.

  • In the local area network, you configure a Dynamic Host Configuration Protocol (DHCP) server to use DHCP option code 43 that is required for Microsoft vendor-specific options. With this option code, Windows Deployment Services clients can connect to the Windows Deployment Services server.

In this scenario, the Windows Deployment Services client cannot obtain a boot image from the Windows Deployment Services server and returns the following error messages:

PXE-E78: Could not locate boot server.

PXE-M0F: Exiting Intel PXE ROM. OS not found.

Resolution

Hotfix information

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 Web site:

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.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 R2 on the computer. Additionally, you must have the Windows Deployment Services server role installed on the computer.

Registry information

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

Restart requirement

You may have to 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 MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important 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

File name

File version

File size

Date

Time

Platform

Binlsvc.dll

6.1.7600.20646

259,072

17-Feb-2010

08:12

x64

Wdspxe.dll

6.1.7600.20646

90,112

17-Feb-2010

08:13

x64

Wdssipr.dll

6.1.7600.20646

194,048

17-Feb-2010

08:13

x64

Wdssipr.dll.conf.ini

Not applicable

5,952

10-Jun-2009

21:06

Not 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 DHCP option code 43 that is required for Microsoft vendor-specific options, visit the following Microsoft Web site:

General information about DHCP option code 43 (Microsoft vendor-specific options)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

File name

Amd64_5c046e123754fcc3cad383de030b4ae3_31bf3856ad364e35_6.1.7600.20646_none_cebbcda7574029f2.manifest

File version

Not applicable

File size

731

Date (UTC)

18-Feb-2010

Time (UTC)

00:35

Platform

Not applicable

File name

Amd64_9aa24ab7064b97bf3fcea3385520ad02_31bf3856ad364e35_6.1.7600.20646_none_44a52a8c53bce065.manifest

File version

Not applicable

File size

722

Date (UTC)

18-Feb-2010

Time (UTC)

00:35

Platform

Not applicable

File name

Amd64_ba914fecdd07e621895049aee0d4631e_31bf3856ad364e35_6.1.7600.20646_none_224262bf19a3487a.manifest

File version

Not applicable

File size

723

Date (UTC)

18-Feb-2010

Time (UTC)

00:35

Platform

Not applicable

File name

Amd64_microsoft-windows-d..ervices-binl-server_31bf3856ad364e35_6.1.7600.20646_none_fa17f8dd6e4f31d4.manifest

File version

Not applicable

File size

36,016

Date (UTC)

17-Feb-2010

Time (UTC)

09:18

Platform

Not applicable

File name

Amd64_microsoft-windows-d..services-pxe-server_31bf3856ad364e35_6.1.7600.20646_none_82601580b28ad834.manifest

File version

Not applicable

File size

9,744

Date (UTC)

17-Feb-2010

Time (UTC)

09:21

Platform

Not applicable

File name

Amd64_microsoft-windows-d..simple-pxe-provider_31bf3856ad364e35_6.1.7600.20646_none_f26bb247f90fe4e7.manifest

File version

Not applicable

File size

4,546

Date (UTC)

17-Feb-2010

Time (UTC)

09:18

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

1,454

Date (UTC)

18-Feb-2010

Time (UTC)

00:35

Platform

Not applicable

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×