The rescue USB is the most important thing Reflect makes, and the most commonly skipped. It takes ten minutes today, or it takes your whole recovery with it later.
Macrium's own documentation puts it bluntly: creating rescue media is the first job after installing Reflect. The reason is simple arithmetic. When Windows boots, Reflect inside Windows can restore your files and even your system. When Windows will not boot at all — dead disk, broken update, corrupted bootloader — the only Reflect that can help is the one on bootable media: a lightweight Windows PE environment carrying the full program, your disk drivers, and tools like ReDeploy and boot repair. In the video you can see this environment used for one-off backup and maintenance work; on your worst day, it is the recovery itself.
Building rescue media in Reflect downloads the Windows PE components from Microsoft and writes them to a USB stick (or ISO) along with a complete copy of Reflect and the drivers your current PC needs — storage controllers, network adapters, USB support. Boot from it and you get a minimal Windows desktop whose one job is finding image files and restoring them, plus fixing boot problems and running ReDeploy for restores onto different hardware.
A built USB is not a tested USB. Boot the PC from it once — today, while nothing is wrong. Confirm three things inside WinPE: your internal disks are listed (storage driver works), your backup location opens (network or USB destination reachable), and your newest image can be browsed. That is the checklist panel at the top of this page, and it takes five minutes. Every failed disaster restore that traces back to rescue media failed on one of those three — a missing RAID driver, a NAS the PE network stack could not reach — and every one was discoverable in advance, for free.
Rescue media carries the drivers of the machine it was built on. A stick built on an office desktop may boot a different model happily — WinPE includes a wide driver base — but storage controllers are where strangers fail. In an office, build or at least test media per hardware family, and in a Site Manager environment remember the agents' machines each need a working restore path just the same. The console manages backups; restores still begin with bootable media in your hand.
New motherboard, new storage controller, a move from SATA to NVMe RAID — rebuild the rescue media and re-run the boot test. Media from before the change may still boot yet fail to see the new disk, which is the same as not booting at all. Tie the rebuild to the same habit as your quarterly restore test and the media will never be older than the machine it protects.
See both tools working on real machines — Reflect on a single PC, Site Manager running an office full of computers.
▶️ Watch Full VideoYou can try — WinPE covers a lot of hardware, and it will likely boot both. The risk is a storage or network driver missing for one of them. Test the stick on both machines with the five-point checklist; if it passes both, one stick genuinely serves both.
Yes — build it on any other working PC with Reflect installed, then boot the dead machine from it. That is exactly how technicians use the portable and rescue versions for maintenance. Just re-check the driver point: media built on very different hardware deserves the boot test before you trust it mid-recovery.
No. Keep them separate. The rescue stick is a small, dedicated boot device; the backup drive holds your images. Combining them risks erasing your images the day someone rebuilds the media, and a restore needs both at once anyway.