and then it will copy that newly built Rescue Media to the target. If it detects that the Rescue Media needs to be rebuilt, which can be needed for a variety of reasons I’ll get to in a moment, then the Status readout will say something else, and clicking Build will force a full rebuild, which involves Reflect getting the “baseline” WinPE/RE files, adding Reflect’s application files and possibly additional drivers, configuring it all, etc. If it determines that it is current, the Status readout near the top of the window will show OK, and clicking Build will just cause Reflect to copy those cached files to the target device. When you launch Rescue Media Builder, it will check that cached build’s state. Reflect maintains a cached Rescue Media build on your system. Are there any significance licensing issues that would cause Macrium to raise an eyebrow with a situation as I had? What is the difference in the 'Build' and 'Rebuild' options?Ģ. I'll check the other 2 out along with their rescue media this evening and see if anything looks out of sorts.ġ. I have 3 computers with individual licenses. Using the procedure you posted, a force rebuild did the trick. If it says Skip instead, then just click Build as normal since in that situation Reflect is going to perform a WIM rebuild anyway.įirst, I attempted a standard rebuild of rescue media (WinPE10) with the same results (differing license keys). Click that arrow and select Force WIM Rebuild.

It shouldn’t be different.Are you comparing the key shown when going to Help > About Macrium Reflect in both cases? Do you maybe have a multi-pack license? Do the NAMES of the licensees at least match on both?Try forcing a WIM rebuild of your Rescue Media by opening Rescue Media Builder and holding Ctrl to expose an arrow on the Build button.

Macrium reflect offline activation key