This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Applies to:
This walkthrough describes how to configure a PXE server to load Windows PE by booting a client computer from the network. Using the Windows PE tools and a Windows 10 image file, you can install Windows 10 from the network.
All four of the roles specified above can be hosted on the same computer or each can be on a separate computer.
On the deployment computer, select Start, and type deployment.
Right-click Deployment and Imaging Tools Environment and then select Run as administrator. The Deployment and Imaging Tools Environment shortcut opens a Command Prompt window and automatically sets environment variables to point to all the necessary tools.
Run the following command to copy the base Windows PE files into a new folder. The script requires two arguments: hardware architecture and destination location. The value of <architecture> can be x86, amd64, or arm and <destination> is a path to a local directory. If the directory doesn't already exist, it will be created.
copype.cmd <architecture> <destination>
For example, the following command copies amd64 architecture files to the C:\winpe_amd64 directory:
copype.cmd amd64 C:\winpe_amd64
The script creates the destination directory structure and copies all the necessary files for that architecture. In the previous example, the following directories are created:
C:\winpe_amd64
C:\winpe_amd64\fwfiles
C:\winpe_amd64\media
C:\winpe_amd64\mount
Mount the base Windows PE image (winpe.wim) to the \mount directory using the DISM tool. Mounting an image file unpacks the file contents into a folder so that you can make changes directly or by using tools such as DISM. See the following example.
dism.exe /mount-image /imagefile:c:\winpe_amd64\media\sources\boot.wim /index:1 /mountdir:C:\winpe_amd64\mount
Verify that the message The operation completed successfully is displayed.
Note
To view currently mounted images, enter dism.exe /get-MountedWiminfo.
Map a network share to the root TFTP directory on the PXE/TFTP server and create a \Boot folder. Consult your TFTP server documentation to determine the root TFTP server directory, then enable sharing for this directory, and verify it can be accessed on the network. In the following example, the PXE server name is PXE-1 and the TFTP root directory is shared using a network path of \\PXE-1\TFTPRoot:
net.exe use y: \\PXE-1\TFTPRoot
y:
md Boot
Copy the PXE boot files from the mounted directory to the \boot folder. For example:
copy c:\winpe_amd64\mount\windows\boot\pxe\*.* y:\Boot
Copy the boot.sdi file to the PXE/TFTP server.
copy C:\winpe_amd64\media\boot\boot.sdi y:\Boot
Copy the bootable Windows PE image (boot.wim) to the \boot folder.
copy C:\winpe_amd64\media\sources\boot.wim y:\Boot
(Optional) Copy TrueType fonts to the \boot folder
copy C:\winpe_amd64\media\Boot\Fonts y:\Boot\Fonts
Create a BCD store using bcdedit.exe:
bcdedit.exe /createstore c:\BCD
Configure RAMDISK settings:
bcdedit.exe /store c:\BCD /create {ramdiskoptions} /d "Ramdisk options"
bcdedit.exe /store c:\BCD /set {ramdiskoptions} ramdisksdidevice boot
bcdedit.exe /store c:\BCD /set {ramdiskoptions} ramdisksdipath \Boot\boot.sdi
bcdedit.exe /store c:\BCD /create /d "winpe boot image" /application osloader
The last command will return a GUID, for example:
The entry {a4f89c62-2142-11e6-80b6-00155da04110} was successfully created.
Copy this GUID for use in the next set of commands. In each command shown, replace "GUID1" with your GUID.
Create a new boot application entry for the Windows PE image:
bcdedit.exe /store c:\BCD /set {GUID1} device ramdisk=[boot]\Boot\boot.wim,{ramdiskoptions}
bcdedit.exe /store c:\BCD /set {GUID1} path \windows\system32\winload.exe
bcdedit.exe /store c:\BCD /set {GUID1} osdevice ramdisk=[boot]\Boot\boot.wim,{ramdiskoptions}
bcdedit.exe /store c:\BCD /set {GUID1} systemroot \windows
bcdedit.exe /store c:\BCD /set {GUID1} detecthal Yes
bcdedit.exe /store c:\BCD /set {GUID1} winpe Yes
Configure BOOTMGR settings (remember to replace GUID1 in the third command with your GUID):
bcdedit.exe /store c:\BCD /create {bootmgr} /d "boot manager"
bcdedit.exe /store c:\BCD /set {bootmgr} timeout 30
bcdedit.exe /store c:\BCD -displayorder {GUID1} -addlast
Copy the BCD file to your TFTP server:
copy c:\BCD \\PXE-1\TFTPRoot\Boot\BCD
Your PXE/TFTP server is now configured. You can view the BCD settings that have been configured using the command bcdedit.exe /store <BCD file location> /enum all. See the following example. Note: Your GUID will be different than the one shown below.
C:\>bcdedit.exe /store C:\BCD /enum all
Windows Boot Manager
--------------------
identifier {bootmgr}
description boot manager
displayorder {a4f89c62-2142-11e6-80b6-00155da04110}
timeout 30
Windows Boot Loader
-------------------
identifier {a4f89c62-2142-11e6-80b6-00155da04110}
device ramdisk=[boot]\Boot\boot.wim,{ramdiskoptions}
description winpe boot image
osdevice ramdisk=[boot]\Boot\boot.wim,{ramdiskoptions}
systemroot \Windows
detecthal Yes
winpe Yes
Setup Ramdisk Options
---------------------
identifier {ramdiskoptions}
description ramdisk options
ramdisksdidevice boot
ramdisksdipath \Boot\boot.sdi
Tip
If you start the PXE boot process, but receive the error The boot configuration data for your PC is missing or contains error, then verify that \boot directory is installed under the correct TFTP server root directory. In the example used here the name of this directory is TFTPRoot, but your TFTP server might be different.
The following process summarizes the PXE client boot.
Note
The following assumes that the client and PXE server are on the same network/subnet/vlan or that PXE requests have been appropriately forwarded from the client to the PXE server using IP helpers configured in the router or switch. For more information about IP helpers, see Configuring Your Router to Forward Broadcasts.
A client contacts the PXE server. When the client is on a different network/subnet/vlan as the PXE server, the client is routed to the PXE server using the IP helpers.
The PXE server sends DHCP options 060 (client identifier PXEClient), 066 (boot server host name) and 067 (boot file name) to the client.
The client downloads boot\PXEboot.n12 from the TFTP server based on DHCP option 067 boot file name value received from the PXE server.
PXEboot.n12 immediately begins a network boot.
The client downloads boot\bootmgr.exe and the boot\BCD file from the TFTP server.
Note
The BCD store must reside in the \boot directory on the TFTP server and must be named BCD.
Bootmgr.exe reads the BCD operating system entries and downloads boot\boot.sdi and the Windows PE image (boot\boot.wim). Optional files that can also be downloaded include TrueType fonts (boot\Fonts\wgl4_boot.ttf) and the hibernation state file (\hiberfil.sys) if these files are present.
Bootmgr.exe starts Windows PE by calling winload.exe within the Windows PE image.
Windows PE loads, a command prompt opens and wpeinit.exe is run to initialize Windows PE.
The Windows PE client provides access to tools like imagex.exe, diskpart.exe, and bcdboot.exe using the Windows PE command prompt. With the help of these tools accompanied by a Windows 10 image file, the destination computer can be formatted properly to load a full Windows 10 operating system.
Training
Module
Troubleshoot Windows startup - Training
This module examines the Windows startup architecture and discusses the methods used to troubleshoot client startup issues.
Certification
Microsoft 365 Certified: Endpoint Administrator Associate - Certifications
Plan and execute an endpoint deployment strategy, using essential elements of modern management, co-management approaches, and Microsoft Intune integration.