Nick from Macrium Support indicated that for image backups, the contents of the pagefile and hibernation file weren't backed up, even though the files appear in image backups with the same size as the source, so I would expect that their contents wouldn't be cloned over either. So whether or not hibernation was enabled shouldn't change the result. But at those speeds it hardly makes a difference! The installer size grew with Reflect 7.2, and it was due to Rescue Media Builder being packaged as a standalone application (RMBuilder.exe). I asked Nick about this exact thing when I was involved in the Rescue Media Builder beta testing because I couldn't see why that change should have bloated the installer so much. He responded basically by saying that in order to get RMBuilder.exe as a standalone item, some code had to be bundled in multiple places. In any case, no I haven't forgotten that Macrium has had some problematic releases. But I'm also capable of reading 2-3 years' worth of fixes and enhancements in the Reflect V7 release notes since those 7.1 releases -- some of which were the result of bug reports and enhancement requests that I personally submitted (which doesn't even count the stuff I submitted during the betas.) If you see absolutely nothing of value anywhere in that list, then you're making an informed decision to stay put where you are. But as I said above, some fixes and enhancements might apply to scenarios you haven't encountered yet but still might, like a restore that involves ReDeploy. There were two significant fixes to ReDeploy since the 7.1 release mentioned earlier, and one since yours. In that case, Intel-to-Intel ReDeploy runs would result in Intel's CPU power management service being disabled on the ReDeployed system, which caused Device Manager to throw errors on all of the CPU items in there, and probably had power and/or performance ramifications. That has since been fixed. Maybe you haven't needed to run that type of restore yet, but that doesn't mean you won't need to. And that's just one example out of a long list of fixes and enhancements. I don't believe in updating just for the sake of updating, since that really is all risk and no reward. But I also don't believe in the pure "If it ain't broke, don't fix it" approach. If you're going to stay put, at least know what you're passing on rather than saying, "Well it works, so I'm not going to bother looking at updates and will just assume I'm not missing out on anything I might need." That's why I'm grateful that Macrium publishes solid release notes, so that I can make an informed decision as to whether an update is relevant to me rather than having to just wonder if an update might be important or if it will just be all risk for me.