
Inconsistency between the two just adds to the problem and maybe that happened to you with v7. In fact, even for v6, results will differ depending on whether you update using the patch or the full installer. At the moment, that's the least of my concerns about any Reflect updates.Ĭan't answer for v7. Possibly v7 patches as well, but I can neither confirm that nor rule it out, Mr. In view of Macrium's apparent dismissal of its potential importance, I'd advise fellow users to do something similar and also to keep a watchful eye on any future v6 updates. My own ad hoc "fix" is to stop the service and then copy the updated executable to the image path that is actually specified in the Windows registry for loading that service. My assumption was that patches don't normally update and reinstall the MacriumService.exe file for no reason at all and that some future change to that executable and/or its service dependencies might make it quite important for the right updated file to get loaded by the registry entry." As I said in my reply there: "My reason for bringing it to your attention was only to ensure that it got caught and corrected for the future. They may be for some updates, but that's a matter of pure luck and the sloppy patching attitude itself is anything but inconsequential.

Apparently, however, he considers such registry image path issues for auto-start (0x00000002) services to be inconsequential. I was assured by Nick Sills himself that it would be corrected. I cannot say myself whether the same situation exists for v7 updates, but someone should probably look into that as well.

I've noted no immediately harmful result as the most recent changes to that service executable appear to be minimal, but the discrepancy would seem to hold some significant potential for future issues if not corrected.

It remains set as "C:\Program Files\Macrium\Common\MacriumService.exe" which is where previous releases installed it. However, the image path set under the HKLM\SYSTEM\CurrentControlSet\Services\MacriumService registry key was not modified accordingly. I notice that the most recent update release has installed its MacriumService.exe file into the "C:\Program Files (x86)\Macrium\Common\" folder on all of my Windows installations.
