# PhoenixPE builds a Windows rescue environment you assemble yourself

> PhoenixPE is a fully customizable WinPE rescue and recovery environment for Windows 10 and 11, built on the PEBakery build engine, with a scriptable way to add your own applications to the image. The first build needs internet access to pull the Windows ADK, and antivirus false positives are a documented feature of the result.

**PhoenixPE/PhoenixPE** — PhoenixPE allows you to create a customized Rescue/Recovery Environment based on Win10/Win11.

- Repository: https://github.com/PhoenixPE/PhoenixPE
- Stars: 630 · Forks: 59
- Language: HTML
- License: NOASSERTION
- Published: 2026-10-22 · Updated: 2026-10-22 · Language: en
- Canonical page: https://hysenlabs.com/projects/phoenixpe-phoenixpe

## A rescue environment you build rather than one you download

PhoenixPE is a fully customizable WinPE rescue and recovery environment built on Windows 10 or 11, and the framing of the project is a response to a broken system rather than a feature. When a machine will not boot, the environment boots instead, from a USB drive, a CD or DVD, over the network with PXE, or from a hard disk, and it gives access to a suite of recovery, diagnostics and repair tools without needing a working operating system. The project describes itself as developed from the ground up to be fast, flexible and user friendly, and the specific complaint it levels at older projects is that they accumulated decades of hacks, workarounds and bloat. That is a design position rather than a feature list, and it is what makes the project worth reading. The alternative, a prebuilt ISO from a redistribution site, gives you an image you did not choose, with software you cannot update and licensing you cannot audit. PhoenixPE inverts that, and the cost of the inversion is the setup work in the getting started section.

## PEBakery is the engine, and it is the real interface

The build engine is PEBakery, and the readme is explicit that this is a next generation engine delivering faster build times and features that legacy Winbuilder projects cannot match. That choice shapes how the project is extended. PhoenixPE is described as modular and extensible, with your own applications and scripts added using PEBakery's scripting language and a documented PhoenixPE API, and the claim is that most scripts can be updated to a new application version simply by changing a version number. That last point is the one that matters in practice. A recovery environment built once becomes stale, and the usual reason people stop rebuilding is that updating a tool means editing a script in several places. If the version lives in one variable, the rebuild is routine. The API and the project variables are documented on the wiki, alongside the PEBakery documentation itself, and the readme points to the community forums as the place to look when a script for a similar application already exists. The top level tree supports this reading, with an Editor directory, a Projects directory and a docs directory, which is the shape of a project that is closer to a configuration than an application.

## Sources are boot images or recovery images, and the first build needs the network

The getting started section is short and its requirements are specific. You need a Windows 10 or Windows 11 host machine to run the build, a compatible Windows source, and internet access for the initial build, with a wiki page listing which sources are compatible. The project builds from either a boot image or a Windows Recovery Environment image, and the readme links the source compatibility page rather than enumerating the combinations, which is a reminder to check that page before you commit an afternoon to a build. The steps are to download the latest release and unpack it, launch PEBakery and point it at your source and choose the scripts to include, then build, and PEBakery downloads the required tools from the Windows ADK on the first run and caches everything locally, so subsequent builds need no internet. Writing the result to media is a separate step with Rufus or your preferred tool, and there is a PXE route for network boot. The readme also offers a practical answer for slow connections, the per script download button in PEBakery for pre-caching installers, and the suggestion of copying the whole PhoenixPE folder to a USB drive and downloading the files elsewhere.

## What ends up in the image

The shipped tool set is grouped into three families, and the grouping tells you what the environment is for. Recovery and repair covers drive backup, cloning and imaging, file recovery, password recovery, and offline operating system troubleshooting, repair and recovery. Security covers malware removal, forensics tools and a secure disk wipe. Hardware and maintenance covers benchmarking, drive partitioning, install prep, hardware diagnostics and system information. The readme is clear that the selection is curated for the most common recovery scenarios, and that because every user's needs differ, the scripting language is what makes it straightforward to add your own applications and settings. The customisation section expands on that, listing the ability to configure application settings at build time, register shell extensions and file handlers, and tailor almost every aspect of the environment, which is a list that matters more in a PE image than it would in a normal installation, since the whole environment is rebuilt rather than patched.

## The argument against prebuilt ISOs

The most opinionated part of the readme answers the question of why not just download a prebuilt image. It names the popular ones, including Hiren's, Gandalf's, MediCat and Sergei, and observes that many are themselves built on Win10XPE or on PhoenixPE projects, but with the licences and credits stripped out and a different name attached. The readme adds that they ship with outdated software, that some prebuilt images hide freely available software behind paywalls, and that some bundle warez, which puts the user at legal risk. The argument about trust is the strongest one. You have no visibility into what is baked into someone else's image, and you are running it with full system access on a machine that is already in trouble, so you are trusting a stranger with a tool that can read and write every disk attached. Building your own means you control what is included, you can keep it current, you can add your own applications and licence keys, and you get it in your own language. The cost is stated plainly, a little work for the reward.

## Antivirus warnings, licence metadata and a dated release train

Two smaller things are worth knowing before you ship an image. The first is the antivirus question, which has its own wiki page, because recovery tools often use low-level system access that antivirus software flags incorrectly, and the readme calls it a known false positive rather than a bug. If you distribute an image built with PhoenixPE, recipients will see warnings, and the documentation page is what you point them at. The second is the licence metadata, which does not fully agree with itself, since the readme badge says MIT while the repository listing reports a custom licence that GitHub cannot classify and points to the LICENSE file, so that file is what to read rather than the badge. The release naming is by date, with tags for 2026.07.25, 2026.04.16 and 2026.03.30, and the last push was on 2026-10-06, so the project is maintained and a build from a recent tag will not be stale. A last detail worth knowing is that uninstalling is deleting the PhoenixPE folder, and that a request to include a particular application is answered with a flat refusal, which tells you the curation is deliberate rather than accidental.

## Conclusion

PhoenixPE earns its place for a technician or a support team that has to hand people a recovery environment, because the set of tools in the image is your decision rather than the distributor's, and a script that pulls a specific application version can be rebuilt next month. It is a poor choice if you are not on Windows, since the build host must be Windows 10 or 11, and a poor choice if you need the result immediately, since the first build downloads from the Windows ADK. Verify three things before you start: which of the source images you have available, because the project builds from a Windows source and lists compatibility on a wiki page, that the machine you build on has the disk space and time for the first download, and how you will handle the antivirus warnings, since the project documents recovery tools as a known false positive source and links a page explaining it. The licence is in the LICENSE file, the last push was on 2026-10-06, and releases are named by the date they were cut.

## FAQ

### What is PhoenixPE and what does it do?

It is a fully customizable WinPE rescue and recovery environment built on Windows 10 or 11, booted from USB, CD or DVD, over PXE, or from a hard disk. It gives access to recovery, diagnostics and repair tools without a working operating system.

### How do I build a PhoenixPE image?

You need a Windows 10 or 11 host, a compatible Windows source, and internet for the first build. Download the latest release, launch PEBakery, point it at your source and select the scripts to include, then build. PEBakery fetches the required tools from the Windows ADK on the first run and caches them, and you write the result to media with Rufus or set up PXE.

### Can I add my own applications to a PhoenixPE build?

Yes. The project is built on PEBakery's scripting language with a documented PhoenixPE API, and the readme says most scripts can be updated to a new application version simply by changing a version number. You can also configure application settings at build time and register shell extensions and file handlers.

### Why does antivirus flag software in a PhoenixPE image?

The readme calls it a known false positive, because recovery tools often use low-level system access that antivirus software flags incorrectly. The project has a dedicated wiki page explaining it in full.

## Sources

- [Issues](https://github.com/PhoenixPE/PhoenixPE/issues)
- [PhoenixPE/PhoenixPE on GitHub](https://github.com/PhoenixPE/PhoenixPE)
- [README](https://github.com/PhoenixPE/PhoenixPE/blob/master/README.md)
- [Releases](https://github.com/PhoenixPE/PhoenixPE/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/phoenixpe-phoenixpe