Skip to main content

Registry gets corrupted after cloning

Thread needs solution

On two computers, I am experiencing the same problem with True Image Home 2010, that after cloning the harddisk to a backup disk, the Windows registry on the original system gets corrupted. Both computers were in hibernate mode when the cloning was done.

I suspect that True Image alters the registry on the source hard disk. Does it? This would explain why after returning from hibernate mode the registry gets corrupted after some time (because the data on the disk is not consistent with the data in the memory). This does not manifest itself immediately, but after a few days the system fails to return from hiberate mode and reports a corrupted registry.

I can clearly say that this issue MUST be related to True Image, because one of the two computers has never shown any problems, and it has not been modified in any way since a *very* long time (no hardware or software installed); also, this system is not connected to any network.

Has anyone encountered the same problem? Does True Image alter the registry on the source disk? Or, does it touch the source disk in any other way when cloning a drive?

Note: Cloning was done by booting from the True Image CD.

0 Users found this helpful

I think the clue is in hibernation.

As far as I know TI doesn't touch registry when cloning or restoring an image, but what does effect reigstry and a boot marker is the PC going into hibernation or hybrid standby mode.

Try it when the Pc isn't in hibernation.