How to Change the Background Image (winpe.jpg) in Windows PE
Windows PE — short for Windows Preinstallation Environment — is a lightweight version of Windows used for system deployment, recovery, and troubleshooting. It boots before a full OS loads, which means customizing it, including swapping out its default background image, requires a different approach than right-clicking your desktop. If you've landed here wondering how to replace that default winpe.jpg, here's a clear breakdown of how it works.
What Is winpe.jpg and Why Does It Exist?
When Windows PE boots, it displays a desktop environment with a default wallpaper — typically stored as winpe.jpg inside the WinPE image. This file lives within the WinPE .wim file (a Windows Imaging Format archive), not on a regular accessible drive partition.
Because WinPE is a compressed, read-only image when in use, you can't simply navigate to a folder and swap the file. You need to mount the image, make your changes, and then commit and unmount it — a process handled through Microsoft's official deployment tools.
What You'll Need Before You Start 🛠️
- Windows Assessment and Deployment Kit (Windows ADK) — specifically the WinPE add-on
- A working Windows PC to perform the editing (not inside the WinPE environment itself)
- Administrator privileges on that PC
- A replacement image file (your custom background, typically saved as a
.jpg) - Basic comfort working with the command line
The Windows ADK is a free toolkit from Microsoft and is the standard method for modifying WinPE images. The specific version of ADK you'll need depends on which version of WinPE you're working with — ADK versions are tied to Windows releases (Windows 10, Windows 11, etc.).
The General Process for Replacing winpe.jpg
Step 1 — Set Up Your Working Environment
After installing the ADK with the WinPE add-on, open the Deployment and Imaging Tools Environment (a command prompt shortcut installed with ADK) as an administrator.
Copy the base WinPE files to a working directory using:
copype amd64 C:WinPE_amd64 Adjust the architecture (amd64, x86, arm64) to match your target hardware.
Step 2 — Mount the WinPE Image
The .wim file (typically boot.wim) needs to be mounted to a folder before you can edit its contents:
Dism /Mount-Image /ImageFile:"C:WinPE_amd64mediasourcesoot.wim" /Index:1 /MountDir:"C:WinPE_amd64mount" Once mounted, the WinPE file structure becomes accessible like a normal folder at the specified mount directory.
Step 3 — Locate and Replace the Background File
Navigate to the background image location within the mounted image. The path typically follows this structure:
C:WinPE_amd64mountWindowsSystem32winpe.jpg Copy your custom .jpg over the existing file — keeping the same filename (winpe.jpg) and making sure the file is a standard JPEG. Mismatched file types or filenames may result in WinPE displaying a blank or black background instead.
Step 4 — Unmount and Commit Changes
Once your replacement file is in place, unmount the image and save (commit) the changes:
Dism /Unmount-Image /MountDir:"C:WinPE_amd64mount" /Commit If you want to discard your changes instead, replace /Commit with /Discard.
Step 5 — Rebuild Your Bootable WinPE Media
After committing, create your bootable ISO or USB drive using:
MakeWinPEMedia /ISO C:WinPE_amd64 C:WinPE_custom.iso Or for USB:
MakeWinPEMedia /UFD C:WinPE_amd64 F: Where F: is your USB drive letter.
Key Variables That Affect How This Works 🔧
Not every WinPE customization experience is the same. Several factors shape the process:
| Variable | How It Affects the Process |
|---|---|
| WinPE version | ADK version must match; file paths may differ slightly |
| Target architecture | amd64, x86, and arm64 use separate base images |
| Image resolution | WinPE may scale the background differently depending on display drivers loaded |
| Third-party WinPE builds | Tools like WinBuilder, Sergei Strelec, or custom enterprise builds may store the background differently or use alternative filenames |
| Organization/IT policies | Enterprise deployment environments may restrict or automate image modification |
If you're working with a third-party WinPE distribution rather than a vanilla Microsoft build, the background file might not be named winpe.jpg at all, or it could be embedded in a different layer of the image. Some builds use registry tweaks to point to a custom wallpaper path rather than replacing the file directly.
When a Registry Edit Is the Alternative Approach
In some WinPE configurations, the background is set via a registry value rather than a hardcoded file path. Within the mounted image, you can load the WinPE registry hive and modify the wallpaper path key — similar to how Windows sets desktop backgrounds in a full install.
This method gives more flexibility (you can point to any file path accessible at boot time) but requires comfort with editing offline registry hives using regedit or reg load commands. The specific registry key involved mirrors the standard Windows wallpaper key under HKCUControl PanelDesktop.
What Determines Your Specific Path Forward
The straightforward ADK method works reliably for clean, Microsoft-built WinPE images. But once variables like custom WinPE distributions, organizational policies, target architecture, or WinPE version enter the picture, the exact steps shift. Even something as simple as image dimensions or JPEG quality settings can affect how the background renders in a minimal boot environment with limited display driver support.
Your WinPE source, the version of ADK available to you, and what you're ultimately using WinPE for all shape which approach actually fits your situation. 🖥️