What a disaster!!

I have a Windows 7-64 PC, a Vista 32 laptop, and a Vista 64 laptop.
I have Rollback RX installed on my desktop.
I uninstalled it (a while ago) and installed CTM on my desktop. I also installed it on my 2-laptops as well.
Since Rollback RX is a much better product, I attempted to uninstall CTM. This corrupted my MBR. I lost everything in the process. I had to reformat and reinstall my OS. None of the suggestions in these forms relating to fixing the MBR worked (not that I should have to do that in the first place)!!

Shortly after this, I tried to uninstall CTM form the Vista 32 laptop (thinking what happened to me was a fluke). Same result. We lost EVERYTHING AGAIN!!

Comodo later announced a new patch that corrects the uninstall (bug!?!) and it was now safe to install CTM.

Since I have no trust in Comodo’s technical abilities or their ethics (leaving the download up even though there have been numerous reports of damage), I felt the need to remove it from my last laptop (Vista 64 laptop). Surely this uninstall issue must be related to either hardware or OS right?
I uninstalled it yesterday and my 3rd. computer crashed in the process of installing CTM. My MBR was corrupted and the computer will not boot. To make matters worse my daughter lost her Toshiba backup disk. I had to purchase Windows 7, which will now not accept the product key (I have been on the phone with Microsoft for hours).

Throughout all of this I followed your uninstall instructions. I am an experienced user of both Rollback RX and EAZ-FIX. I know what I’m doing. Neither of these 2 other products has caused me any issues.

Your technical support has been a joke. They usually start off very polite. Once they offer the obvious suggestions, the communication stops.

Comodo knows they have a SERIOUS flaw that they created when they attempted to modify code that worked perfectly before they got their hands on it. In all my years of computing (too many to mention) I have never run across a company that didn’t immediately fix such a serious problem or take the download down. What makes this ever worse, Comodo continues to tell it’s users that the uninstall issue is fixed knowing perfectly well that it has not been fixed.

How long will you allow this to continue? Is Comodo willing to pay for the damage that occurred by me using CTM, which they purposely misrepresented, as safe?

This is just unheard of!!

I have installed Rollback trial in my computer.
Uninstalled and installed CTM. I’ve uninstalled CTM twice and reinstalled.
Seems I’m lucky. No problems with Windows 7 32 bits here.

I’m preparing the plan “B” for me: having access (backup/restore) of the MBR. Still not found a clear way to do so.

There are some useful tools on the Hirens boot cd that allow you to backup/recover the MBR. Even so the partition table. You could give that one a try.

Hmmm… The story of lucky22 does sound a lot like the story of some other member on this forum. Also same pc configurations. Also a happy Rollback RX and EAZ-FIX user (I always wonder why people try both and then also try CTM if they claim to be happy with the 1st 2). What’s most odd is that his 1st 2 pc’s cot unbootable with the previous CTM release. His last one with the 166 release. When the 1st 2 pc’s died, then he had direct communication with the comodo staff, though today’s post is only his 1st on this forum. Guess someone did come back to us :wink:

It would if it is the other member.

This is most suspicious,has Masterblaster returned I wonder? 88)

Who is Masterblaster?

He’s the master that ended up with three CTM blasted machines ;D

Just start here, then you know https://forums.comodo.com/news-announcements-feedback-ctm/post-here-if-ctm-distroyed-your-computer-t51771.0.html

You have a suspicious mind Marlon.

What's most odd is that his 1st 2 pc's cot unbootable with the previous CTM release. His last one with the 166 release. When the 1st 2 pc's died, then he had direct communication with the comodo staff, though today's post is only his 1st on this forum. Guess someone did come back to us ;)

I didn’t say you were wrong, though. :wink: :smiley: