Table of Contents

Build a Windows PE image

When a PC starts from the network, it first loads Windows PE. Windows PE is a small version of Windows that runs from memory. The SharpDay Deploy PE client runs inside it, talks to the server and sets up the PC.

This page shows how to make the Windows PE image, set it up for your PCs and build it.

Boot folders

A boot folder holds the files a PC downloads when it starts from the network. You can see them on Boot Files > Boot Files. On the server, each one is a folder inside the Boot Files folder of the share. See The share folder.

A Windows PE boot folder has these files:

File What it is
bootmgfw.efi The boot manager. This is the first file a PC starts.
BCD The boot settings the boot manager reads.
boot.sdi The RAM disk Windows PE starts from.
boot.wim The Windows PE image.
Fonts A folder of fonts for the boot manager.

The primary boot folder

Each processor family has 1 primary boot folder: 1 for x64 PCs and 1 for ARM64 PCs. It shows a Primary label in the list. A PC that starts from the network gets the primary folder for its processor family.

  • To change it, select the gear (More options) on a folder, then Make Primary.
  • The server always keeps 1 primary folder for each family. If you turn off the primary folder with Disable, another folder of the same family takes over.
  • A folder marked Disabled is never sent to a PC.
  • A rule on the Reroute page can send some PCs to a different boot folder.

What you need first

  • The Windows ADK and its Windows PE add-on from Microsoft, installed on the server. Get them from Microsoft's ADK download page.
  • Install both from the same release, in the default place: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit.
  • For ARM64 images, the ARM64 files of the Windows PE add-on. If they are missing, the server tells you to add the ARM64 architecture in the Windows PE add-on installer.
  • A role that can change Boot Files. If the buttons on this page are greyed out, ask an administrator. See Users and roles.

The Console tells you if the ADK is missing or out of date in 3 places:

Where What it shows
The Checks step of first time setup The Windows ADK and Windows PE add-on rows, and an ADK update row when a newer kit is out. A row has a Download button when there is something to install. See First time setup.
About > About The Windows ADK card: Installed, Version, Windows PE add-on, Newest Microsoft kit and ISO boot image, with any advice below. Open Microsoft's ADK download page opens the download page.
Build, inside a boot folder Any ADK warning that affects a build.
Note

This advice never stops a build. SharpDay Deploy never installs or removes the ADK, and you can keep an older one if you need it.

Make a boot folder with Windows PE in it

There are 2 ways to put a Windows PE image in a boot folder.

Create a new boot folder

  1. Go to Boot Files > Boot Files.
  2. Select Create boot folder. If there are no boot folders yet, select Add new.
  3. In Folder name, type a name, for example Windows 11 x64.
  4. Under What goes in it, select Windows PE.
  5. Under Which machines will boot from this image?, select the processor family. See Choose the processor family.
  6. Under Which boot files should it hand out?, select Old boot files [Most Compatible] or New boot files. See Secure Boot.
  7. Select Create.

The server copies the Windows PE image, boot.sdi and the fonts out of the ADK. It then puts in the boot manager and writes new boot settings. A card at the top of the tab shows its progress. Copying the image can take a while.

When the card says the folder is ready, select Dismiss. If something goes wrong, the server removes the part made folder, and the card says why.

The other choices under What goes in it are iPXE and Empty folder. They do not make a Windows PE image.

Generate a Windows PE image in a folder you have

Use this for a boot folder that has no .wim file yet, such as an empty folder.

  1. On Boot Files > Boot Files, double-click the folder to open it.
  2. Select Generate PE WIM.
  3. The Generate a Windows PE image window asks Which machines will boot from this image?. Select the processor family.
  4. Select Generate.

The server copies the Windows PE image out of the ADK into the folder as boot.wim. This can take a few minutes. The folder then shows its image pages in the menu on the left.

This way only adds boot.wim. Until you build the image, Files shows This folder is not ready to boot a machine. A full build adds the other files.

Choose the processor family

Choice Use it for
x64 Intel and AMD PCs. Most desktops and laptops use this.
ARM64 Snapdragon and other ARM based PCs.

A PC can only start from a boot image of its own processor family. If you have both kinds of PC, make 1 boot folder for each.

There is no language choice. The server uses the English (en-us) Windows PE image from the ADK.

Set up the image

Once a boot folder has a boot.wim, open it to see this menu on the left:

Section What it is for
Files The files in the folder, and which boot manager it uses.
WIM Overview What the server read from the image, such as its version and languages.
Optional Components Extra Windows PE packages to add.
Drivers Drivers to add to the image.
Updates Windows updates to add to the image.
Build Builds the image with your choices.

Your choices on Optional Components, Drivers and Updates go into the image the next time you select Build WIM File.

Important

The image the server copies from the ADK is plain Windows PE. It does not have the SharpDay Deploy PE client in it yet. Build the image before any PC uses the folder.

Optional Components

This lists the Windows PE packages the ADK has for this processor family.

  • Tick a package to add it. Clear the tick to remove it.
  • Some packages show Required. You cannot remove these.
  • Use the search box to find a package by name or category. Tick Show selected only to see only the ones you picked.
  • If a package needs another one, tick that one too. If you do not, the build stops and the log says Prerequisite package not selected.

If the list shows No optional components found, the server cannot find the Windows PE add-on.

Drivers

Windows PE needs network and storage drivers for each PC model you set up. Without them, the PC cannot reach the server or see its disk.

This section shows the driver packs from the Drivers page as folders. See Drivers.

  • Tick the driver folders to add to the image. Ticking a folder ticks everything inside it.
  • Select All and Clear Selection change every folder at once.
  • Right-click a folder and select Expand All or Collapse All.

The build skips drivers that are not made for the image's processor family. If a driver cannot be added, the build carries on without it, and the log says which one.

Updates

This lists the Windows updates on the server for this processor family. A cumulative update from June 2026 or later also brings the boot managers inside the image up to SVN 9.0 or higher. SVN is the Secure Version Number. See Secure Boot.

  1. Download the newest cumulative update for this Windows PE from the Microsoft Update Catalog. For Windows PE from the current Windows 11 ADK, that is the newest cumulative update for Windows 11, version 24H2.
  2. Select Upload update and pick the .msu or .cab file. You can also copy update files into the folder named at the bottom of the page, then select Refresh.
  3. Tick each update you want in the image.

Only pick updates made for the same Windows version and processor family as the image. The build adds ticked updates oldest first, after the optional components and before the drivers. If an update cannot be added, the build stops and the folder keeps the image it had.

To remove an update from the server, select the delete button next to it (Delete from the server).

Build

This is where you build the image.

Button What it does
Build WIM File Builds the whole image again from the ADK's Windows PE image. It adds your optional components, updates, drivers and the PE client, and puts the boot files in the folder.
Rebuild Just the Client Only updates the SharpDay Deploy PE client inside the image you have. It does not add components, updates or drivers.

Above the buttons, the page shows when the image was last built (Date Last Built), and how many updates the next full build adds.

A full build does these steps in order:

  1. Checks the ADK and the Windows PE add-on.
  2. Copies the ADK's Windows PE image to a work area, and copies boot.sdi and the fonts into the folder.
  3. Adds the optional components.
  4. Adds the Windows updates.
  5. Adds the PE client.
  6. Adds the drivers.
  7. Writes the boot settings (BCD).
  8. Puts the boot manager in the folder.
  9. Makes the image smaller and saves it to the folder as boot.wim.

If the build fails, the boot folder keeps the boot.wim it had before.

How long it takes, and where to watch

What you started Where to watch it
Create boot folder The progress card on Boot Files > Boot Files.
Generate PE WIM No progress shows. The folder changes when the copy is done, after a few minutes.
Build WIM File or Rebuild Just the Client The Build Log on Build. The server's progress shows here as it works.

A cumulative update alone can take 10 minutes or more. When a build ends, the log says WIM Image Build Complete and how long it took.

The server builds 1 image at a time. If you start another build, it waits in a queue and the log says Added to Rebuild queue. If the server's service stops, the build stops too.

Does the server build boot files by itself?

Only when you make a new boot folder. If you choose Windows PE in Create boot folder, the server fills the folder from the ADK for you.

The server does not build or rebuild an image by itself. You start every build with Build WIM File or Rebuild Just the Client.

Secure Boot

Secure Boot only lets a PC start boot files signed by a certificate it trusts. A boot folder can hand out 1 of 2 kinds of boot files:

Choice Use it for
Old boot files Signed with Microsoft's 2011 certificate. For older PCs that do not trust the 2023 certificate yet. This works on the most PCs.
New boot files Signed with Windows UEFI CA 2023. Needed for PCs that have blocked the old certificate or are locked to an SVN.

You choose when you create the folder. To change it later, open the folder and use Which boot files should this folder use? on Files. Update boot files puts in the newest boot manager of the kind the folder is set to.

Tip

If the server cannot create a folder with the new boot files, create it with the old boot files. Switch it over once its boot image has a recent update.

If the build log warns that the boot manager is lower than SVN 9.0, PCs locked to SVN 9.0 will not start from this folder. Add a cumulative update from June 2026 or later on Updates, then select Build WIM File again.

Next steps

  1. Add the network and storage drivers for your PC models in the boot folder's Drivers section, then build again. See Drivers.
  2. Point your DHCP server at the SharpDay Deploy server. See DHCP options.
  3. If you have more than 1 boot folder for a processor family, make the right one primary.