Restore a Macrium Image to Different Hardware With ReDeploy
Your PC died but its image survived. The new machine is different hardware — and Windows, restored raw, will refuse to boot on it. ReDeploy is the bridge.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ How-to guide
🎥 Watch the full video — Macrium Reflect and Site Manager compared side by side, step by step
This is the job that separates disk imaging from mere file backup. A dead motherboard, a stolen laptop, an office upgrade — the image exists, but the replacement hardware differs, and a plain restore boots into a blue screen because Windows tries to start storage hardware that is not there with drivers for hardware that is gone. Macrium's ReDeploy, run from the rescue media straight after a restore, reconfigures the restored Windows for its new home. This guide covers what it really does, the order that works, and where its limits honestly lie.
ReDeploy — what happens, in order
1 · Boot rescue mediaWinPE starts
2 · Restore the imageOnto the new hardware
3 · Do NOT reboot yetRun ReDeploy first
4 · Point at driver foldersStorage drivers especially
5 · ReDeploy injects driversBoot-critical only
6 · First boot into WindowsInstall the rest normally
The official Macrium sequence. Step 3 is the discipline — a premature reboot is the classic own goal.
1
Why a Raw Restore Fails on New Hardware
Windows is not hardware-neutral once installed. Its boot process loads the driver for the storage controller it was installed on; move the disk image to a machine with a different controller — a new chipset, a RAID card, a virtual machine — and boot dies early with an inaccessible-boot-device error. The data is fine. The settings are fine. The directions to the disk are wrong, and that is precisely the class of problem ReDeploy exists to fix.
2
What ReDeploy Actually Does
Per Macrium's own documentation, ReDeploy examines the restored, offline Windows installation, detects the critical hardware changes, and searches for matching drivers — in locations you point it to, on removable media, and in the Windows driver store — then injects the boot-critical drivers and adjusts the system so it can start. One honest limit, stated by Macrium itself: ReDeploy does not install the complete driver set for the new hardware. It makes Windows bootable. Graphics, network extras and the rest are installed normally, inside Windows, afterwards.
3
The Steps, in the Order That Works
Boot the new machine from the Macrium rescue USB.
Restore your image onto the new disk — and when the restore finishes, do not reboot. Set the after-restore action aside and stay in the rescue environment.
Run ReDeploy Restored Image to new hardware from the Restore menu, and select the restored Windows installation.
On the driver locations screen, point ReDeploy at the driver folders you prepared (next section) — the storage controller driver above all.
Let it inject and finish, then reboot into Windows and install the remaining device drivers as usual.
4
Prepare the Drivers Before You Need Them
ReDeploy can only inject drivers it can find. Before the restore, download the new machine's storage/RAID controller driver (and chipset drivers) from the manufacturer, extract them to plain folders on a USB stick — installers and .exe wrappers are no use here; ReDeploy wants the driver files themselves. Keep that stick with your rescue media. In an office, one driver folder per hardware model turns a hardware-swap restore from research project into routine.
5
The Honest Limits
Editions: ReDeploy is a feature of the paid Reflect line, prominently the Server editions — check your edition includes it before the bad day, not during.
Activation: Windows and some software will see a new machine and ask to reactivate. That is licensing working as designed, not a ReDeploy failure.
Distance: the further the hardware jump — decades-old to brand new, physical to virtual — the more first-boot tidying to expect. Same-era hardware swaps are routine; archaeology is not.
It is also the P2V door: the same process prepares an image to boot as a virtual machine, which is a legitimate way to keep an old system alive for one legacy program.
🔴 Honest note: ReDeploy rescues the operating system, not the situation. If the dead machine's image is months old, the restored PC is months old too — pair hardware restores with the backup discipline from this series, or you will boot a museum.
🎥 Watch the Complete Video Guide
See both tools working on real machines — Reflect on a single PC, Site Manager running an office full of computers.
Can ReDeploy move Windows from an old HDD machine to a new NVMe PC?
That is its home ground — a storage change is the classic case, provided you supply the new controller's driver when asked. The bigger the overall hardware gap, the more post-boot driver installation to expect, but the boot itself is what ReDeploy secures.
Do I lose my programs or files when I use ReDeploy?
No. ReDeploy modifies the restored Windows installation's hardware configuration, not your data — programs, files and settings arrive with the image. What can change is activation state: Windows and some licensed software may need reactivating on the new hardware.
Is there a free way to do the same thing?
Windows sometimes survives a hardware swap on its own with generic drivers, and a fresh install is always an option if you have the time. But a supported dissimilar-hardware restore is a paid-edition capability in the Macrium line — plan for that if hardware moves are part of your job.
This guide is based on the Technical Anshu video comparing Macrium Reflect and Site Manager • Stuck on a step — ask in the video comments and the community will help 🙏