Corrupted Master File Table after creating new Baseline

[GlennB]

I've been using RollBack 9.1 on my Win7 (32 bit) system for over a year and updated baselines several times.
Yesterday when I did it I got a "Corrupted Master File" Error on booting which could not be repaired.
The computer still boots normally and all drives are accessable.

Fortunately before updating the baseline I imaged the drive with Drive Cloner RX. I've consulted support and they say if I replace the drive with the image after first removing RollBack everything will be fixed.

Has anyone else had this problem?

[HDS-Jacob]

Hi GlennB,

Thanks for stopping by the forum and leaving us feedback from your experience. Let's see if we can some suggestions here.

Best,
Jacob

[GlennB]

Just an update,
My problem seems to have been caused by AVG 2011.
I uninstalled it (was having other problems with it anyway) and rebooted but still got the same message. THen I took a snapshot and reverted to it and the error disappeared.
I have also consolidated several snapshots into a new baseline - which is when my problem first appeared and everything boots up normally again.
I don't know what AVG was doing but I've gone to Avast instead.

[HDS-Jacob]

Hi again GlennB,

I was also going to mention that others have suggested or mentioned using Avast as well. Hopefully, it will work smoother. Thanks for the update!

Best,
Jacob