Uninstall procedures?

[Guest]

[Steinsk]

I read in several BETA posts that uninstalling CTM is quite a hassle. If so, can anyone post a description on how to do it properly? 

Just in case! Not that I plan to uninstall - I LOVE it already  :comodosavedmylife:

[Monsunami]

Yah.  I need to uninstall.  It could not install properly (subconsole can't install).  Even with deleting reg keys, uninstalled services, and deleting its folder, would not let me reinstall it.

[canderoc/PsychEroc]

I've read that entering the sub-console at boot-time and uninstalling from there is the safest way.
Obviously that won't help if it never installed correctly to begin with.
Deleting things manually definitely won't work because it lodges itself in the MBR which can't be accessed from registry or files within the OS.
I'm surprised they haven't publicized any fail-safe ways of cleaning it out of the MBR.

[rambo]

An answer would be appreciated.
Thanks and Regards

[Bad Frogger]

Part:A  This is how a Textbook Uninstall should go.

However If you installed CTM alongside conflicting software, or have somehow otherwise borked your system, to the point that it will not boot, as in failed CTM uninstall, "operating system not found" or similar indication.
Odds are that your MBR has been corrupted.   See Part:B


Part:A
To uninstall COMODO Time Machine

Click Start > Settings > Control Panel

In the Control Panel, double-click Add/Remove Programs

In the list of currently installed programs, click COMODO Time Machine

Click the 'Remove' button.

Or

Click Start > All Programs > COMODO >  Time Machine > Uninstall.
 
A dialog box will appear  to confirm that you want to un-install COMODO Time Machine. Click 'Yes'.

A progress dialog box will appear, indicating the Uninstallation process.

You will be prompted to select the snapshot to which your system has to be rolled back before uninstalling the application.


Current System - If you want to keep the current state of the system intact and uninstall Comodo Time Machine, select the 'Current system' and click 'OK'.

Select one snapshot to restore to - If you want to roll back your system to a previous snapshot before uninstalling Comodo Time Machine, select the radio button 'Select one snapshot to restore to' and choose the snapshot you want to roll back to, from the drop-down menu and click 'OK'.

A progress dialog will appear.

On Completion, you will be prompted to restart the system for the uninstallation to take effect.

Click Yes to restart your system. If you plan to restart the system at a later time, click No. The uninstallation will be effective only on next restart.
On the restart, your system will be rolled back to the snapshot you selected and the Comodo Time machine will be removed.



Part:B Caution is advised from here on. Please try to verify with help if necessary that your MBR is indeed damaged/corrupted.
You can seriously hose a system with these tools.

For Vista and Win 7
How to use the Bootrec.exe tool in the Windows Recovery Environment
http://support.microsoft.com/kb/927392

For Windows XP
Description of the Windows XP Recovery Console
http://support.microsoft.com/kb/314058

or
an alternative utility for XP and older windows can be found here.
http://www.ambience.sk/fdisk-master-boot-record-windows-linux-lilo-fixmbr.php

With this you won't need recovery console or windows disc, but you will need to get proficient enough to make a bootable floppy or usb drive work.
Ignore the names "linux lilo", It doesn't matter how it got hosed. The same fix applies.

This should be more than enough info. At least regarding getting back into your OS.
And as always just ask in the forum for help with individual steps, clarifications.

Bad

[rambo]

thanks

[canderoc/PsychEroc]

This is valuable information and should be stickied!

[howardb21]

I am rather surprised that a company whose mission is to help users with ``safety and security'' would freely supply users with such a dangerous program - that that works on deep, pre-windows levels like the MBR, working with sectors, and installing drivers that load at boot time. Most windows programs, including recovery programs wont help you if trouble happens at these low levels.

That said, I suggest at minimum that you backup the MBR (master boot record), boot sector and 0 sectors before you install CTM. Programs like mbrfix and some boot managers will do this for you, and this was done more often in the old days of FAT based file systems. Then you have a chance of restoring these critical data, if CTM messes them up. It is probably also wise to take before and after snapshots of your registry and files with a program like total uninstall. This can help clean up any changes within the OS, that CTM uninstall did not restore properly. For about maximum safety, make a full, sector by sector image backup of your drive, before installing CTM.

Even all this may not help some unlucky users, if the MBR is so jumbled that most disk, partition, boot, and recovery software will not even recognize your drive anymore! In just this case, I found the free utility, test disk was able to find a lost ntfs partition and restore it, where other software could not.

[jay2007tech]

I have windows 7 32bit
This is what I do to uninstall it <----Yeah I know theres more then one way to uninstall, but if someone plans on uninstalling it.  I would serious use this method (See Below) instead of going over to the "control panel ----- remove  program"
Hopefully it'll save some people from hassle

This is how I uninstalled it (If you already tried it through other means, then it's propably damaged, still you got nothing to loss)  

1) Power up the computer
2) when the CTM screen comes up, quickly hit the "home" key on the keyboard (99% certian)
3) a new comodo screen comes up
4) click on uninstall

I think this is the best way to uninstall it because It can "uninstall" before windows comes up.
 I think the CTM is chainlinked to the MBR(something like that)   Uninstalling it with windows running like using the control panel or ccleaner could possibly be the reason for the crash.   IMO

[Greg S]

1) Power up the computer
2) when the CTM screen comes up, quickly hit the "home" key on the keyboard (99% certian)
3) a new comodo screen comes up
4) click on uninstall
I think this is the best way to uninstall it because It can "uninstall" before windows comes up.
 I think the CTM is chainlinked to the MBR(something like that)   Uninstalling it with windows running like using the control panel or ccleaner could possibly be the reason for the crash.   IMO

Hmm, CTM must be totally different than Eaz-Fix or Rollback then. Uninstalling from console is the last method to use instead of the safest. Console uninstall with them only do away with the pre win boot condition of the app. It doesn't totally uninstall it.

[Masterblaster]

Be VERY aware.
I installed CTM on 2 computers. I tried to uninstall it from the CTM console on one of them. This produced several error messages and a freeze. Upon boot up, I get a blank screen with a blinking cursor in the upper left corner. It trashed my computer. I had to reformat!!
I contacted tech support and asked them how to get this d**n thing off my other computer. They couldn't help then just stopped contacting me.
The program that was supposed to save my data has destroyed it and they cannot help me.
This sucks!!

BTW, I am a registered user of Rollback RX/EAZ-FIX. I have installed and uninstalled these programs many times from the console and never had problems.

[jay2007tech]

It doesn't totally uninstall it

What do you mean? like leftover registry entries

BTW, I am a registered user of Rollback RX/EAZ-FIX. I have installed and uninstalled these programs many times from the console and never had problems.

This is only a idea, Since you used "Eaz-Fix and Rollback" many times, would you think CTM may have screwed up partly from something left over from Eaz-Fix or Rollback.  <---I was just thinking

---this is how I came up with that idea
You know how certian anti-virus software doesn't work with each other and it may require that you uninstall it to install that one.    Let's say one can't use AVG and Kaspersky together.<-- just an example.  Let's say you uninstall AVG so kaspersky will let you install it.  But when trying to install kaspersky, it still won't let you install it because it still detects AVG (even when you uninstall it).  Only when you remove completely every single trace does finally kaspersky let you install it

Now just based on that,  maybe Comodo CTM shouldn't be installed until Eaz-Fix and/or Rollback has every single traces removed because if installing Comodo CTM.  Comodo CTM may have have problems when uninstalling

Whether it's true or not, it's just an idea (maybe one of the developers can test this theory out.)  They just need to Install AND Uninstall Eaz-Fix and  Rollback a couple of times. Then install Comodo CTM and THEN uninstall it so they can see if this is the case.  

[Greg S]

What do you mean? like leftover registry entries   

Program files and reg entries. I was referring to Eaz-Fix. I have no idea about CTM's uninstall method from the console. I haven't uninstalled it yet so hopefully it's as you say it is. My point was, CTM and EF seem to be very similar and EF recomends console uninstall as the last method to use.

[Masterblaster]

Quote
BTW, I am a registered user of Rollback RX/EAZ-FIX. I have installed and uninstalled these programs many times from the console and never had problems.
This is only a idea, Since you used "Eaz-Fix and Rollback" many times, would you think CTM may have screwed up partly from something left over from Eaz-Fix or Rollback.  <---I was just thinking

No that's it at all. I know to install and uninstall. No need to look beyone the nose on your face.
The issue is VERY simple.
Rollback RX and EAZ-FIX work as they should. They install and run as they should. When uninstalled, they perform a clean uninstall leaving MBR intack and the computer running like it was never there.
CTM corrupts the BMR sometimes upon install and sometimes upon uninstall. This happenned to me and MANY others. Once this happens, your computer will never reboot and a reformat and OS install are requires losing ALL of your impotrant data in the process.
TAKE THIS DANGERIOUS SOFTWARE OFFLINE IMMEDIATLY!!!!

[carfal]

Masterblaster, you need to get some serious perspective. I've noticed your extremely negative input for sometime now and frankly i think i can speak for most of us when i say we've all had about all we can stand of it.

Clearly you've been burned by CTM. Nobody here is disputing that. Anybody who reads these forums has got a clear picture on where you stand on this product. You continually Bible bash us (dont mean to offend any religious people....just making a point) about your bad experience but dont offer any helpful solutions to peoples problems. All your interested in is telling everyone how you got burned and DONT use this product because if i got burned....you'll get burned.

News flash...of the hundreds of downloads so far (if not thousands), why dont we see hundreds and thousands of trashed system postings here??? Dont give me the "give it time" B*llsh*t. It doesnt fly when you do the math.

Is CTM perfect?.....Definitely not.

Can there be better warnings of the consequences of a failed install or uninstall and a strong suggestion to backup your drive?....Definitely

By creating this link

https://forums.comodo.com/bug-reports-ctm/post-here-if-ctm-distroyed-your-computer-t51623.0.html

you've created a situation where a small group of people report their similar problems in one location, distorting the image of CTM and trying to make people think that if they install CTM they will definitely trash their system. Its like the mechanic working in a Factory repairing all the vehicles that come off the line with problems. All he sees is all the broken vehicles. There may be 600 vehicles that come off a line and maybe 20 go to him and the rest are perfect. What perception do you think the mechanic will have?

Well creating threads like I've mentioned presents the same perception. Sure, originally your intention may have been to warn people to be aware of what might happen (and that was admirable at first) but you've really lost that message IMO. A moderator warned ( or tried to steer you away from this model) but you didnt seem to care. Your determined to keep crying the same message. The moderator rightly suggested that these serious system crashes be designated their own posts so that they (the Dev team) can look at each problem and respond individually in an organised fashion. They close the post. What do you do? Create a new one....very childish.

Get over it. Software is not perfect. There are many progams out there that can trash a system so there is always a risk that something will go wrong. Its your responsibility in the end to protect yourself in the form of an image of your system or a simple backup of your important data files. No software company can posssibly foresee all configurations and problems that will arise on everybodys system. As a consequence, systems will occassionally fail and yes, data will be lost. This is something that anybody that knows computers is fully aware of and those of us who dont will one day get burnt and will from then on join the ranks of backing up their data. Its as devastatingly simple as that. No amount of insidious posting by you will change that. All your achieving now is annoying people with your well advertised problem with CTM.

Comodo dev team im sure are working hard to continually improve their product and clearly want our feedback on problems, whether their  serious or just simply a nuisance. So I'm not suggesting to stop posting serious crashes. What i am suggesting is post them ONCE and if there is anything new to add then by all means do so. This is not an unreasonable request is it?

So please......give it a rest and offer constructive advice. I realise that this very post isnt really constructive in itself and i'm not interested in a word war with you because frankly im bored with your whole topic (specifically from you). You've done an excellent job of making an ass of yourself and you should stop now.

[Tags:]