Revo Uninstaller Hangs
John
it goes through the first process, using the manufacturers uninstallation
file, it hangs. I cannot even close it down and have to resort to Windows
Task Manager to shut it down.
I am still able to uninstall programs using the manufacturers uninstall
files.
I suspect it has to do with COMODO Time Machine which does images of the
hard drive. I've read something like this before.
Does anybody know of similar issues?
Ron May
wrote:
> Does anybody know of similar issues?
No problems here with v1.92 and 32-bit Vista Home Basic SP2. No Comodo.
--
Ron M.
Ubuntu User #33236 (10.10)
Registered Linux User #511161
Ubuntu/Vista Dual Boot
John
Using Opera's revolutionary email client: http://www.opera.com/mail/
There are issues regarding Revo Uninstaller and COMODO Time Machine.
Problems occur when Revo Uninstaller is used to remove COMODO Time Machine.
COMODO Time Machine should only be removed using its own uninstall file.
VanguardLH
Uffda, you're using CTM? And on a critical or production host?
Considering how the program function, where it stores its backups, and
hiding its files from the system API (which leads to other utilities not
knowing those sectors are inuse), you are taking a big risk with your
host.
CTM doesn't support TRIM for SSDs (you must disable TRIM for the SSD
which means reduced life and speed).
CTM stores it snapshots in the free space in the *same* partition that
is being snapshotted. It hides its files from the system API.
Utilities that look for and manage freespace won't know about those
files. You must NEVER use a utility that wipes free space (e.g.,
CCleaner). If the hard disk dies, you also lose your snapshots so it's
all lost (just like you never had snapshots, never did backups, and the
disk drive and you lost it all). The use of this hidden disk space can
enlarge so much over time that the OS won't function (it thinks there's
freespace but there isn't). Backups should be saved on a *different*
disk or, at a minimum, in a different partition.
CTM usurps the bootstrap code area of the MBR. This means you are no
longer using the standard bootstrap program. It also means you cannot
use another program that usurps the MBR's bootstrap area, like rescue
programs (e.g., Acronis TrueImage or Paragon boot mode restore),
multiple boot managers (e.g., GAG), or disk/partition encryption (e.g.,
TrueCrypt, Comodo Disk Encryption).
Crashing or hanging Win7 x64 on boot. Sometimes a reboot works. Event
viewer shows something failed with "volmgr".
Melih doesn't seem really intent on developing CTM. There is a spurt of
activity, then it's dead for a long time, then a small spurt, then dead
again. It doesn't seem to have its own dedicated team of developers.
Instead, it appears they rotate developers to the lesser important
programs, and CTM is one of them. It's been 7 months from 2.8 to the
2.9 (plus it doesn't appear but 1 or 2 devs working on it when not
working on something else) but then they have a LOT of problems to fix
and still have a lot more to fix. Note that all versions of CTM should
be considered beta versions.
Restores in the latest version are extremely slow. A 5-minute restore
in 2.8 has become a 40-minute restore in 2.9.
If the host has been left idle for awhile, CTM will begin defragging its
snapshots. This results in 100% CPU occupancy. The user may have to
wait up to 1 minute before CTM quiesces to wrest control back to the
user for the host to be usable again.
You must never use a defrag tool while CTM is installed. So the
protected partition continues to get slower and more disk head thrashing
over time with continued updates to the file system in the protected
partition. You must uninstall CTM, defrag, and reinstall CTM. Sucks!
If you choose to uninstall CTM, you lose the current state of your host.
You must uninstall the last (most recent) snapshot to uninstall CTM.
This means reverting your host back to before that last snapshot.
Have you ever bothered to review the posts over in their CTM forum?
Installing CTM will plummet the reliability of your host. I'm surprised
you chose to install CTM assuming you did the research on it, like
reading the forums for it.
You didn't perhaps try to use Revo to uninstall CTM, did you? There are
lots of forum posts on why that doesn't work and can cause a
nonbootable, crashing, or looping host.
Craig
> Considering how the program function, where it stores its backups, and
> hiding its files from the system API (which leads to other utilities not
> knowing those sectors are inuse), you are taking a big risk with your
> host.
Thanks VanguardLH. I can quibble with your editorial decisions but I
really value pieces like this.
Best,
--
-Craig
http://pricelesswarehome.org/
Saxman
> You didn't perhaps try to use Revo to uninstall CTM, did you? There are
> lots of forum posts on why that doesn't work and can cause a
> nonbootable, crashing, or looping host.
I've not tried to uninstall CTM at all. It's running fine on my machine.
As I said earlier one needs to delete CTM with its own uninstall file.
It's Reveo Uninstaller I'm having problems with.
You make the software sound like crap, but it was recommend by PC World
magazine (I think) as being one of the best 100 pieces of free software.
milsabords
> I said earlier one needs to delete CTM with its own uninstall file. It's
> Reveo Uninstaller I'm having problems with.
I do not understand your point.
Revo first executes the program's uninstaller. After that it scans the
registry and the file system for residues.
There may be a piece of Comodo software in the background which should
be killed.
Saxman
> I do not understand your point.
> Revo first executes the program's uninstaller. After that it scans the
> registry and the file system for residues.
> There may be a piece of Comodo software in the background which should
> be killed.
I need to verify that when Revo Uninstaller hung, I was not trying to
remove COMODO Time Machine. I merely stated that I thought it might
something to do with CTM.
Good reply from VangauardLH. It's correct that if one loses the hard
drive, then the image is lost as well unless it's stored elsewhere. I
think CMT is only really intended to be a 'roll-back' piece of software.
gufus
"John" <john.h....@btinternet.com> wrote in message:
On Sat, 23 Apr 2011 08:22:08 +0100
> I've tried using Revo Uninstaller a couple of times recently and as soon
> it goes through the first process, using the manufacturers uninstallation
> file, it hangs.
Check the task bar at this point, the program being un-installed might be
asking to proceed and you don't see that.
-
With best regards, gufus. E-mail: stop.nos...@shaw.ca
Message-ID: op.vudqq6qnthnkgo@john-pc Sent at 13:10
gufus
"Ron May" <may...@hotmail.com> wrote in message:
On Sat, 23 Apr 2011 04:17:40 -0500
>> Does anybody know of similar issues?
>
> No problems here with v1.92 and 32-bit Vista Home Basic SP2. No Comodo.
XPP/XPH SP3 32-bit works fine here.
-
With best regards, gufus. E-mail: stop.nos...@shaw.ca
Message-ID: e065r6lt3u2515cij...@4ax.com Sent at 13:30
gufus
"milsabords" <nos...@nospam.org> wrote in message:
On Sun, 24 Apr 2011 01:10:11 +0200
> There may be a piece of Comodo software in the background which should be
> killed.
Or Comodo is asking to continue (in the background)
-
With best regards, gufus. E-mail: stop.nos...@shaw.ca
Message-ID: 4db35c55$0$5800$426a...@news.free.fr Sent at 13:50
Saxman
wrote:
> Check the task bar at this point, the program being un-installed might be
> asking to proceed and you don't see that.
I'll do that next time thanks.
Saxman
wrote:
> Or Comodo is asking to continue (in the background)
I'll check that out. CTM I would assume must run in the background in
much the same way that Windows System Restore does?
Saxman
wrote:
> Or Comodo is asking to continue (in the background)
>
Just checked using Windows Task Manager/Processes and it's there using
3.228K's worth.
I'll turn it off next time.
gufus
"Saxman" <john.h....@btinternet.com> wrote in message:
On Sun, 24 Apr 2011 21:51:57 +0100
>> Check the task bar at this point, the program being un-installed might be
>> asking to proceed and you don't see that.
>
> I'll do that next time thanks.
Revo will stay on top, that's what I discovered. couldn't see the
manufacturers uninstallation questions.
-
With best regards, gufus. E-mail: stop.nos...@shaw.ca
Message-ID: op.vugmwvpf8ok78v@john-pc Sent at 15:13
gufus
"Saxman" <john.h....@btinternet.com> wrote in message:
On Sun, 24 Apr 2011 21:53:42 +0100
>> Or Comodo is asking to continue (in the background)
>
> I'll check that out. CTM I would assume must run in the background in
> much the same way that Windows System Restore does?
Don't know. I would *guess* Yes
-
With best regards, gufus. E-mail: stop.nos...@shaw.ca
Message-ID: op.vugmzseh8ok78v@john-pc Sent at 15:24
gufus
"Saxman" <john.h....@btinternet.com> wrote in message:
On Sun, 24 Apr 2011 21:53:42 +0100
> I'll check that out. CTM I would assume must run in the background in
> much the same way that Windows System Restore does?
-
With best regards, gufus. E-mail: stop.nos...@shaw.ca
Message-ID: op.vugmzseh8ok78v@john-pc Sent at 16:32
VanguardLH
Comodo Time Machine is not a typical application. Not only does it
install drivers to intercept file I/O for the disk but it also usurps
the MBR bootstrap code. You don't run an uninstaller from within
Windows. You boot using their MBR bootstrap program (what they call the
"subconsole") and uninstall from there. You are required to rollback to
a prior snapshot (so you lose the current state of your host) and then
the boot-mode uninstaller runs.
Don't expect all programs to uninstall using simple file deletes or MSI.
For this program, you do NOT run the uninstall from within Windows, so
something like Revo is not only unusable but also hazardous. Revo is
not the panacea uninstaller that many users think it is.
If Comodo has protection for CTM, the hang is likely CTM preventing an
uninstall of itself under the *wrong* environment (i.e., from within
Windows).
Go read CTM's manual, page 76, on how to properly uninstall it:
http://www.google.com/url?sa=t&source=web&cd=1&ved=0CCwQFjAA&url=http%3A%2F%2Fcomodo.com%2Fsupport%2Fuser-guides%2FComodo_Time_Machine_User_Guide.pdf&ei=otC0TbmdIcne0QG96-D0CA&usg=AFQjCNHtNOjgizoJI5z8x4CjenQjcC22zQ
REM
> lugnut <lug...@roadkill.net> wrote:
>I recently upgraded to Avast! v6. Reveo then started
>exiting as soon as the software uninstaller completed and
>before the registry scan started. I removed Avast! and
>replaced with another AV and Revo now is back to normal. I
>contacted Revo about this and their response was that they
>could find no problem. I went bact to Avast! and the
>problem returned. It looks like they just won't play nice.
>Since there was no problem until the Avast! v6 installed, I
>suspect the problem is with Avast!.
You might try manually updating the program in Avast!
They had a problem with the sandbox part jumping in at the wrong
times. We run the commercial version, but I'm sure the prigram is the
same.
I had to manually update the (Avast!) program and reboot all problem
PCs. Only certain types of software had this problem. Luckily the
majority of the PCs here did not run software that triggered this
flaw, which has been fixed.