True and this is seen with Windows inbuilt imaging for some users yet I have never had a problem so far. In my case this PC in question has been imaged for years with Macrium including using the ext HDD in question. The fact that it is reported by others as a very occasional event suggests Macrium isn't 100% reliable. I'll still use it but it's nice to have images made by another program as a safeguard.
I don't use Macrium (still with Ghost 15) but that's not a flaw with Macrium. To me, anyway.
It's caused either by a change in the VSS snapshot, which is taken taken before imaging begins, or possibly by write caching not being enabled on your external HDD.
That info is garnered by google.
I don't see where Macrium is really at fault, though a case could be made for that. Ghost 15 isn't perfect either. OTOH, maybe software should be perfect. We can dream.
To my mind, a real failure is when the image won't restore properly.
Do you image cold, using the "rescue environment?"
I've never done it any other way, except when I was playing with the inbuilt Win 7 imaging.
Not saying that should be accepted practice, just my preference.
Write caching was enabled. I've been taking images every few weeks using Macrium and Windows inbuilt for some years now and have never experienced a problem like this before. The ext HDD checks out with thorough testing and the system configuration for the PC in question is the same as ever. Given that others have experience the (rare) event I think it is likely some glitch between Macrium+Windows.
I have had volsnap errors with Windows inbuilt. They are logged in the event viewer but this has never impacted on the integrity of the image.
Quote