Windows PE (WinPE)

Windows PE (WinPE) is a small operating system used to install, deploy, and repair Windows desktop editions, Windows Server, and other Windows operating systems. From Windows PE, you can:

• Set up your hard drive before installing Windows.
• Install Windows by using apps or scripts from a network or a local drive.
• Capture and apply Windows images.
• Modify the Windows operating system while it's not running.
• Set up automatic recovery tools.
• Recover data from unbootable devices.
• Add your own custom shell or GUI to automate these kinds of tasks.

Get started using WinPE

Download WinPE

WinPE is an add-on to the Windows Assessment and Deployment Kit (ADK). You can download the ADK and WinPE add-on from Download and install the ADK. Install the ADK and the WinPE add-ons to start working with WinPE.

Note

Prior to Windows 10, version 1809, WinPE was included in the ADK and wasn't an add-on.

Create bootable WinPE media

You can boot WinPE from USB, CD/DVD/ISO, or a virtual hard drive. See Create bootable WinPE media for more information.

Supported Windows features

Windows PE runs the Windows command line environment, and supports these Windows features:

• Batch files and scripts, including support for Windows Script Host (WSH), and ActiveX Data Objects (ADO), and optional support for PowerShell.
• Applications, including Win32 application programming interfaces (APIs) and optional support for HTML Applications (HTA).
• Drivers, including a generic set of drivers that can run networking, graphics, and mass storage devices.
• Image capturing and servicing, including Deployment Image Servicing and Management (DISM).
• Networking, including connecting to file servers using TCP/IP and NetBIOS over TCP/IP via LAN.
• Storage, including NTFS, DiskPart, and BCDBoot.
• Security tools, including optional support for BitLocker and the Trusted Platform Module (TPM), Secure Boot, and other tools.
• Hyper-V, including VHD files, mouse integration, mass storage and network drivers that allow Windows PE to run in a hypervisor.

Hardware requirements

Windows PE has the same requirements as Windows with these exceptions:

• No hard drive is required. You can run Windows PE entirely from memory.
• The base version requires only 512MB of memory. (If you add drivers, packages, or apps, you'll need more memory.)
• In order to boot Windows PE directly from memory (also known as RAM disk boot), a contiguous portion of physical memory (RAM) which can hold the entire Windows PE (WIM) image must be available. To optimize memory use, manufacturers should ensure that their firmware reserves memory locations either at the beginning or at the end of the physical memory address space.
• The 32-bit version of Windows PE can boot 32-bit UEFI and BIOS PCs, and 64-bit BIOS PCs.
• The 64-bit version of Windows PE can boot 64-bit UEFI and BIOS PCs.

Limitations

Windows PE isn't a general-purpose operating system. It may not be used for any purpose other than deployment and recovery. It shouldn't be used for hardware validation, as a thin client, or an embedded operating system. Microsoft makes other products, such as Validation OS and Windows IoT Enterprise, which may be used for these purposes.

• To prevent its use as a production operating system, Windows PE:

  • Automatically stops running the shell and restarts after 72 hours of continuous use. This period is not configurable.
  • All changes are lost when Windows PE reboots, including changes to drivers, drive letters, and the Windows PE registry. To make lasting changes, see WinPE: Mount and Customize.

• The default Windows PE installation uses the FAT32 file format, which poses its own limitations, including a maximum 4GB file size and maximum 32GB drive size. To learn more, see WinPE: Use a single USB key for WinPE and a WIM file (.wim).

• Windows PE doesn't support any of the following:

  • File server or Terminal Server use.
  • Joining to a network domain.
  • Connecting to an IPv4 network from Windows PE on an IPv6 network.
  • Remote Desktop.
  • .MSI installation files.
  • Booting from a path that contains non-English characters.
  • Running apps that are compiled for one architecture on a different architecture, for example running 32-bit apps on the 64-bit version of Windows PE or running Amd64 applications on the Arm64 version of WinPE.
  • Adding bundled app packages through DISM (.appxbundle packages).

Tip

In general, use the latest version of WinPE to deploy Windows. If you are using customized WinPE for Windows 10 or Windows 11 images, you may prefer to continue using your existing Windows PE image and run the latest version of DISM from a network location. To learn more, see Copy DISM to Another Computer.

Notes on running Windows Setup in Windows PE:

• For Windows 11: If you're launching Windows Setup from WinPE, make sure your WinPE image includes the WinPE-WMI and WinPE-SecureStartup optional components. If you don't include these optional components, you may see an error that your PC doesn't meet the minimum hardware requirements.
• You can use the 32-bit versions of Windows PE and Windows Setup to install 64-bit versions of Windows. For more information, see Windows Setup Supported Platforms and Cross-Platform Deployments.
• Although Windows PE supports dynamic disks, Windows Setup does not. If you install Windows to a dynamic disk created in Windows PE, the dynamic disks won't be available in Windows.
• For UEFI-based PCs that support both UEFI and legacy BIOS modes, Windows PE needs to be booted in the correct mode in order to correctly install Windows. For more info, see WinPE: Boot in UEFI or legacy BIOS mode.

See also

Content type	References
Product evaluation	What's new in WinPE
Deployment	Create a USB Bootable drive | Create a boot CD, DVD, ISO, or VHD | Install on a hard drive (Flat boot or Non-RAM) | Boot in UEFI or legacy BIOS mode | Boot to UEFI Mode or legacy BIOS mode | Use a single USB key for WinPE and a WIM file (.wim)
Operations	Mount and customize | Add drivers | Storage Area Network (SAN) policy | Create apps | Optimize and shrink the image
Troubleshooting	Network drivers: Initializing and adding drivers | Debug apps
Tools and settings	Wpeinit and Startnet.cmd: Using WinPE Startup Scripts | Identify drive letters with a script | Add packages (Optional Components Reference)
Command-line options	CopyPE | Drvload | Makewinpemedia | Wpeutil
Technologies based on Windows PE	Windows Setup | Windows Recovery Environment | Diagnostic and Recovery Toolset (DaRT)